Jev directory
CommunityJev Benchmarks & Evaluations
Jev Job Matching
Independent experiment scoring 400 real job postings against 30 fictional résumés with Jev, producing 12,000 evaluations in about 197 seconds for roughly $0.17, with a 100-posting answer key and an analysis of what the model got wrong.
- Stars
- 1
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
Highlights
- 400 real job postings from a public Kaggle dataset scored against 30 fictional résumés
- 12,000 candidate-job evaluations completed in about 197 seconds for roughly US$0.17
- Top 3 matched the answer key on 96 of 100 hand-checked postings
- Top 1 was 45/100 with the 1.5 cutoff and 60/86 without it
- All 14 postings with no suitable candidate scored below the cutoff and were called correctly
Questions about this entry
Short answers drawn from the linked project or page.
Run python avaliar.py. It compares resultados.csv against gabarito_claude.csv and recomputes the top-1, top-3, and none-detection numbers locally without contacting the API.
About US$0.17 in TypeSafe API credits. The run used 3,988,299 input tokens across 400 postings. You need your own key in a .env file, and the author paid for all calls with personal credits.
Each job posting description plus the 30 fictional résumés. The trap notes section of curriculos_ficticios.md, which describes expected behavior, is deliberately not sent to the model.
The CSV files and the fictional résumés are CC BY-SA 4.0. The Python scripts are MIT. The underlying postings come from the LinkedIn Job Postings dataset on Kaggle, also CC BY-SA 4.0.
It was tested with Python 3.14. Setup is a virtual environment plus pip install -r requirements.txt. A TypeSafe API key is only needed to re-run rodar_jev.py.
Most misses are seniority mix-ups: 16 of 26 top-1 misses without the cutoff. The 1.5 cutoff was also too high, since the median best score across 400 postings was 1.31 and 225 postings fell below it.
The answer key was labeled by Claude and only spot-checked by the author on a sample, so it is not fully human-labeled. Kaggle updates the source dataset, and model outputs can differ between runs and model versions.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.