8 min read
Your offer number was picked before the recruiter liked your resume. US employers don't start from what you earn today and add a polite bump. They open a job grade in Workday, anchor near the band midpoint for that level code, and slide inside the approved min-to-max range. When the verbal offer feels like a lowball, you're often looking at the band floor for the level they priced you at, not a personal judgment on your worth.
Check your resume for free against the posting before you obsess over pay. A Coordinator headline on a Manager req gets priced at Coordinator grade even when your bullets scream scope. Fix level signals on the file first, then read the offer against the band logic below.
You'll still hear "we based it on your current compensation" on some calls. That's often recruiter shorthand for "you're inside the band we already approved." It's not the math they're running in the HRIS. Once you see how band midpoints and level codes work, you'll know when to counter hard, when to ask for a level change, and when the floor really is the floor.
Job searching is stressful enough without guessing whether an offer is insulting or just structurally tight. This page walks the employer side so you can diagnose your situation in ten minutes. No pep talk. Just the machinery behind the number on the call.
Quick Wins
- Ask which job level and grade the offer maps to.
- Compare the offer to the posted range, not only to your last paycheck.
- Counter with scope proof when you want a level bump, not only a bigger base.
- Treat band minimum as structural until HR confirms room above floor.
The symptom: the offer lands low and nobody explains why
The call usually goes like this: strong interviews, friendly recruiter, then a base number that sits at the bottom of what you hoped for. You wonder if you should counter 20% higher or if you'll look greedy and lose the offer. The silence in your head is worse than the number itself.
Three employer-side patterns explain most low offers: the req was approved at band midpoint for a conservative level code; internal equity holds new hires near existing team pay; or finance capped the grade at minimum for that headcount line. Your current salary is rarely the anchor on banded corporate reqs. The HRIS already had a min, midpoint, and max before your first screen.
I've watched hiring managers pick a level in Workday during intake, not during your final interview. Recruiter comp fields pull from that grade. When your resume headline reads one notch below the scope you discussed, the system prices the lower code. That's not a secret lowball. It's a level mismatch you can sometimes fix with a counter framed as scope, not ego.
Transparency laws put ranges on more postings now. Use them. An offer at the bottom of a posted band often means you're at grade floor, not mid-band target. An offer below the posted minimum means someone typo'd, mixed up levels, or you're looking at a different comp structure than you assumed. Clarify before you rage-counter.
How US employers decide salary ranges behind the scenes
The decision tree runs on grades, not feelings. Below are the three causes recruiters see most, with before/after examples and a fix for each.
Cause 1: band midpoint is the default anchor
Finance approves a salary range per job grade: minimum, midpoint, maximum. Recruiters are trained to target midpoint when the candidate fits the level without drama. Strong files sometimes land above midpoint with approval. Weak level fit or tight budget lands at minimum.
Before: Mid-level product analyst received verbal offer at band minimum. Assumed personal lowball. Never asked for grade or midpoint.
After: Asked recruiter to confirm level P3 and band min/mid/max in writing. Learned offer was at floor for P3 while scope discussed matched P4. Countered with bullet proof on roadmap ownership. Level moved, offer shifted toward new midpoint.
Signal you're here: offer sits at bottom of posted range, recruiter cites "approved compensation for this level."
Fix: request level code and band spread before you name a counter number. Negotiate level when scope supports it, not only base within the wrong grade.
Cause 2: level code in Workday priced you low
Workday stores requisitions with a job profile and compensation grade. Recruiters map your application to that profile during intake or after screen one. Title on the resume, years in the field, and manager title on the posting all feed the guess.
Before: Operations lead with "Supervisor" headline on resume received offer slotted as Grade 6. Peer team leads were Grade 7 with higher midpoint.
After: Sent one-page scope summary: headcount managed, budget size, systems owned. HR reclassified req to Grade 7 before written offer. Base moved without a hostile counter.
Signal you're here: posting title says Manager, your resume says Lead, offer feels "junior" for the work discussed.
Fix: align headline within one level of the posting before apply. At offer stage, bring written scope proof and ask for re-leveling, not a random higher number.
Cause 3: internal equity holds the band down
Hiring managers look sideways at existing team pay. Bringing you in far above tenured peers triggers compression reviews. Recruiters may open at band minimum even when you're strong, because the approved range for that grade is already tight against incumbents.
Before: Senior data engineer countered 18% above verbal because prior employer paid more. Recruiter said band max was lower than counter. Candidate assumed bad faith.
After: Asked for sign-on and review-at-six-months language instead of base above max. Total first-year package improved without breaking equity grid.
Signal you're here: recruiter mentions "alignment with current team" or "equity across the group."
Fix: trade base for sign-on, equity, or accelerated review when base is capped. Read total compensation vs base salary before you fixate on cash only.
How to tell which cause is yours
Copy-paste this triage before your next counter email:
1. Get job level and grade in writing from recruiter
2. Ask min, midpoint, and max for that grade
3. Compare offer to posted range on the original job ad
4. If offer equals band min: floor is real unless level changes
5. If headline was below posting title: suspect level mismatch
6. If recruiter cites team equity: ask sign-on or review path
7. Counter with scope bullets, not anger or last W-2 alone
Run those seven lines on paper before you send the counter. You'll know within five minutes whether you're fighting the band floor or a wrong level code.
Cause 4: headcount was budgeted at grade minimum
Sometimes finance approves a new req with instruction to hire at band minimum. Recruiter has little room until you prove level stretch or they pull an exception. This shows up on backfills after layoffs and on cost-control quarters.
Before: Marketing manager offer matched band minimum exactly. Candidate countered 12% without asking if exception budget existed.
After: Recruiter secured partial exception to midpoint after candidate shared competing written offer at higher band. No level change needed.
Signal you're here: offer equals band min on day one, recruiter sounds apologetic but firm, posting range was wide.
Fix: bring outside interest or niche skill proof. Give recruiter ammunition for an exception request instead of demanding they break policy on the call.
More before/after: reading lowball vs band floor
Before: UX designer treated offer at posted range minimum as insult, declined without asking midpoint. Role filled at same grade.
After: Different candidate asked if offer was min or target for L5. Learned team norm was min for external hires with six-month merit review. Accepted with review clause in writing.
Before: Financial analyst assumed current salary drove offer because recruiter mentioned "market alignment."
After: Requested grade sheet. Saw offer was midpoint for Analyst II while candidate self-identified as III. Re-level conversation moved base without a hostile email war.
For application-stage band mistakes, read why candidates get rejected over compensation . Offer-stage logic starts where apply-stage filters end.
Misreads that waste counters
Assuming current salary is the anchor. On banded reqs, grade midpoint drives the open. Your W-2 is context, not the formula.
Treating band minimum as an opening bid. Sometimes it is. Often it is the approved floor until level or exception changes.
Countering without knowing the level code. A bigger number on the wrong grade stalls in HR workflow.
Ignoring posted range position. Bottom of band feels bad but may be structurally normal for that employer.
Demanding mid-band without scope proof. Recruiters need a reason to go upstairs. "I want more" is not a reason.
Mixing OTE and base in your head. Employer bands may be cash-only while you're counting bonus from last role.
Negotiating before written offer. Verbal numbers shift. Get level and band on paper first.
Edge case: startup without published grades. Bands are looser, manager discretion is higher, but board approval still exists. Edge case: union or government steps. Midpoint logic gives way to fixed steps with narrow negotiation room.
Comparing employer bands to a friend's employer. Midpoint at Company A is not midpoint at Company B for the same title string.
Reading recruiter empathy as flexibility. They may agree you're great and still be boxed by grade until HR acts.
Skipping the sign-on ask when base is capped. Many teams have sign-on budget separate from base grid.
Exceptions: executive reqs where comp committees set custom packages. Sales roles where OTE band is the real structure. Internships with flat rates. In those cases, midpoint talk looks different, but level codes still matter for internal parity.
Level fit before pay talk
Paste the posting, then run a free ATS check on title and bullet one. Employers price the level they think you are. A parsed file with the right seniority language gives recruiters cover to slot the higher grade before the offer is built in Workday.
Scope box on the apply? Generate a cover letter that mirrors bullet one and states the level you are targeting. That gives recruiters cover to slot the right grade before comp is built in Workday.
Read the band, then counter
How US employers decide salary ranges behind the scenes comes down to grades, midpoints, and level codes in systems like Workday, not a whispered guess about your current paycheck. When an offer stings, diagnose whether you're at band floor, wrong level, or equity-capped before you send emotion in an email.
Run the copy-paste triage on your next verbal. Ask for level and min/mid/max in writing. Counter with scope when you need a re-grade, sign-on when base is capped, and patience when the recruiter is clearly boxing you honestly. That's how you separate a structural floor from a true lowball.
Keep a one-line note per offer: posted range, verbal offer, level cited, band position. Three rows and you'll stop repeating the same counter mistake on every company. The machinery is boring. Your notes make it visible.
For offer-stage scripts when you lack competing bids, read how to negotiate salary without competing offers . Band logic tells you whether there is room. Negotiation tells you how to ask.
Read more
Frequently asked questions
Less often in states that ban salary history questions, and less often on banded corporate reqs. Most US employers anchor to an internal grade midpoint and level code in Workday or a similar HRIS, then adjust within the approved min-to-max band. Your current pay may still matter as a data point on optional fields, but it rarely overrides a grade that was set before you applied.
The midpoint is the target number finance approved for a job grade. Recruiters are coached to open near midpoint when the candidate fits the level cleanly. Offers at band minimum usually mean the req was approved at the floor, the level code is conservative, or internal equity caps the room. Midpoint is the default anchor, not the ceiling.
Compare the offer to the posted range when you have one. An offer at the bottom of a wide posted band with no level discussion often is the floor for that grade, not a opening bid with huge upside. An offer below the posted minimum is a red flag to clarify in writing. Ask which job level the offer maps to and what the full band is for that level before you counter.
Sometimes, with HR and finance sign-off. It is not a same-day click in Workday. Large jumps need a level change, exception approval, or equity-heavy mix. Candidates who counter with scope proof and competing interest give recruiters something to take upstairs. Counters that ignore the level code usually stall.