A modern resume tool — including ours — will tell you a compatibility number between your resume and a job description. Usually a percentage out of 100. Most candidates look at the number and either feel anxious about a low one or relieved about a high one, without knowing what the score actually represents. The number is useful, but only if you understand what it measures and what it doesn't.

This post is about how compatibility scores work in practice. It applies to most modern tools, including Resumer's. The goal isn't to make the score the goal — it's to use it as one input among several.

What the score actually weighs

Different tools weight their scoring differently, but the major factors converge across vendors:

Roughly:

• 30% on vocabulary match. Does your resume use the same specific nouns (tools, methodologies, certifications) that the posting uses?
• 25% on experience fit. Years of experience parsed from dates, seniority match, role-level alignment.
• 20% on format / parseability. Can the parser actually read your resume? Single column, real headings, standard date format.
• 25% on recency and relevance. Is your most-recent experience relevant to the target? Are the most relevant items emphasized at the top?

A specific point: the vocabulary-match weight is high because it's the most predictive of what the actual ATS at the company will compute. A score that emphasizes other factors over vocabulary is calibrating to a different goal (recruiter readability, for example) — useful, but different.

What the bands mean

The number itself isn't the headline; the band matters more:

The 60–80 band is where most tailored resumes land, and where the marginal effort pays off most. Above 80, you're likely to clear the parser and the recruiter filter — small further increases don't change outcomes much. Below 60, no amount of last-minute tailoring fixes the structural mismatch.

A score of 95 isn't a goal worth chasing if it requires keyword-stuffing or padding. A 75 with credible vocabulary and clean format outperforms a 95 with stuffing every time, because the recruiter who reads the document spots the stuffing instantly.

Where the scores are right vs. where they mislead

Two specific patterns worth knowing:

The "stuffed but high-scoring" trap. A resume that loads every keyword from the posting into the skills section can hit a high compatibility score — and then read as obviously stuffed when a recruiter opens it. The tool sees keyword overlap; the recruiter sees a list of skills the candidate can't actually defend. Score chasing without honest fit is a fast track to a "claims expertise in X but can't talk about it" tag.

The "low-scoring but actually good fit" case. A resume might score 55 on a tool because it uses different vocabulary than the posting (you say "data warehousing," posting says "Snowflake") even though you've done the same work. The tool sees no match; the recruiter, with context, might. The fix is the vocabulary alignment — but the score isn't telling you the candidate isn't qualified; it's telling you the surface words don't align.

How to actually use the score

A workflow that produces better outcomes than "rewrite until the number goes up":

1. Run the score once on the draft you'd otherwise submit. This is your baseline.
2. Look at the breakdown, not the total. Which sub-score is dragging you down? Format, vocabulary, experience-fit, or recency?
3. Fix the biggest gap first. Format issues are usually fastest (single column, header fixes). Vocabulary is next. Experience-fit and recency are slower and may not be fixable per-application.
4. Re-run and compare. If the score moved by 5+ points and the bullets still read naturally, ship it. If you had to stuff to move the score, revert and ship the original.
5. Don't chase 95+. The marginal effort to go from 80 to 95 is rarely worth it — and often involves stuffing. Stop at "high band, no stuffing."

Specific gotchas

A few things to watch:

• Different tools score differently. A resume that scores 78 on one tool might score 65 on another. The absolute number is less meaningful than the band and the breakdown.
• The actual company's ATS may score differently than the tool. Tools approximate ATS scoring; they don't replicate any specific company's exact algorithm. Don't treat the score as a guarantee.
• Scores drift over time. Vendors update their scoring weightings. A resume that scored 82 last quarter might score 76 this quarter without you changing anything. Re-baseline periodically.
• One score doesn't generalize. A 78 on a posting for Senior PM at a B2B SaaS company doesn't predict your score on a Senior PM posting at an enterprise software company. Each role-and-company pairing scores independently.

When the score is most useful

The score earns its keep in three specific cases:

1. Format diagnostics. Catches parser-breaking format issues you'd otherwise miss.
2. Quick keyword audit. Surfaces specific terms you might add (where you actually used them).
3. Pre-submit sanity check. A 45 on a role you thought you were a strong fit for is a signal to re-read the posting — either you're misreading the role or your resume isn't surfacing what you've done.

When the score is least useful

A few cases where the score is noise:

• Senior roles with broad scope. The vocabulary match for a Director or VP role is less predictive — what matters is the narrative across multiple sub-skills, which scoring tools don't read well.
• Career-change applications. A pure compatibility score will be low because your previous work, by definition, doesn't match the target. The actual question — "is this candidate's underlying skill set transferable?" — isn't what the tool measures.
• Cold strategic applications. A targeted outreach to a specific person at a specific company isn't competing on parser score. Hit the relationship channel directly.

What this isn't

A few things this isn't:

• It's not anti-scoring. Compatibility scores are useful diagnostic tools. The argument is against treating the score as the goal.
• It's not specific to one tool. Different tools weight differently, but the broad shape of what scoring measures is consistent across vendors.
• It's not a substitute for the underlying work. A resume that's strong on its own merits will score reasonably; a weak resume can be pushed to a high score through stuffing but won't read well to the recruiter who eventually opens it.

The compatibility score is most useful as one of several inputs into a tailored application — not as a target to optimize toward. Use it to find structural problems, fix them, and ship.