An ATS score vs a recruiter reading your resume
A score and a recruiter look at two different objects. The score reads a string of text and checks whether it is ordered, complete, and specific. A recruiter reads a story and asks whether it is worth a call. Confusing the two is how a resume gets optimised into something nobody wants to talk to.
- —You want to know whether the resume is worth reading, not whether it parses.
- —You are deciding between candidates or between two versions of a career story.
- —You need judgement about fit, which no rule set can supply.
- —You want to remove the mechanical reasons a file gets filtered before a human sees it.
- —You want the same answer every time you re-run the check.
- —You want specific failures, not general advice.
Side by side
01What the score can see
02It can see whether the text layer came out in a usable order, whether the contact block is machine-readable, whether the posting's concrete terms appear, and whether bullets contain outcomes rather than duties. Those are properties of the document, and they are checkable without understanding your career.
That is also the limit. The score is not measuring whether you are good at the job. It is measuring whether the document survives the step before a person reads it.
What it cannot see
03- —Whether the achievements are impressive, only whether they are specific.
- —Whether the career story makes sense, only whether the sections parse.
- —Whether you are a fit for the team, which is a judgement no document score can make.
- —Whether the employer's actual filters will pass you, because those are not public.
What a recruiter actually does
04The first pass is fast and shallow: title, company names, dates, and the first line of each role. If nothing there matches the role, the rest is not read. That is not laziness; it is the only way to process a stack.
The second pass is where the score stops helping. A recruiter is looking for evidence of scope and a reason to believe the numbers. A resume can pass every rule on this site and still fail that pass, because the rules describe mechanics, not substance.
How to use both
05- —Run the score first and fix the mechanical failures. There is no reason to lose on formatting.
- —Then read the file as a stranger would: cover the name, read the top third, and ask what this person changed.
- —Then tailor per posting. The keyword layer only exists when there is a posting, because coverage is relative to what was asked.
The trap
06Optimising for a score to the exclusion of a reader produces resumes that are 100 out of 100 and unreadable: forty nouns in a skills line, every bullet ending in a percentage, no narrative. The score is a floor, not a target.
The useful habit is to treat anything above the mechanical threshold as good enough, and spend the remaining effort on the story a person will read.
Score, verdict, and the three rules costing you the most points. No account, no card.