By Peter Miller · Published February 6, 2026 · Last updated: September 15, 2026
11 min read
You nailed the interviews. The offer still landed below what you hoped, and nobody warned you the number was mostly fixed weeks ago. That's not because you didn't ask pretty enough. It's because most US employers set a salary band when the req opens, and the hiring manager spends the process deciding where you sit inside it, not inventing a new range on your last call.
You're not failing because you lack confidence. You're failing because you're negotiating like the range is a secret when it's usually written on a comp worksheet in Workday or Greenhouse before your screen. Before you type expectations into another portal field, check your resume for free against the posting so your proof lines match the level they're pricing. A mid-level band won't stretch for senior scope, and a senior band won't open for duty-list bullets.
Job searching while bills stack up is brutal. This page is for candidates, not HR policy slides. You'll see why bands lock early, when they actually flex, and what to do tonight so your next counter lands inside a range someone can approve without a two-week exception chain.
If the posting asks for a cover letter, don't paste salary wishes into paragraph one. Generate a cover letter that proves scope instead. Numbers come after they believe the level fit.
Quick Wins
- Read the posting level and geo line before you type salary on the form.
- Rewrite bullet one so scope matches the top third of that level, not your old title.
- Ask the recruiter for the band width once, after screen, not before every email.
- Counter with total comp pieces if base is pinned at max.
Why the band exists before you walk in
Finance and HR do not wait for your final interview to pick a number. When a hiring manager opens a req in Workday, they attach a job code, a location tier, and a approved salary range. That range reflects headcount budget for the quarter, internal equity with people already in the seat, and the level definition HR uses across the company.
The band is the guardrail, not the opening bid. Recruiters screen inside it. Hiring managers argue for a target point as evidence stacks. Executives only see exceptions when someone wants above max or a level bump. You are negotiating placement inside a corridor that already has walls.
Most candidates treat salary like a personality test. Employers treat it like procurement with feelings. The req carries a min, a mid, and a max. Strong proof moves you toward max. Thin proof settles near mid. That is the whole game before anyone mentions sign-on bonus.
Edge case: the posting lists a broad public range. That range is marketing as much as math. The real band on the req is often narrower. Use the screen to learn width, not to treat the footer number as gospel.
Edge case: you're internal. Internal transfer bands sometimes ignore external market spikes. Your current pay anchors harder than it does for an outside hire. Read internal mobility policy before you compare yourself to friends who joined from outside.
For how variable pay fits once base is capped, read total compensation vs base salary . Base is the spine. Bonus and equity are the levers when the band max is real.
How employers decide salary ranges on the req
Bands are built from four inputs you can reverse-engineer as a candidate: level code, job family, location tier, and budget pool. Your job is to show you belong at the top of that combo before you counter. Below: how each input shows up in your file and your calls, with before and after pairs you can copy.
Input 1: Level code beats job title on the business card
Two people called Senior Analyst can map to different levels in the HR system. The req carries a level code like P3 or IC4. That code sets the band. Your resume title is decoration until it matches the code's scope verbs: owns, leads, defines, ships.
Before: Resume title Senior Analyst. Bullet one: Responsible for weekly reporting and stakeholder updates.
After: Same employer, same dates. Bullet one: Owned forecast variance workflow for a twelve-rep region, cutting manual reconciliation from six hours to forty-five minutes in Looker.
The second file reads like top of band for many corporate analyst reqs. The first reads like mid. Same person, different placement inside the range.
Input 2: Location tier splits the same title
Remote tiers often pay by where you live, not where the HQ sits. A req opened in Tier 2 geo carries a lower max than Tier 1 even when the work is identical. Employers decide ranges per tier tables updated once or twice a year.
Before: Candidate in a lower tier state countered using a friend's offer in a Tier 1 city as the only anchor.
After: Same candidate asked which tier the req used, priced rent and tax difference explicitly, and countered at top of their tier with a sign-on ask for the first-year gap.
You won't move tiers with charm. You can sometimes move with a relocation clause or a re-level if scope is clearly above the code. Bring scope proof, not a COL lecture.
Input 3: Budget pool and headcount timing
Hiring managers receive a slice of headcount budget per quarter. A req opened in Q1 with fresh budget often has more room at max than a backfill req absorbing a frozen band from last year. Recruiters rarely announce that detail. They feel it when an offer stalls at mid without explanation.
Before: Composite ops manager accepted mid on the first offer because the recruiter said that's what they had.
After: Same candidate asked whether the role was backfill or net-new headcount, requested max base plus a six-month review clause tied to a shipped workflow metric already on the resume.
I've screened offers in Workday where the band was approved when the req opened and the hiring manager needed a comp exception packet to go one dollar above max.
Input 4: Internal equity inside the team
Even when market data screams higher, managers hesitate above what current teammates earn at the same level. Internal equity pulls offers toward mid. Your outside offer from a hotter company is a data point, not a veto, unless they planned for a premium hire flag on the req.
Before: Candidate led the counter with an outside offer number in email before the employer finished references.
After: Candidate shared the outside offer verbally after the employer named their top of band, then asked for match at max base plus sign-on to close the gap without re-leveling the whole team.
Copy-paste block: band placement script for recruiter screen
{`AFTER RECRUITER CONFIRMS LEVEL + GEO TIER:
"Based on the scope in the posting and my background leading [WORKFLOW/METRIC],
I'm targeting the upper part of the band for this level in [TIER/CITY].
Is the req approved through [BAND_MAX], or is base capped lower?"
IF THEY SHARE WIDTH:
"That fits if we can land near top of band. I'll send a one-page scope summary
that maps my last role to your must-haves before the hiring manager round."
IF BASE IS CAPPED AT MAX:
"Understood on base. Which of these is easiest on this req: sign-on bonus,
performance bonus target, equity refresh, or an earlier merit review date?"
ONE-PAGE SCOPE HEADER (paste under your name):
Role level on req: ___________
Top-of-band proof (3 bullets max):
1. Owned ___________ affecting ___________
2. Shipped ___________ measured by ___________
3. Coached / led ___________ without title inflation
DO NOT:
- Anchor on current pay in the first screen
- Name a single hard number before you know tier
- Counter with COL alone when scope still reads mid-band`}
Send the scope page as a plain PDF attachment or bullet email after the recruiter asks for materials. Keep it one screen. Hiring managers forward short proof to HR faster than a ten-paragraph essay about passion.
For questions that surface band width without sounding money-obsessed in round one, see what questions to ask at the end of an interview .
When the range breaks your assumptions
Bands are rigid until they are not. These exceptions show up often enough that you should plan for them instead of treating the first number as final law.
Hot skill shortages. Some reqs carry a premium flag for niche stacks. The posting still looks generic. The recruiter can confirm after screen. If your skills match a scarce combo named in the must-haves, ask whether the req includes a premium band before you accept mid.
Re-level mid-process. If interviews reveal scope above the opened level, the hiring manager can request a level bump. That is slow. Help them by documenting scope gaps in writing during debrief. Silence lets HR keep the cheap code.
Equity-heavy packages. Startups and public tech firms split cash bands from equity grants. A low base max on the req may pair with a refresh budget. Negotiate grant size and review cadence when cash is pinned.
Contract-to-hire conversions. Hourly caps do not map to FTE bands cleanly. Clarify the conversion level and band before you start, not at week ten.
Before: Candidate treated a posted wide range as a promise of max for average proof.
After: Same candidate treated the footer range as marketing, confirmed tier and level on the screen, and tied every counter point to a metric the hiring manager repeated in debrief.
Edge case: nonprofit and public sector reqs publish step tables. Negotiation is often which step you enter, not a custom band. Read the table in the posting before you import private-sector tactics.
Edge case: union roles. Base moves on schedule. Your room is placement on the step, overtime rules, and differentials. Do not burn goodwill asking for a private-sector counter pattern.
This won't fix applying to roles where your scope still reads one level down. It stops a qualified candidate from accepting mid when the req had headroom at max and the proof was already on the resume.
Match level before you name a number
Bands follow level fit. Run score your job match on the posting before the recruiter asks for expectations. If must-have scope words only appear in Skills, you're priced like mid-band while talking like max-band in the interview.
Then run HireFlow's free ATS resume checker on the same file. Workday and Greenhouse import Experience before they import your salary answer. A parser-clean bullet that proves ownership moves the offer point more than a confident guess on the phone.
Do this now: Highlight three scope verbs from the posting, rewrite bullet one, run the checker, then draft the band placement script before your next screen.
Run the band check tonight
How employers decide salary ranges is not a mystery ritual. Level, location tier, budget, and internal equity set the corridor before your first screen. Your work is to prove top-of-band scope early, confirm width once with the recruiter, and counter inside the window with total comp when base hits the ceiling.
Job searching is hard enough without treating every offer like a blank check. Open the req you care about. Rewrite bullet one with scope verbs from the posting. Run the match score and checker. Draft the band placement script before the next call so you're negotiating placement, not guessing.
- Read level and geo before you type salary on the form.
- Map proof to top third of the band, not your old title.
- Ask for band width once after screen, not in every email.
- Shift to sign-on, bonus, or review date when base is capped.
- Send a one-page scope summary the hiring manager can forward.
Open the posting you're targeting. Run a free ATS check , confirm bullet one parses and reads at the level they're pricing, then walk into the salary conversation with a counter someone can actually approve.
Read more
Frequently asked questions
Most US corporate bands are approved when the req opens, before the first screen. Finance sets a min and max for the job level and location tier. The hiring manager picks a target inside that window as interviews progress. You rarely invent a new band mid-process. You argue for the top of the one already on the req.
If the field is optional, skip it or write negotiable tied to scope. If it is required, use a range that spans the band you found in the posting or recruiter screen, not your current pay. Anchor on role level and location, not what you earned at a smaller title. A number typed too early can cap you before anyone reads bullet one.
Sometimes, but not by whispering in a hallway. They need a comp exception, a re-level, or a sign-on budget from a different pool. That takes days and a VP signature at many firms. Your move is to show top-of-band scope in writing before the offer, then ask for total compensation pieces if base is hard-capped.
Job family, level code, and location tier differ even when titles sound alike. A Senior Analyst in a revenue org often sits on a different band than a Senior Analyst in operations. Remote tiers split by state. Read the level in the posting and the geo line, not just the words on the business card.
It moves you inside the band, not outside it. Great answers justify the top third. Thin proof lands near the midpoint. If you want more than max base, shift to sign-on bonus, equity refresh, or an early review date. Those draw from other budgets that are not always frozen with base.