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, in the header block
- Employment dates — a date range attached to each role so the parser can build your timeline
- 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
What the “What an ATS sees” panel shows
Above the checks, the report shows the structure a parser extracts from your text before any person reads it: the contact fields it could pull into their own columns, each role with the date range it attached, your education and skills as it filed them, and the lines it could not place under any recognized heading. Every check then points back at the exact lines behind its verdict, so a fix is a line number, not a guess. The panel is deterministic and runs in your browser; it models how parsers behave in general, not any one vendor's system.
What the file check adds for PDF uploads
A pasted resume can only be judged as text. An uploaded PDF is also inspected as a file, in the same pass that extracts its text, and the report shows what the file itself says: whether it has a text layer at all or is an image (scanned or printed to picture), what kind of fonts are embedded and whether their glyphs map to characters (Type 3 faces, the kind Chrome embeds for variable web fonts, are a common silent failure), where the text sits on the page (a multi-column layout is detected from positions, not guessed from whitespace), whether contact details fell into the header or footer zone that several parsers skip, and whether letter-spaced headings shattered into single characters. Those findings feed the relevant checks above, so a file-level problem lowers the score the same way a text-level one does. The thresholds come from our own extraction audit of 36 PDFs across five parsing engines.
AI rewrites, and where the free tier ends
Everything deterministic on this page is free without limit: the 15-check score, the parser panel, the file check, and the job-match report. The AI layers cost us real compute per run, so they are metered: AI feedback is free with a daily limit, and AI bullet rewrites — before-and-after versions of the bullets the checks flagged, grounded in your facts, never inventing a number — come with a generous free daily allowance (50 runs anonymous, 100 signed in) and more on Premium. Accepted rewrites travel with the import into the builder. Signed-in users can also save a report and see the score delta on their next run; Premium keeps the full history. The score itself is never gated and never will be.
How the job-match report is scored
The ATS score is deliberately job-agnostic: keywords only mean something against a specific posting, so scoring them blind would be noise. The optional match report under the score is where that comparison happens, and it is a second, separate number. Paste a posting and the report lists the hard skills, soft skills and qualifications it names (recognized from the same lexicon the keyword extractor uses, aliases included), marks each one stated or missing in your resume, and reports the share stated, weighted by how much the posting emphasizes each term: a skill under “Requirements” counts double one in the company blurb. 70% and up reads as a strong match, 45 to 69 partial, below 45 weak. Three requirement checks sit beside the percentage without changing it: whether a role title of yours matches the posting's title, whether your dated roles add up to the years it asks for, and whether your Education section meets the degree it names. Every matched keyword and every requirement verdict points at the resume lines behind it. The report is free, has no limit, and runs in your browser; run it once per application, after the structural score 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 single-column templates (9 of its 12) are built as one text flow with standard headings and clean characters, so rebuilding in one of those 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.