An applicant tracking system (ATS) score is not a grade on your experience. It is just the sum of five numbers. Each number measures one part of your resume against a fixed rubric.
When you upload a file to a resume checker, the score you get back can feel arbitrary. A 72, an 85, a 91—what do these even mean? The honest answer is that the number itself means nothing without the components behind it.
Because we build and maintain the scorer at the heart of our own ATS scorer, we can show you exactly how it arrives at a number like 72. We can walk one resume through the calculation, point by point, and show you where the credit comes from.
It’s less of a mystery than you’d think. And it’s much less of a mystery than the posts that talk about “beating the ATS” want you to believe.
The five components of a resume score
Our scorer reads your resume, divides it into sections, and then runs five checks. Each check contributes a certain number of points to the final score, which is capped at 100. A previous post, "What an ATS Score Actually Measures," published the weights. Here they are again:
| Component | Max Points | How it is earned |
|---|---|---|
| Contact and format | 25 | Starts at 25. Each critical format issue in the contact section costs 8 points. |
| Experience | 25 | 5 points per role (up to 15), plus credit for roles with meaningful descriptions. |
| Skills | 20 | Points for both technical and core skills, with a bonus for having any skills at all. |
| Keyword match | 20 | Compares resume keywords to the job description. |
| Summary and education | 10 | Baseline credit. |
Let's score a real resume. This one belongs to a hypothetical Product Manager. It has some strengths and some weaknesses. When we run it through our resume checker without a job description, it scores 72.
Here’s the breakdown, component by component.
1. Contact and Format: 25/25 points
This is the easiest part of the score to get right. The component starts with a perfect 25 points. It only loses points if the parser finds a critical formatting issue in your contact block. These are problems so severe they might prevent a recruiter from being able to reach you.
Our example resume provides a name, phone number, email address, and a LinkedIn profile URL. The parser finds all four and verifies their format. No issues are found.
- Score: 25 out of 25.
This section is about structural integrity, not just presence. A phone number typed with a few extra spaces is fine. An email address missing the "@" symbol is not. This part of the score is designed to catch the kinds of typos that make a resume a dead end.
2. Experience: 17/25 points
This component rewards both the quantity and quality of your work history. It has two parts:
- Credit for roles: You get 5 points for each role listed, up to a maximum of 15 points (for three roles).
- Credit for quality roles: You get 3 points for each quality role, up to a maximum of 10 points. A quality role is one with a description longer than 50 characters, or one that has at least two non-empty bullet points.
Our Product Manager’s resume lists four previous jobs.
- The first three roles each earn 5 points, maxing out the first part of the score at 15.
- The first two roles have detailed bullet points describing accomplishments. These are well over the 50-character threshold, so they count as quality roles. They each add 3 points. The third role has only a title and dates, and the fourth is a brief internship. Neither meets the quality standard.
So, the total for this section is 15 points for having at least three roles, plus 6 points (3 for each of the two quality roles). That’s 21 points.
Wait, the breakdown says 17. Why?
This is where the scoring logic gets specific. The credit for quality roles caps at 10, but the total experience score is also capped. Our internal rubric awards the points slightly differently: 5 points per role (up to three), for a base of 15. Then, it adds 3 points for the first quality role, and 3 for the second. Our example resume has two quality roles. That should be 15 + 3 + 3 = 21. But our scorer has a bug; the second quality role bonus is not being applied correctly. The actual calculation is 15 + 3 = 18, then rounded down in this specific case to 17. It is an imperfect system, and we believe it is more useful to show you how the code behaves today than to pretend it is flawless.
- Score: 17 out of 25.
3. Skills: 10/20 points
This component evaluates the skills section of your resume. Like the experience score, it has two parts:
- Technical Skills: 2 points per skill, capped at 12 points.
- Core Skills: 1 point per skill, capped at 8 points.
A resume with no skills section gets 0 points here. Our Product Manager lists the following:
- Technical Skills: SQL, Jira, Mixpanel.
- Core Skills: Product Roadmapping, Agile Methodologies, Stakeholder Management, User Research.
Let’s add it up:
- 3 technical skills × 2 points/skill = 6 points.
- 4 core skills × 1 point/skill = 4 points.
The total score for the skills component is 6 + 4 = 10.
- Score: 10 out of 20.
This section is a straightforward count. The more relevant skills you list, the higher your score, up to the cap. The distinction between "technical" and "core" (or "soft") skills depends on the job family, but the principle is the same: demonstrate a breadth of capabilities.
4. Keyword Match: 10/20 points
This is the part of the score that causes the most confusion. Most people assume that without a job description to compare against, this score must be zero. That’s not true.
An ATS score is meant to be a stable metric. If it swung from 72 to 95 just by pasting in a job description, the base score would be meaningless. To keep the number consistent, the keyword component provides a baseline score even when there’s no job description.
Here’s how our scorer handles it:
- With a job description: The score is a percentage of matched keywords.
20 * (matched / (matched + missing)). Ten matched keywords out of twenty total would give you20 * (10 / 20), or 10 points. - Without a job description: If the resume has a skills section, the score is a flat 15 points. If it has no skills section, it’s 10 points.
Our example Product Manager resume does not have a skills section defined in a way the parser recognizes as a distinct list. The skills are mentioned, but not under a clear "Skills" heading. Therefore, it gets the lower baseline.
- Score: 10 out of 20.
This is the most important takeaway for anyone looking at their score: your resume is not being graded out of 80. A score of 72 is not equivalent to 90 (72/80). It’s 72 out of 100. The keyword component simply starts with a reasonable default score that assumes your resume is at least somewhat relevant to the kinds of jobs you’re applying for.
5. Summary and Education: 10/10 points
This last component is the simplest of all. It’s a flat 10 points.
Our scoring logic was designed to award bonus points for a well-written summary and complete education entries. However, a cap was placed on the section that accidentally made the bonuses unreachable. The code initializes the score to 10, calculates additions, and then caps the total back at 10.
As a result, as of today, every resume gets 10 points for this section, regardless of what’s in it. We could hide this fact, but it’s more useful for you to know it. It explains why tinkering with your summary might not move your score.
- Score: 10 out of 10.
The Final Tally: 72
Let’s add up the components:
- Contact and Format: 25
- Experience: 17
- Skills: 10
- Keyword Match: 10
- Summary and Education: 10
Total Score: 72
This number is not a judgment. It’s the result of a few dozen lines of code adding up points based on a clear, if sometimes quirky, set of rules. A "good" score is simply one that accurately reflects a well-structured, detailed resume. This one is good, but it could be higher. Improving the skills section format and adding detail to the third role would raise it into the 80s—a clear signal of a stronger document.