Recruitment Operations API
Structure job requirements, extract resume facts, and explain candidate matches. Scores are not hiring decisions.
Read Title, Requirement, and Responsibility lines into explicit requirements. Unlabeled prose is not turned into a requirement, and a requirement counts toward a score only when it is marked required.
Read Skill, Role, and Qualification lines. Personal-attribute lines and references are ignored and are not stored.
Compare supplied skills, qualifications, and role dates with explicit required items. A caller alias is marked inferred. A responsibility is not marked met.
Compare supplied skill names across candidates and against an explicit skill list. Missing skills are not invented.
Check supplied employment dates for invalid dates, overlaps, and gaps. Dates are not rewritten, and a gap is not a ranking penalty.
Draft questions from missing required items, inferred alias matches, and job responsibilities. The questions do not score the candidate.
Score candidates only from explicit required matches. An exact match is worth 2 and a caller alias is worth 1. Ties keep the caller's order.
Combine the job requirements, resume facts, match explanations, experience checks, interview prompts, and shortlist scores. The report is not a hiring decision.