Reading a match score: what it tells you, and what it doesn't

A score is not a grade

A grade ranks candidates on a scale of worth. A match score does not: it measures the distance between what a job description asks for and what a resume demonstrates. An excellent engineer can score 48 % on a role that is not theirs, and that figure says nothing about their value — it says the pairing is poor.

The practical consequence is simple: scores compare only within the same job description. Comparing one candidate's score on role A with another's on role B means nothing at all.

Three questions behind a single figure

An overall score aggregates things of different natures. Telling them apart changes how you read it, because they are not fixed the same way:

• coverage: how many of the requirements leave a trace in the resume. This is the layer automated filters reproduce, and the easiest to game by pasting keywords;
• recency: when the resume demonstrates each skill. Kubernetes practised in 2019 and Kubernetes practised last year are not worth the same, yet a resume lists them on the same line;
• strength of evidence: what the claim rests on. A quantified achievement, a described assignment, or a line in a skills list — three very different degrees of credibility.

Why 66 % can beat 82 %

A candidate at 82 % with high coverage but purely declarative evidence has a well-written resume. A candidate at 66 % whose every critical skill rests on a dated achievement has a track record.

It is the disagreement between the layers that informs you, more than the total. Strong coverage with weak evidence describes a resume written with care. Average coverage with solid evidence describes someone who did the work but whose resume fails to tell it. The second situation is fixed in one interview; the first, not always.

Potential: what the resume hides

Part of the gap comes not from a missing skill but from an under-exposed one: a candidate who led a migration never wrote it down because it seemed obvious to them.

Hence the value of separating the observed score from the score reachable once the resume is clarified. The distance between the two is a work order — for the candidate rewriting their resume, and for the recruiter preparing interview questions.

What a score will never know

It knows nothing of motivation, of the ability to work with the team in place, of the context of a departure, or of what someone learned from a failure. It reads two documents, and nothing else.

That is a legal requirement as much as common sense: European regulation forbids a decision producing legal effects from resting on automated processing alone. The score prepares the decision; it does not make it.

In practice

Three habits are enough to get something honest out of it:

• read the gaps before the total: missing critical skills decide, not the two points between the third and fourth candidate;
• use the holes as an interview outline: an undemonstrated skill is a question to ask, not a verdict;
• never reject on the figure alone. A low score on an unusual profile often signals a badly written resume, which has nothing to do with the ability to do the job.