HR evaluation with Jev
Inbound applications and tickets mix eligibility, policy questions, and messy free text. The ATS, payroll, and your employment counsel still own outcomes. Jev can score job-related criteria you wrote. It is not an ATS and must not become a proxy for protected-class decisions.
This unofficial page is the evaluation slice of the HR screening operations pack. Intent: apply the Jev (TypeSafe System One) decision model to HR screening operations evaluation. Primary search language: HR Jev evaluation. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Job-criteria Nouls with an explicit do-not-encode-protected-class lint — not a clone of an ATS or HR-screening product page.
HR use-case context
Evaluation for HR screening operations is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: screen gold from recruiters, work-auth gold, and whether a human would have held docs. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: HR screening.
Evaluation inputs
Replay the same contract you ship:
{
"app": { "id": "c-190", "text": "5 years Python; no work auth mentioned; relocating July." },
"role": { "must": "Python in production; authorized to work without sponsorship this cycle." },
"ticket": { "type": "inbound_app" }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- False auto-reject on a planted qualified canary (block ship)
- Missed hold_docs
- Override rate by recruiter — high override means criteria are wrong
Pair auto-act errors with handoff rate. If the screening worker never acts, you have not evaluated HR screening operations — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” HR screening operations score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For HR screening operations, treat auto_reject as the high bar (auto-rejecting a candidate or taking employment action). Tune on labels — see offline evaluation.
Evaluation and rollout notes
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your application or HR ticket texts. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the HR pack? Start with HR failure modes and HR production rollout. Cluster hub: Use cases.
Is this an ATS or hiring decision system of record? No. It is an unofficial typed-screening pattern. Employment law stays with you and counsel.
Can we score “culture fit”? We recommend you do not. Keep criteria job-related and lint for proxies.
What this page does not claim
- Not an ATS, not employment-law advice, not a fairness certificate.
- No quality-of-hire numbers.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.