This use case provides technical implementation details for sending selection signals to SEEK.
Selection signals represent the progression of candidates and positions through a recruitment process.
Feeding these back to SEEK helps to improve our search & recommendation capabilities,
and ultimately match candidates with the optimal positions on offer.Signal capture is supported for partners that have implemented Job Posting and/or Optimised Apply.
It is not currently available for recruitment software providers that post SEEK job ads via middleware and solely support linking out to an external apply form.By building Selection Signals,
you agree to the additional terms specified in Section K of our SEEK API Terms of Use .GraphQL operations for Selection Signals require a partner token.Selection Signals refers to its key concepts using the following terminology:
- A position is an opening at an organization that may be advertised through different channelsYour software may refer to this concept as an employment opportunity, job order, job requisition, job vacancy, or position opening.
- A candidate is an individual who could fill the positionYour software may refer to this concept as an applicant, jobseeker, or talent.
- An application is a candidate’s expression of interest for a given position
- A
PositionStatusUpdatesignal upon changes to the status of a position, if it was advertised on SEEK - An
ApplicationCompletesignal upon submission of an external apply form, if the candidate used SEEK to apply for the position - An
ApplicationStatusUpdatesignal upon changes to the status of an application, if the candidate used SEEK to apply for the position
Section | Description |
|---|---|
Walk through data structure & mapping concerns | |
Break down scenarios for application signals | |
Break down scenarios for position signals | |
Provide implementation guidance on signal capture |