Skip to main content

Candidate matching for recruitment teams

Match candidates to jobs using structured recruitment data

Turn a CV and job description into structured records, then inspect the components behind the match. Recruiters keep the final decision.

How a match is built

Job description

Parse the role into structured requirements, including job skills and experience fields.

Candidate CV

Parse the candidate into a profile with skills, experience, education and other available fields.

Reviewable match

Use the total score, component scores and evidence as a starting point for human review.

See more than one opaque score

The documented matching response exposes a total score plus separate components. The presence and value of a component depend on the data and matching request.

Skills
Compare extracted candidate skills with job skills.
Experience
Review experience alongside the role requirements.
Education and languages
Inspect separate components where the source data supports them.
Distance
See a distance component when location information is available.
Profile and context
Review profile, semantic and career trajectory fields exposed by the API.

A score helps prioritize review; it does not decide whether to hire, reject or contact a person. Confirm the role criteria and examine the underlying CV before acting.

Matching in your ATS or application

The API documents stored-resource matching and a file-to-file matching endpoint, along with a response containing score components and evidence. Teams can keep the review inside their existing workflow.