Layers (L1–L5)
Auto-advance and CV analysis toggles live on the job (dashboard Overview or Public API job update). AI analysis is plan-gated (Growth+).
If you are recruiting / ops
1
Add requirements
Open the job → Screening. Add must/should requirements (skills, years, tools, titles). Save.
2
Optional auto-advance
On Overview, enable auto-advance and set a minimum L3 score if you want high matches to move without a click.
3
Review ranked Candidates
The Candidates tab sorts by match score when requirements exist. Open a row for the brief and breakdown. Hold, advance, or reject.
4
Screened CVs
Org-wide queue: Screened CVs.
For engineers
Requirements
Replace body:
{ "requirements": [ … ] }. Each row uses kind (must | should), field (skill | years | tool | title | education | custom), key, label, optional weight, min_years, values, sort_order, is_active.
Screening result
GET returns the stored CVScreenResult, or runs a screen (without auto-advance) if none exists.
Rerun body (optional): { "action": "full" | "rerun_parse" | "rescore" | "rerun_brief" }.
Useful fields: status, l1_passed, l3_score, l3_breakdown, ai_brief, ai_red_flags, auto_advanced, screened_at.
Webhook
application.screened fires when L2/L3 finish (L4 brief may be present). Payload includes nested screening with status, l1_passed, l3_score, auto_advanced. See Webhook events.
Publishing a job ensures a pipeline cv_screen stage when a pipeline is linked. Advance can move the enrollment onto that stage.
Micro-task gate
Optional short platform task on the job (Overview → Micro-task gate). On advance, Assess invites that single-task assessment first. When the candidate passes, the full linked assessment invite is sent. Fail leaves them advanced without the full invite so a recruiter can decide next steps.Soft L4 usage
Growth+ orgs see CV analysis briefs (L4) counts on the Usage page (by_activity / total_cv_briefs). Report only — no per-CV credits.