Where HireLayer sits in your application pipeline
Your ATS stays the system of record. Calls happen server-side, at two moments your product already has: when a CV is uploaded, and when a recruiter reviews applications for a job.
- 1
Your system
Step 1, your system: An applicant submits a CV
Your upload service receives the file with the application, from your career page or a job board integration.
- 2
HireLayer
Step 2, HireLayer API: Parse the document
Send the file with application_id set to your application id. The parsed resume comes back in the same response, under resume.
POST /api/v4/resumes/parse
- resume.info_candidate
- resume.work_experiences[]
- resume.educations[]
- resume.languages[]
- resume.skills[]
- 3
Your system
Step 3, your system: Prefill and store
Map the fields to your candidate model and index info_resume.text for full-text search. Show the applicant a review step if your flow has one.
- 4
HireLayer
Step 4, HireLayer API: Extract job criteria once per job
When a recruiter publishes a job, send its description with your job id. HireLayer stores it with weighted criteria recruiters can adjust before scoring.
POST /api/v4/jobs/extract-criteria
- 5
HireLayer
Step 5, HireLayer API: Explain fit for each application
Send the application id with the job id. Save score, verdict, summary and criteria with the application.
POST /api/v4/resumes/score
- scores[].score
- scores[].criteria[]
- 6
Your system
Step 6, your system: The recruiter decides
Your interface shows the statuses next to the CV. Knockout rules on mandatory criteria remain your product’s logic.