Guide
What an ATS score is, and what it can actually tell you
An ATS score estimates how closely a resume matches one job description, usually as a percentage. It is calculated by comparing the skills, titles and terms in the resume against those in the posting. No third-party tool can read the employer's real system, so treat any score as a gap checklist, not a verdict.
Published
What is an ATS score?
An ATS score is a number — usually a percentage — expressing how closely one resume matches one job description. It is produced by comparing the content of the resume against the content of the posting: the skills named, the tools listed, the titles held, and the responsibilities described.
The name is slightly misleading, and worth unpicking before you rely on one. An applicant tracking system is the software an employer uses to receive, store, search and move applications through hiring stages. Most of what it does is administrative. The "score" is a matching feature layered on top — and when you get a score from a tool that is not the employer's own system, what you are seeing is that tool's reconstruction of the same comparison, not a reading from the employer's.
That distinction is the whole reason to read the rest of this page. A match score is a genuinely useful checklist of what your resume fails to evidence. It is not a prediction of whether you will be rejected.
How an ATS match score is calculated
Implementations differ, but almost all of them do the same four things in the same order.
1. Parse both documents into structured fields
The resume is broken into contact details, roles, dates, education and skills. The posting is broken into responsibilities, required qualifications and preferred qualifications. Everything downstream depends on this step succeeding — a resume that parses badly scores badly for reasons that have nothing to do with the candidate.
2. Extract the terms that matter from the posting
Not every word is a requirement. The terms that count are the named skills, tools, certifications and titles, weighted by where they appear — a requirement stated in the qualifications section is weighted more heavily than a passing mention in a paragraph about company culture.
3. Match those terms against the resume
Exact string matching is the floor. Better implementations also match synonyms and related terms, so "PostgreSQL" can satisfy a requirement written as "relational databases". This is where scores diverge most sharply between tools: a strict matcher penalises vocabulary mismatch that a semantic matcher forgives.
4. Weight and total
Matches are combined into a single figure, usually weighting required qualifications above preferred ones, and often weighting recency — a skill used in your current role counts for more than the same skill last touched in 2016.
What counts as a good ATS score?
There is no universal threshold, and any page that gives you one without naming the tool it applies to is inventing it. Scores are only comparable within a single tool, against a single posting. What is stable is the shape of the advice at each band.
| Band | What it usually means | What to do |
|---|---|---|
| Below 50% | Either the resume genuinely does not fit this role, or it failed to parse and the comparison never ran properly. | Check the parse first. If your roles and dates came through wrongly, fix the file before touching the content. |
| 50-65% | A real fit with a vocabulary problem: you have done the work, described in different words. | Rewrite using the posting's own terms for the same things. This band moves the fastest for the least effort. |
| 65-80% | A solid match with specific, nameable gaps. | Address the two or three largest missing requirements, or decide knowingly that you will apply without them. |
| Above 80% | Strongly matched. Further points are usually bought with keyword padding rather than substance. | Stop optimising and spend the time on the covering note and on the interview. |
The most common error is chasing the last fifteen points. Past roughly 80%, the edits that raise a score are the edits that make a resume worse to read — and the human reading it in the second pass is the one who decides.
What an ATS score cannot tell you
Four limits, all of which matter more than the number itself.
- It is not the employer's score. No external tool has access to the employer's configuration, weighting or shortlisting rules. Any score you see outside their system is a reconstruction.
- It does not predict rejection. In most configurations an application is not auto-rejected on a score. Scores rank and filter to help a human decide.
- It cannot judge quality. A score measures overlap in vocabulary and structure. It has nothing to say about whether your achievements are impressive, your writing is clear, or your experience is real.
- It ignores everything outside the file. Referrals, prior contact with the company and portfolio work routinely outweigh the resume comparison entirely.
Used as a gap checklist, a match score is one of the most useful things you can run before applying. Used as a verdict, it is misleading in both directions.
How to improve a low ATS score
In rough order of return per minute spent:
- Fix parsing first. If the tool read your job titles as body text or lost a role entirely, nothing else you do will help. See ATS-friendly resume format.
- Adopt the posting's vocabulary. Same work, their words. This is where most of a low score actually lives — see resume keywords.
- Add the missing evidence. If a required skill is genuinely part of your history but absent from the file, add the bullet that demonstrates it.
- Reorder for relevance. Promote the experience closest to the posting to the top of each role.
- Cut the irrelevant. Removing unrelated content raises the proportion of the document that matches, and makes the match easier for a human to see.
What does not work: keyword lists, hidden text, and copying the posting verbatim. Those are covered in how to get past an ATS, along with the widely repeated statistics about ATS rejection that turn out to have no source.
Why two tools score the same resume differently
Because they disagree about all four steps above. One matches strings, another matches meaning. One weights required qualifications at twice preferred, another at four times. One penalises a two-column layout it could not parse; another linearises it cleanly and never notices.
The practical response is to stop treating the number as the output. Read the gap list instead — which specific requirements the tool could not find evidence for. Two tools that disagree by twenty points will usually agree almost exactly on that list, and the list is the part you can act on.
tailorurCV reports the gap for that reason: what matched, what is missing, and what to fix first, before you apply rather than after.
Sources
- Wikipedia — Applicant tracking system — what an ATS is, the functions it provides recruiters, and the parsing and search features that scoring is built on top of
- schema.org — JobPosting — the separation of skills, qualifications and responsibilities that matching is performed against
- Google Search Central — JobPosting structured data — the fields employers publish machine-readably, which is what makes automated extraction of requirements possible in the first place
Keep reading
- ATS resume checkers: what they test and what they miss
What an ATS resume checker can genuinely verify, what it can only estimate, and how to read one honestly — including why two checkers disagree about the same file.
- Resume keywords: finding them, placing them, and not overdoing it
How to extract the terms that matter from a job description, where to place them so they read naturally, and why stuffing a keyword list is worse than omitting it.
- How to get past an ATS (and what that phrase gets wrong)
An honest account of what applicant tracking systems do, which tactics survive contact with them, and why the most repeated statistic about ATS rejection is unsourced.
Score your resume against a real posting
Paste a job description and see the gap: which requirements are evidenced, which are missing, and what to fix first.