What’s inside each export
- ✓Candidate reference ID & role title
- ✓Alignment score (0–100) with tier color
- ✓Skills verified with evidence snippets
- ✓Rubric dimension breakdown (Architecture, Concurrency, etc.)
- ✓Identified gaps & red flags
- ✓Generated interview question kit
- ✓Salary context & market band (Tavily-powered)
- ✓Compliance disclaimer + blind screening badge
{
"candidate_ref": "CAN-8420-DISTRIB",
"role_title": "Staff Backend Engineer",
"alignment_score": 0.96,
"blind_screening": true,
"skills_verified": ["Rust / Tokio", "Raft Consensus", "Kafka / ClickHouse"],
"rubric_assessment": { "architecture_impact": 5.0, "concurrency_depth": 4.9 },
"status": "Shortlisted — Ready for Human Confirm"
}FAQ — ATS integration
Which ATS platforms are supported?▾
Greenhouse, Lever, Workday and Ashby via validated JSON and CSV. Exports match their API schemas — no custom mapping required. Enterprise plans add bi-directional sync and webhook triggers.
What data is included in exports?▾
Candidate match score, matched skills with evidence, identified gaps, rubric breakdown, interview question suggestions and salary context where available — all validated via Pydantic.
Do we need to change our ATS workflow?▾
No. Export as spreadsheet or payload and import into your ATS; or use RecruitAI as the screening layer before candidates enter your ATS pipeline.
Is data kept in sync?▾
Trial accounts use 1-click exports. Enterprise plans support automated sync with rate-limited webhooks and idempotent upserts.