We’ve found that there’s no consistent way ATS’ track the “hired” stage. Unfortunately most ATS's allow people to create their own stages and orders so we don't have a way of automatically determining if a candidate was hired.

What we’ve built is a "current_stage" field on the Application Common Model which can be populated with the hired status. You’ll want to recommend to your customers that they have a clear hired status as application stages are often very customized by instance.

This is a common use case for our customers, so they generally do the following:

  • After a customer links their ATS via Merge, allow the initial sync to complete

  • Once the initial sync finishes, prompt the user with all the job stages in their system.

  • Once a user selects the “Hired” stage, maintain the mapping on your end

Greenhouse and Lever are two integrations that we do have a way of determining "hired". If you are using Greenhouse or Lever, you can use the following criteria to identify hired candidates:

  • Greenhouse: Applications in the "Hired" stage represent candidates that have been hired

  • Lever: Applications with “reject_reason”:“Hired” represent candidates that have been hired

Did this answer your question?