ATS resume checker
Upload your resume and a job description to see whether software can read it, which skills from the job are missing, and what to fix first.
Your resume never leaves your device.
Your score and fix list appear here.
What we check
The score out of 100 is our own weighted checklist, not any ATS vendor's formula:
- Can software read it? (20 points) Did text come out of the file at all; are there pages with almost no text (images or scans); garbled characters from icon fonts; two-column layouts; tables and text boxes (DOCX); more than 3 font families (PDF). We also flag length: Our rule of thumb for students and early-career engineers: one page is usual, two is the most.
- Contact details (10) Email, phone, LinkedIn and GitHub as plain text.
- Section headings (15) Standard headings on their own line: Education; Experience or Projects; Skills.
- Skills from the job description (30) We find the skills a job description mentions (with synonyms: "k8s" counts as Kubernetes, "Node" as Node.js) and check your resume for each. The skill list is shared with our skill pages.
- Numbers in bullet points (10) Full marks when at least half of your bullets include a result with a number.
- Action verbs (10) Full marks when at least 60% of bullets start with a verb like built, reduced or automated; weak phrases like "responsible for" cost a little.
- Consistent dates (5) One date format throughout.
Files are read in your browser: PDFs with a copy of pdf.js served from this site (it loads only when you pick a PDF), DOCX files with a small built-in reader. Nothing is uploaded and nothing is stored.
Last verified .
Questions
Does my resume get uploaded anywhere?
No. The file is read by your own browser, and the checks run there too. The page makes no network requests with your resume or the job description; you can turn off your internet after the page loads and it still works.
Is this the score an employer's ATS gives me?
No. Every applicant tracking system works differently and none publishes its scoring. This is our own checklist of things that commonly trip up resume parsers and recruiters' keyword searches, with the reason for each point.
Should I use a two-column template?
Safer not to. Many parsers read straight across the page, so a sidebar of skills gets mixed into your job history. A single column with clear headings reads correctly everywhere.
Should I copy every keyword from the job description?
Only the ones that are true. Add skills you really have, using the same words the job uses (for example "PostgreSQL" rather than only "SQL databases"). Interviewers will ask about anything on your resume.
PDF or Word?
Either works if it is a text PDF exported from Word or Google Docs, not a scan. If a company's portal asks for .docx, send .docx.