Seniority Band Scoring: Why It Caps at 70

A candidate with fifteen years in enterprise sales applied to a role built for two to four years of experience. Judge the resume purely on tenure and it should have topped the shortlist: strong background, obviously capable, more years than anyone else in the pipeline. It did not top the shortlist. It landed at 70, comfortably below several candidates with a fraction of the experience, and a recruiter reviewing the queue could see exactly why: the role never asked for the most experienced person available. It asked for someone who fit a specific band.

That 70 is not a penalty for being good at your job. It is what happens when a scoring engine is told, explicitly, what range of experience a role is actually built around, and a candidate’s real background falls outside it. The number is deliberate, and so is the fact that it is 70 and not zero.

Why “Most Qualified” and “Best Fit” Are Different Questions

Without a configured band, a scoring model has no way to know that a role wants two to four years specifically rather than “as much relevant experience as possible.” Left to its own judgment, more experience reads as a stronger signal, the same way it would on a resume being screened by eye for a senior role. That is the correct read for a genuinely open-ended senior hire. It is the wrong read for a role with a defined level, and a defined level is the norm, not the exception, once a role has been scoped around a specific band of seniority and a specific budget line to match it.

Once a band exists on the role, the question the scorer is answering changes from “how much experience does this person have” to “how well does this person’s experience match what this specific role needs.” Those are different questions with different right answers, and a fifteen-year candidate against a two-to-four-year band answers the second question worse than a three-year candidate does, no matter how strong the fifteen-year resume looks on every other axis.

Two Ceilings, Not One

The scoring ceiling is not a single cutoff. A candidate who reads as over the configured band, meaningfully more experienced than the role calls for but not wildly so, caps at 70. A candidate who reads as far over the band, or far under it on the other end, caps at 25, a level that sits below where most roles set their auto-reject threshold.

The gap between those two numbers is the point. A score of 70 keeps a profile squarely inside the range a human reviewer would actually look at, because a moderately over-qualified candidate sometimes is the right hire anyway, just not automatically the top-ranked one. A score of 25 signals something closer to a structural mismatch, someone whose actual experience sits nowhere near what the role needs, in either direction, and for whom a human review is far less likely to change the outcome. Two different scores exist because two different situations exist, and collapsing them into one flat penalty would have thrown away exactly the distinction a recruiter needs when triaging a long queue.

Why the System Does Not Just Reject Over-Qualified Resumes Outright

An easier design would have been a hard rule: if experience exceeds the band by some margin, reject automatically. That rule would have thrown away too much, because a meaningful share of the candidates it would catch have real, legitimate reasons for applying to a role below their prior seniority. A candidate deliberately stepping back from a demanding role for a health or family reason. Someone relocating to a new city where their prior title does not exist in the local market. A professional re-entering the workforce after a gap and choosing to restart at a level they can actually land quickly. None of these candidates are a mismatch in the way the scoring engine needs to worry about; they are a mismatch on paper only, and a flat auto-reject rule cannot tell the difference.

Recruiter sentiment on this reflects the same tension in practice. Most hiring managers say they are willing to consider an over-qualified candidate, even as a majority also worry those hires will not stay long once something better comes along. That worry is a real signal worth weighing, not a reason to skip the conversation entirely. Capping the score instead of rejecting the resume keeps the candidate in front of a recruiter who can actually ask about motivation, timeline, and compensation expectations directly, rather than letting a years-of-experience number make that call unilaterally before anyone has spoken to the person.

Academic research on how hiring practitioners actually evaluate over-qualified applicants backs up that instinct. A study on employer perceptions of overqualified job applicants found that hiring judgments about overqualification are shaped heavily by context, including the candidate’s stated reason for applying, not by the years-of-experience gap in isolation. A scoring number that flags the mismatch without deciding the outcome leaves exactly the room that context needs.

The Other Direction: Far Under the Band

The ceiling works the same way on the other side of the range, and it is worth naming directly because it is easy to focus only on the over-qualified case. Flip the earlier example around: eight months of experience against a role built for two to four years reads as far under rather than far over, and it caps at the identical 25 a far-over-qualified resume would hit. The two situations look nothing alike on a resume, one candidate has too little relevant history, the other has too much, but both land in the same place on the score because both represent the same underlying fact: the role was built around a specific range, and this candidate’s actual experience sits well outside it in either direction.

Treating far-under and far-over as mirrored cases rather than opposite problems keeps the scoring logic honest. A band is not a floor with no ceiling, or a ceiling with no floor. It is a range, and a range has two edges that both matter once a recruiter has taken the time to configure one.

Where the Ceiling Can Get It Wrong

The ceiling is a general rule, and general rules have edges where they do not fit perfectly. A role built around a 2 to 4 year band because that is what the budget allows will sometimes still benefit from an unusually strong candidate at six or seven years who is willing to take the role anyway, for reasons entirely their own. The score alone will not surface that possibility; it will cap the resume at 70 the same way it would for a less exceptional over-qualified candidate, because the scoring layer has no way to distinguish “unusually strong fit despite the mismatch” from “ordinary over-qualification” using resume data alone.

This is exactly why the ceiling caps a score rather than removing the resume from the queue outright. A recruiter who spots something worth a second look in a capped profile can still open it, still reach out, and still make the call a resume score was never going to be equipped to make on its own. The ceiling narrows the queue a recruiter has to work through by volume. It does not replace the judgment call at the end of it.

How the Ceiling Lands in Auto-Decide

Roles that opt into auto-decide thresholds auto-reject below one score and auto-fanout to interview above another, surfacing only the middle “Needs review” band to a recruiter. The ceiling described here changes which side of those thresholds a capped resume lands on, without ever touching the thresholds themselves.

A score of 25 sits below where most roles set their auto-reject floor, so a far-over or far-under candidate on a role with auto-decide enabled is likely to auto-reject the same way a genuinely weak resume would, without a recruiter ever seeing it. A score of 70 behaves differently. It is high enough that it usually lands inside the Needs review band rather than auto-advancing, which means a moderately over-qualified candidate gets a human look rather than either extreme. The two mechanisms were built independently, the band ceiling decides what the number is, auto-decide decides what happens once the number exists, but they compose cleanly because both operate on the same match score.

This is worth checking directly if you run both features on the same role. A recruiter who configured a band expecting every capped resume to land in front of them should confirm where the auto-fanout and auto-reject thresholds actually sit relative to 70 and 25, rather than assuming.

A Worked Batch: What a Recruiter Actually Sees

Picture a role with a 2 to 4 year band configured, running against a batch of 40 resumes. Most of the batch clusters where you would expect, scores spread across the matched range based on skills and relevance. Three resumes stand out at the extremes: one candidate at nine years, one at six years, one at four months.

The nine-year resume caps at 25, the same as the four-month one, because both are far enough outside the band to read as a structural mismatch in either direction. The six-year resume caps at 70, comfortably inside the moderately-over-qualified range rather than the far-over one. A recruiter scanning that batch sees two candidates near the bottom of the queue for very different underlying reasons, one with too little relevant history, one with too much, and one candidate sitting in the middle of the pack at 70 despite having the second-most experience in the batch. None of that is visible from a raw resume; it only becomes visible once the band has done its job of translating years into fit.

What Happens After the Score Lands at 70

A score of 70 is not the end of the review, it is the start of a more specific one. On the dashboard, a recruiter looking at a capped profile can see the underlying signal, that this candidate cleared the role’s skills and relevance checks but sits outside the configured experience band, rather than seeing an unexplained number with no context behind it. That is a materially different review than a generic low score, because it tells the reviewer exactly what to ask about: is this candidate applying for a considered reason, or did they simply apply broadly without reading the level.

Recruiters running a role with a configured band for the first time are usually surprised by how many strong-looking resumes land in the 70 range rather than the 90s and 100s they might expect. That is usually the band doing its job correctly, not a sign of a miscalibrated rubric. It is worth confirming this by looking at the actual score distribution for the role rather than assuming, since a rubric that cannot separate candidates at all can produce misleading clustering for reasons that have nothing to do with the experience band.

The Ceiling Only Exists Because the Band Does

None of this scoring behavior happens unless a recruiter has already configured an experience band on the role. The ceiling is downstream of that decision, not a separate setting to hunt for. A role with no band configured scores experience the way it always has, with no cap applied at either end, which means the 70 and 25 numbers described here are only relevant once a recruiter has deliberately told the system what range this specific role is built around.

That JD-level configuration lives alongside every other identity detail a role carries through its lifecycle: what happens when two roles share a parsed title, what happens when a role gets renamed mid-campaign, and what happens when a finished role eventually gets cleaned up. A band configured on a JD needs to survive all of that, the same way a label or a rubric does, because none of those actions are meant to reset the scoring decisions a recruiter already made.

If your own screening setup treats fifteen years of experience as an automatic win against a role built for two to four, that gap is worth checking before it costs you a candidate who accepts an offer and leaves within a quarter. Talk to us to see how the band and ceiling behave on one of your own roles.