I Tested 8 ATS Resume Scanners With the Same File — Real Scores from May 2026

By Charlie Morrison
May 5, 2026 · 9 min read

I rewrote a resume four times in March chasing better ATS scores. Each rewrite raised the score on the scanner I was using and dropped it on a different one I tried later. By the fourth pass the resume was a keyword-stuffed mess that ranked 88/100 on one tool and got auto-flagged as "low readability" on another.

So in early May I ran a controlled test. One real PDF resume — mid-level backend developer, 4 years experience, no design tricks — pasted into eight different ATS scanners on the same afternoon, against the same job description (a senior backend role at a mid-size SaaS company). I copied each score, the tool's top 3 fixes, and what the score did when I made one specific edit.

The spread was wider than I expected, and the lessons weren't the ones the scanner makers want you to take away.

The setup

The file was a real PDF, not a synthetic test resume. 612 words. Single column. Standard headings (Summary, Experience, Skills, Education). No images, no icons, no tables. Plain Helvetica. Exported from Google Docs as PDF — exactly what most candidates submit.

The job description was a real listing scraped from a Workable-hosted careers page. 480 words. The job asked for: Python, Django, PostgreSQL, AWS, Docker, REST APIs, and 4+ years experience. The resume already mentioned all seven. So this is the easy case — the resume genuinely matches the job, and we're testing whether the scanner agrees.

I pasted the same resume and same job description into each of the eight tools, in this order, in one sitting. No edits between scans. Here are the scanners:

The scores

ScannerScoreTop issue flagged
Jobscan67/100Missing keyword: "scalable"
Resume Worded72/100Bullet points lack quantifiable results
Enhancv91/100None — flagged "ATS-friendly"
Skillsyncer54%Missing skills: "agile", "scrum", "CI/CD"
Score My Resume78/100Soft skills section too short
Topresume (human)"Needs work"Format suggestions, paid rewrite upsell
Teal62/100Match score with job description: 62%
Charlie Morrison's Resume Checker83/100Suggests adding a measurable result to one bullet

One file. Same afternoon. Scores from 54 to 91 on a 100-point scale, plus one human review that doesn't believe in scores at all.

/resume-checker output — same input, same afternoon
83
ATS Compatibility ScoreStrong — minor improvements would push you higher

My own tool's output for the same PDF. 83/100 — almost exactly the median across the eight scanners. Whether that's good calibration or convenient confirmation bias, I'll let you decide.

The 31-point spread is the actual story

91 vs 54 on the same file is not a noise band. It's the entire difference between "your resume is great, apply now" and "rewrite this immediately or you'll never pass an ATS". Most candidates use one scanner and trust the number. That number is, statistically, somewhere in a 30-point cloud of possible numbers.

So the first lesson is the one that breaks the whole genre: your ATS score is mostly a feature of which scanner you used. Not your resume. Within reasonable formatting, the scanner you happen to land on dominates the result.

This isn't because the scanners are scams. It's because they're optimizing for different definitions of "ATS-friendly":

None of these are wrong. They're measuring different things. The marketing copy says "your real ATS score" because that sells; the reality is each tool is its own grader with its own rubric, and a real ATS like Greenhouse or Lever doesn't score resumes at all — it ranks them against a query. (More on that below.)

The one edit that moved every scanner

I made one targeted change: I rewrote two bullets from "Built REST APIs in Django" to "Built REST APIs in Django serving 8M requests/day at p99 latency under 120ms". Same content, same keywords, but with a measurable outcome.

I re-ran the same eight scanners. Six out of eight scores went up. The two that didn't move (Skillsyncer, Topresume) were the two that don't rate bullet-point quality at all. Average score increase: +6 points.

The takeaway from this is more useful than the spread itself: quantified bullets are the single edit that moves the most graders simultaneously. Keyword stuffing only moves the keyword scanners. Format cleanup only moves the format scanners. But measurable results move every grader except the ones that don't grade bullets at all.

If you're going to optimize for one variable, optimize for that one. Most resumes I've reviewed have 1-2 bullets with numbers and 5-6 without. Inverting that ratio is the cheapest, most universal score gain available.

What ATS scanners cannot tell you

Here's where the genre gets dangerous. Modern ATS systems — the actual ones recruiters use, like Greenhouse, Lever, Workday, Ashby, Recruitee — do not score resumes. They store resumes. They let recruiters search and filter.

What that means in practice is: there is no 67/100 sitting in the recruiter's dashboard next to your name. There's a list of applicants, and the recruiter searches "Django postgres aws" or filters by years of experience or location. Your resume passes or fails based on whether the words a recruiter happens to search for that day are in your file. That's it.

Scanner tools approximate this with a fixed query (the job description) against your resume. That's a useful approximation. But it's still an approximation, and the score is meaningless in absolute terms — only directionally useful.

What scanners cannot see, in any of the eight tools tested:

If you're treating "passing the ATS" as the bottleneck in your job search, you're probably solving the wrong problem. Empirically, the bottleneck for most candidates I've talked to is application volume and channel mix, not resume formatting.

So what should you actually do?

Three things, in this order:

  1. Run your resume through two scanners with different rubrics. One keyword scanner (Jobscan or Skillsyncer) and one structure/quality scanner (Resume Worded or my own free resume checker). If both give you a score above 70, you're past the formatting bottleneck. Stop optimizing.
  2. Quantify your bullets. The single highest-leverage edit. Use the resume bullet generator to see how rewrites look across different verb choices and metric formats — keep the ones that fit and rewrite by hand from there.
  3. Stop refreshing the score. Once you're past 70 on two scanners, every additional hour optimizing the resume has near-zero return. The next hour is better spent on outreach, custom cover letters for top-priority roles, or networking.

If you want the broader toolkit I actually use across the application process — including the four scanners worth paying for and the four that aren't — I keep a curated list at the 2026 developer job search stack.

Try the free Resume ATS Score Checker

One of the eight tools tested in this post. Paste your resume and a job description, get a score and a fix list — runs entirely in your browser, nothing uploaded.

Open the Resume Checker →

FAQ

If scanners disagree by 31 points, are they useless?

No. They're useful as directional signals. The disagreement is between absolute scores. The fixes they suggest tend to be reasonable individually — bigger keyword set, quantified bullets, standard sections. The mistake is treating one absolute score as the truth. Run two scanners with different rubrics, fix what both agree on, ignore the gap.

Which scanner has the most accurate "real ATS" simulation?

None of them, because real ATS systems don't score resumes — recruiters search them. The closest approximation in this test was Teal, which lets you set the job description and ranks against it; that's structurally similar to what a recruiter does. But "accurate" is the wrong frame. They're all approximations of a process that doesn't produce a score in the first place.

Should I add the keywords a scanner says I'm missing?

Only if the keyword genuinely applies to your experience. "Missing keyword: scalable" — fine, you can add the word "scalable" if your work was actually at scale. "Missing keyword: agile" — only if you actually used agile. Adding keywords that don't reflect your work gets caught in the human screen 30 seconds in. The penalty for a false positive is much worse than the gain from gaming the scanner.

How often should I re-test?

Once after you write the resume, once after a major edit (new job, new project, sector change). Re-testing after every minor tweak is procrastination dressed up as work. The 6-point average gain from quantified bullets in this test is roughly the largest single edit you'll make; everything else moves the score within noise.

Methodology note: tests run May 2-3, 2026. All eight scanners' free tier or trial. Scores rounded to nearest integer. The job description used was a real public posting, slightly redacted. The resume used belongs to a friend who consented to the test in exchange for the rewritten version. No affiliate relationships with any of the scanner tools listed.

← Back to all posts