The Pay-Band Target Score, to Stretch, Match, or Hold

Before you rewrite a single bullet, you have to answer one question: which pay band are you writing toward? The band above you, the one you sit in now, or a step down to clear the screens. This guide is for job seekers about to rebuild a resume, profile, or portfolio, and it gives you a scoring model that turns your own evidence into a single target band, plus a documented call on whether to stretch one band up.

Most compensation-and-positioning advice starts one step too late. It assumes you already know your target band and only helps you signal it. It explains how companies build bands, not how a candidate picks which one to write toward without getting auto-rejected as over-budget or anchored a level too low. That upstream judgement call is what this guide scores.

Why the target band is the decision, not the details

The band you aim your materials at is the single choice that governs every downstream edit, because a resume written for the wrong band either reads as junior or gets screened out as overqualified. Pick the band first; polish second.

Two facts make this decision worth real thought. First, the seniority read is fast and shallow: a recruiter's first scan decides whether to invest the next 30 to 60 seconds, not whether to hire you. That means the band is set by a pattern-match, so you are aiming at how you scan, not how you interview.

Second, aiming wrong is expensive in both directions. Aim too low and you leave a band's worth of pay on the table and anchor every later number. Aim too high and you trip the overqualification filter, which is a resume-level decision that your stated willingness to take the pay almost never reverses. The whole point of scoring the band up front is to avoid both failures on purpose.

A resume written for the wrong band either reads as junior or gets screened out as over-budget, and you never learn which.

What a pay band actually is, and why one band up is smaller than it feels

A pay band is defined by three numbers - a minimum floor, a midpoint anchored to the market rate the organisation targets, and a maximum ceiling it will not normally exceed without an exception. Understanding the geometry between adjacent bands is what stops you from over- or under-aiming.

Here is the counterintuitive part. Midpoints step only 8 to 15 percent between adjacent grades, but the range spread - the distance from a band's floor to its ceiling - runs 40 to 60 percent for professional and managerial roles. Because the step is small and the spread is wide, the next band's minimum frequently sits below your current band's maximum. You may already be paid into the next band without a title change. "One band up" is set by geometry, not by ambition, and the geometry says the jump is often modest.

Overlap guidance conflicts across sources, and you should know that going in. One source puts healthy overlap between adjacent grades at 10 to 30 percent, another at 15 to 35 percent, and a third calls 50 to 60 percent common. I will not pretend there is a single number here. The practical takeaway holds regardless: with small midpoint steps and non-trivial overlap, the real distance to the next band is usually narrower than the title change suggests.

There is a second trap in the math itself. Sources disagree on whether to anchor band calculations on the midpoint or the minimum. Midpoint-anchoring is standard. If you compare a minimum-anchored source against a midpoint-anchored one, you will inflate your perceived position. Check which convention each source used before you line the numbers up.

The five dimensions that decide your band

Recruiters map four signal families - scope, title and trajectory, quantified impact, and recognizable employers - to a level, and replaceability decides how much leverage that level actually carries. Those become the five dimensions you score.

The first four come straight from how recruiters read. On a fast scan they look for quantified achievements, recognizable company names, scope indicators like team size or budget responsibility, and action verbs that signal seniority. Scope is explicit: does the title reflect leadership, budget ownership, strategy, direct reports. Trajectory is compared candidate to candidate, so two people with ten years each read differently if one climbed from coordinator to senior manager and the other held one level the whole time.

The fifth dimension, replaceability, is not on the resume at all - it is about the pool you are compared against. Scarcity can carry a stretch that skill alone cannot, and a deep pool erases the leverage of generic "I'm senior" positioning. This is where Refolk's index gives you a number most candidates never see.

Each signal proves something specific, and each has a failure mode where it is present but lying. Leadership without direct reports still counts - people lead through projects, matrix relationships, vendors, cross-functional teams, and subject-matter expertise - but only if the resume shows the leading, not just the title.

How replaceability rescales the whole call

Replaceability is the size of the pool you are compared against, and it changes the reading of identical evidence from "rare hire" to "over-budget" depending on how deep the band is. This is the dimension published guides omit, and it is often decisive.

Refolk's index of professional profiles lets you see the pool. Stepping from Senior to Staff/Principal in US software engineering cuts the comparable pool by about 65 percent. The same materials that read as one-of-many in the deep band read as scarce in the thin one - and scarcity is exactly what a stretch needs.

Geography rescales your leverage before your resume does. The US Senior pool is about 7 times the UK's, so an identical candidacy is far more replaceable in the US market. The same materials should be scored differently by location - not because the person changed, but because the pool did.

Before you commit to a target band, it is worth seeing who else sits in it. Refolk writes a resume from your own history and scores how well you fit a posting, and its index lets you check the pool at each level directly rather than guessing at how replaceable you are.

The scoring procedure, run end to end

Run these seven steps in order. The output is one target band on paper plus a written stretch decision with its evidence cited. Budget roughly half a day for the analysis and another two to four hours for the rewrite.

For the scoring in steps four and five, keep it simple and repeatable. Use this rubric so the composite is honest rather than aspirational.

Scope        (0 no ownership / 1 partial / 2 clear budget or team or decision rights): __
Trajectory   (0 flat / 1 one move / 2 steady climb across roles): __
Quant impact (0 none / 1 execution metrics / 2 ownership-scale metrics): __
Market data  (0 one source / 1 two sources / 2 three sources agreeing): __
Replaceability(0 deep pool, generic / 1 mid / 2 thin pool or rare skill): __
TOTAL /10: __

Band rule:
  0-4  = Hold. Write to your current band; fix gaps before aiming up.
  5-7  = Match. Current band is defensible; stretch only if one dimension is a clear 2.
  8-10 = Stretch candidate. Proceed to the stretch call below.

Making the stretch call

Stretch one band up only when documented level evidence carries it, because an above-band ask stops being a pay conversation and becomes a leveling conversation. The bigger number needs scope and trajectory behind it, not just a market chart.

The boundary is well documented. Applying one level down is usually fine if you can name a specific reason. Two or more levels down triggers the overqualification filter almost every time, and it is a resume pattern-match, not an interview judgement, so your willingness to accept the pay rarely reverses it. The same logic runs upward: stretch one level with evidence, and you clear the screen; overreach past it, and you get auto-rejected before anyone reads the detail.

What actually justifies the stretch, in order of strength:

Note the ceiling on positioning itself. The cleanest field evidence shows algorithmic resume rewriting raised hourly wages 8.4 percent and lifted first-month hiring likelihood by 8 percent. That 8.4 percent is roughly one midpoint step - enough to move within a band or just over an edge, not to skip a band. Treat it as the size of the lever, not proof that words alone jump you a level. And keep the boundary honest: that figure comes from a gig-platform field experiment and should not be presented as a general salaried-band result. A clean published "positioning moves you a full band" number is not established publicly.

Quantification deserves its own emphasis, because it is differentiating precisely because it is rare. Only 10 percent of resumes include measurable results, and experienced professionals are more than twice as likely to quantify than entry-level ones. A fully quantified resume out-signals about 90 percent of the pool on the exact dimension recruiters scan for scope. If your rubric score is borderline, quantifying real ownership is the cheapest move that pushes it up.

How this goes wrong: the failure modes

The scoring model fails in predictable ways, and each false positive looks like success until it costs you the role or the pay. Read this section before you trust your own composite - it is the most valuable part of the standard.

Overlap illusion. You treat one band up as a big leap, but with small midpoint steps and heavy overlap the real gap is small. The false positive is under-aiming, holding when you could match. Check by computing both bands' min and max, not just the midpoints.

Anchor-math mismatch. You use minimum-anchored math against a midpoint-anchored market and inflate your perceived position. Check which convention each source used before you compare a single number.

Two-levels-up screen-out. You stretch past one level and the resume pattern-matches "overqualified." The false positive is brutal: strong final-round-caliber candidates get auto-rejected before a human weighs them. Limit the stretch to one level and name a specific motivation for the move.

Vanity quantification. Numbers are present but not tied to scope or level, so a metric-heavy resume still signals execution, not leadership. Check that each metric attaches to ownership or scale, not just activity.

Single-source market claim. One salary tool gives a number you cannot defend, and the ask reads as a wish. Cite 2 to 3 credible sources; a single source is not enough to move the reader.

Confusing above-band with above-offer. A 10 to 20 percent ask fits inside most bands and stays a pay conversation. An above-band ask becomes a leveling debate. Check whether your target still sits inside the higher band's maximum before you decide which conversation you are starting.

Replaceability blind spot. In a deep pool - 168,606 US Senior software engineers in Refolk's index - generic positioning has no scarcity leverage. The false positive is "I'm senior" with nothing rare behind it. Check that a differentiator actually narrows you against the pool.

Trajectory gap. The same title held for years reads as a plateau even with real tenure. Check that the resume shows expanding scope over time, not accumulated years at one altitude.

Writing the materials to the chosen band

Once the band is set, rewrite the summary and every bullet to pattern-match that band's signals on a fast scan, then re-read the resume as a recruiter would in the first 30 to 60 seconds. The test is not whether the resume is accurate; it is whether the level is legible in one pass.

The flow is short and it is where the analysis pays off.

Front-load the markers. On a fast scan the summary and the top bullets carry the level, so ownership, budget or team size, and quantified outcomes belong there, not buried in the third role. This is exactly the work Refolk automates - it drafts a resume from your history, tailors it to each posting, and scores the fit - but the target-band judgement still has to be yours, because Refolk tailors toward the band you point it at.

Keeping the call current

Re-run the band score whenever the inputs move, because pool depth, market rates, and your own evidence all drift. A structural review of grades, spreads, and overlap is recommended every 2 to 3 years, and your personal read should not lag far behind.

Three triggers should send you back through the rubric. First, a new quantified outcome or a scope change - a bigger team, a real budget - can move your trajectory and impact scores enough to change the band. Second, a shift in the pool: the same materials read differently as a market thins or deepens, and by location, so re-check the pool if you start targeting a new geography. Third, a competing offer, which is the single strongest piece of stretch evidence and can convert a "match" into a defensible "stretch" overnight.

Recheck the market numbers against 2 to 3 named sources each time rather than trusting a cached figure, since posted ranges and midpoints move with the market. The mechanism is what to watch, not any one number: when midpoint steps stay small and spreads stay wide, one band up remains a modest, evidence-gated move - and that is the judgement this score is built to make cleanly, every time you reopen your resume.