What an ATS actually does with your resume
An applicant tracking system is a database with a parser in front of it. When you apply, the parser reads your file, splits it into fields (name, contact, roles, dates, skills, education) and stores the result. Recruiters then work inside that database: they search it, filter it, and rank it. Per Harvard Business School's Hidden Workers research (2,250+ executives surveyed), more than 90 percent of employers use such a system to make the first cut.
Two consequences follow, and this tool is built around both. First, parseability is binary: whatever the parser cannot read does not exist in the database, no matter how good it looked on the page. Second, convention is searchability: recruiters find candidates using standard section names, standard job-title phrasing, and the literal keywords of their posting. A resume can be beautifully written and still be unfindable.
Every check this tool runs
The score is not a black box. These are all 15 checks, rendered from the same definitions the scoring engine executes, grouped the way the report groups them:
Parse & structure (30 points)
- Readable text volume — enough extractable text to be a resume at all
- Standard section headings — Experience, Education, Skills, and a Summary the parser can recognize
- Contact details — an email address and phone number in plain text
- Employment dates — year ranges a parser can attach to roles
- Bulleted experience — accomplishments broken into list items, not paragraphs
Content quality (40 points)
- Length in range — 300 to 1,100 words, judged loosely without knowing your level
- Bullet length discipline — average bullet between 8 and 30 words
- Quantified evidence — share of bullets containing a number
- Strong bullet openers — share of bullets starting with an action verb
- Weak-phrase count — "responsible for", "duties included", "worked on", "helped with", "tasked with"
- No first-person pronouns — "I", "me", "my" stay off a resume
ATS formatting safety (30 points)
- Clean characters — smart quotes, ligatures, and decorative symbols that corrupt parsing
- Single-column layout signals — mid-line whitespace runs that suggest tables or columns
- Line integrity — extraction producing coherent lines rather than fragments
- Plain-text contact info — no "[at]"-style obfuscation a parser reads literally
One deliberate omission: this checker is job-agnostic, so it does not score keyword matching, because keywords only mean something against a specific posting. That comparison is the keyword extractor's job, and it is the step to run per application after this one passes.
What your score means, and what it doesn't
The bands are the ones the tool applies: 85 and up is ATS-ready, 65 to 84 means minor fixes, below 65 means structural work before you apply anywhere. The score measures exactly what the 15 checks measure: parseability and convention. It is deliberately not a prediction of interviews, a measure of how impressive your career is, or a match score against any job.
That honesty matters because score-anxiety is how this tool category misleads people. A 95 with weak content loses to a 70 with strong evidence every time a human reads them; the score's only promise is that the human gets the chance. Treat 85+ as "the machinery will not lose me" and put the rest of your effort into what the machinery delivers.
A worked example
Here is a condensed sample resume (an operations manager, two roles, standard sections) run through the real engine as this page was built. It scores 93/100 and grades as "ATS-ready" with 2 flagged items:
Length in a sane range — 2/6
184 words falls outside the broad 300–1,100 band. For a target tuned to your experience level, use the word count checker.
Weak phrases — 2/5
2 weak phrases found ("responsible for" and friends). Each one spends words claiming ownership instead of showing results.
Both flags are instructive. The length flag is honest about the sample itself: at 184 words it is condensed for this page, and the checker says so rather than grading on a curve. The weak-phrase flag caught "Responsible for overseeing" and "Worked on scheduling" — both real bullets above that spend their opening words claiming ownership instead of showing results, exactly the pattern the check exists to catch. A strong score with named, checkable flags is what the full report looks like for most working resumes.
Fixing what the checker finds
Each flagged item links to its fix, and the fixes fan out across this site's tools and guides, which is the way this page is meant to be used: as the hub you return to after each round of fixes.
- Character and formatting flags are what the plain text converter fixes in one pass: smart quotes, ligatures, and invisible characters normalized to safe ASCII.
- Length flags get a level-specific verdict from the word count checker, including which sections and bullets to cut first.
- Structure and content flags (missing headings, unquantified bullets, weak phrasing) are best fixed against a working model: the resume examples show standard headings and evidence-dense bullets for dozens of roles.
- Everything at once: the builder's templates pass the structural checks by construction — single text flow, standard headings, clean characters — so rebuilding there retires the whole formatting category in one move.
Then re-run the check. The loop of fix, re-check, fix is the entire method; each pass should retire a category, and two passes usually reach the 85 band.