ATS résumé score, in 10 seconds.
Engineering recruiters scan résumés in 6 seconds. Their ATS scans them in milliseconds. We grade four dimensions an ATS actually weighs — parseability, keyword density, quantified impact, and action-verb strength — and tell you what to fix. Paste a job description and we also list the keywords from that posting your résumé is missing.
What we score, and why
- ATS parseability (0–25)
- Did our parser actually extract your text? Is your contact info readable? Image-only PDFs, exotic fonts, and tables routinely tank this score before a recruiter ever sees the file.
- Keyword density (0–25)
- Most ATSes weight keyword overlap heavily. We check against ~250 commonly-required engineering technologies (languages, frameworks, cloud, data, observability) and surface what's missing.
- Quantified impact (0–25)
- “Built X to handle 50k req/s” beats “Worked on scalability” every time. We count the % of bullets that include a measurable number.
- Strong action verbs (0–25)
- Bullets that open with verbs like Shipped, Reduced, Architected outperform “Worked on”, “Helped with”, “Was responsible for”. We measure the ratio.
- Job match (optional, separate from the 100)
- Paste any posting and we extract its keywords with the same extractor our tailoring uses, then report the percent your résumé covers and name the ones it doesn't. It reads technical keywords: languages, frameworks, cloud and data tools. Add a missing one only where you have the experience behind it.
Privacy: the file and any job description you paste are read in memory, scored, and discarded. We do not write them to storage, attach them to an account, or send them to any third party. The only telemetry we collect is the anonymized numeric score (used to chart score distribution, not tied to you).