What a Match Score Actually Tells You (and What It Doesn't)

You paste in a job description, upload your resume, and a number comes back. 62. Or 81. Or 47. It's tempting to treat that number like a grade. It isn't, quite, and knowing what it measures is what makes it useful.

Our first two posts covered how applicant tracking systems read your resume and how to tailor it to a specific posting. This one is about the number in between: the match score, and how to read it without over- or under-reacting.

What a match score is measuring

A match score compares two documents: your resume and one job description. It asks a narrow question. How much of what this posting asks for can be found, clearly, in this resume?

In practice that comes down to a few things:

• Coverage. Do the skills, tools and responsibilities the posting names appear in your resume?
• Emphasis. Are the most important requirements backed by evidence near the top, or buried on page two?
• Language. Does your resume describe the work in terms a reader of this posting would recognise?
• Experience fit. Do your seniority and years in the relevant areas line up with what's asked for?

That's it. It's a measure of fit between two pieces of text, for one role.

What it doesn't tell you

A match score is not a measure of how good you are. A strong engineer with a resume written for a different kind of role can score badly against a posting they'd be excellent at. That's not a verdict on them. It's a sign the resume isn't showing the right evidence for this job.

It also can't tell you:

• Whether you'll get an interview. Referrals, timing, the number of applicants and the hiring manager's own priorities all sit outside the document.
• How well your resume is written. A keyword-dense resume can score well and still read badly to a human. The score is one input, not the whole review.
• How you compare to other applicants. The score is about you and this posting, not about the rest of the pile.

Why the same resume scores differently on different jobs

This catches people out. You score 78 on one Senior Developer posting and 54 on the next, with the same file.

Nothing is wrong. As we covered in the tailoring post, two postings with the same title can weight things very differently. One wants cloud infrastructure and on-call experience; the other wants front-end depth and design-system work. Your resume might hold evidence for both, but it can only put one set of things first.

A score that moves between jobs is the score doing its job. It's telling you which applications your current resume is already pointed at, and which ones need a tailoring pass.

What's a "good" score?

There's no universal pass mark, and anyone who gives you one is guessing. A more useful way to read it:

• High: your resume already makes the case for this role. Check it reads well to a human, then apply.
• Middle: the evidence is probably there but not visible enough. This is where tailoring pays off most.
• Low: either the role is a genuine stretch, or your resume is describing a different job. Look at what's missing before deciding which.

The middle band is the one worth your time. A score you can lift by reordering and rewording true information is the clearest sign of an application you were about to undersell.

How to use the score well

1. Score your resume against the posting before you edit anything, so you have a baseline.
2. Read the gaps, not just the number. Which requirements weren't found?
3. For each gap, ask: do I have this experience? If yes, make it visible. If no, leave it alone.
4. Re-score after editing. If the number moved because you surfaced real evidence, that's progress. If it only moved because you added words you can't defend, undo it.

That last step matters. The goal was never a higher number. It was a resume that shows the right person the right evidence for this job. The number is just a quick way to check.

Where ResumeLens fits

When you paste a job into ResumeLens, the match score comes with the reasons behind it: which requirements were found, which weren't, and specific suggestions for closing the gaps you can honestly close. Use the number as a starting point, and the gaps as your to-do list.