Job Board - Native Apply

For example, with SEEK: Job boards - Native apply/Quick apply feature enables you to post jobs directly on platforms such as Seek from within the XeopleRecruit application. This eliminates the need for redirection to external websites. This feature offers candidate(s) a seamless experience, enabling them to apply for jobs without leaving the platform they are applying on. 

Recommend Reading: How to configure the Job Boards, click here: Marketplace Configuration - SEEK, Marketplace Configuration - Broadbean.

Recommend Reading: How to configure the application form to map with job postings: Configure Job Application Form.

Recommend Reading: How Job Boards Management works, click here: SEEK, Broadbean.

Recommend Reading: How SEEK Job Posting - Native Apply works, click here: SEEK.

Native Apply (Without Screening (Knockout) Questions)

Screening (Knockout) Questions are optional for Native Apply. If you choose not to enable them:

• You publish the job on SEEK.
• Candidates apply directly.
• All applicants are automatically mapped to the Applied stage in the job workflow.

Native Apply (With Screening (Knockout) Questions Enabled)

If you enable Screening Questions via the checkbox:

• The default Application Form (mandatory) is automatically selected (you may choose another if needed) before publishing the job on SEEK.
• Candidates applying for the job will see the Screening Questions.
• Based on their answers:
  • Correct/Matching response → Candidate is mapped to the Applied

• Incorrect/Non-matching response → Candidate is mapped to the Rejected stage (linked to the reject stage type in the workflow).

Seek – Apply Type – Native Apply

After a Job Apply – Candidate Created under the Candidate Module

When a candidate applies to a job using SEEK Native Apply, their profile information automatically is update in the Candidate Summary page along with Experience, Education and Skills. This removes the need to enter the information manually and helps keep data accurate and consistent.

Experience (Career History)

The following information from SEEK is transferred to XR:

• SEEK provides only month and year. XR requires a complete date.
• The system converts the date to dd/mm/yyyy format and use the first day of the month. For example, May 2024 becomes 01/05/2024.
• If "Still in Role" is selected in SEEK, the record is marked as the current company in XR.

Experience   - Coming from SEEK

Education

The following information from SEEK is transferred to XR:

• SEEK provide only the year (for example, 2026), while XR requires a full date.
• In such cases, the system defaults the date to 01/01/2026 (first day of the first month).
• This value will be stored in the End Date field to ensure compatibility with XR.

Education   - Coming from SEEK

Skills Mapping from SEEK to XR

When a candidate applies through SEEK Native Apply and selects skills, the system:

• Check whether each selected skill already exists in XR.
• If the skill does not exist, create the skill and associate it with the candidate profile.
• If the skill already exists, associate the existing skill with the candidate profile using an exact match.
• Prevent duplicate skills from being created or associated with the candidate profile.

Skills   - Coming from SEEK

Duplicate Prevention

The system avoids creating duplicate skills in the master data.

For example:

• If the master database already contains "age care", and the candidate selects:
  • "Age Care" (different capitalisation), or
  • " age care " (extra spaces),

the system recognises these as the same skill and link the existing "age care" skill to the candidate instead of creating a new one.

The system also prevents duplicates when a candidate selects the same skill multiple times in SEEK Native Apply. In such cases, only one instance of the skill is associated with the candidate profile.

This ensures that candidate profiles accurately reflect their skills, maintains data consistency, and prevents unnecessary duplicate records in XR.

Editing in XR

After the information is transferred, you will be able to edit and update the data in XR.

SEEK Native Apply – Split Screen (Job Action) – Applications PDF

System automatically generates a consolidated PDF of all details including (experience and education) submitted through the application form.
You can access this PDF from multiple locations within the application:

• Job Summary> Grid View>Checkbox placed in front of candidate> Actions for the respective job.
• Job Summary > List View > Three-dot menu next to the candidate > View Application.

The PDF displays:

• Job details: Job Title, Organisation Name, Job Reference ID, Date Applied.
• Source field: Allows you to identify where the candidate was sourced from.
• Candidate information: First Name, Last Name, Email, Phone, Address.
• Professional details: Current Salary, Notice Period, Skills, Experience and  Education. 
• Attachments: Resume, Cover Letter (if provided).
• Screening: Knockout Questions and the candidate’s responses. Correct responses are highlighted in green and incorrect responses in red.

Job Summary – Candidate Checkbox - Applications

If the candidate is knocked out based on application form configuration or knockout settings, the PDF will display a clear Knocked Out watermark, along with the specific responses that triggered this outcome.

Job Summary – Candidate Checkbox – Applications – Knockout

When configuring Broadbean from the Marketplace, you can select only one plan type at a time: Application Form or Email Apply. For Broadbean, Native/Quick Apply is Email Apply. If you choose Email Apply, this will be your only option for posting jobs. To use the Application Form (redirecting to the Xeople career page), you must reconfigure Broadbean from the marketplace.

Back to Top