9 min read · Posted bands change the script
The posting lists $98,000 to $118,000. You still answer the form with $95,000 to $115,000 because an old blog told you to bracket low and hope they'll split the difference. They won't. They'll treat $95,000 as the number you said you'd accept, and you'll wonder why published ranges feel useless.
Before you rehearse any line tonight, check your resume for free against the posting. The band you'll negotiate inside is often decided from scope on page one before anyone hears your bracket.
Job searching's already slow enough without handing away margin on autopilot. This page diagnoses why salary bracketing backfires when ranges are public, how to tell which mistake is yours, and what to say on Workday forms and recruiter screens instead.
And you don't need a policy lecture. You need a placed number, a consistent repeat, and a resume that reads at the level the top of that band assumes.
Quick Wins
- Open the posting and write one target number about two-thirds up their band.
- Reuse that exact figure on the application, recruiter call, and hiring manager chat.
- Stop talking after you say the number. Silence beats a self-discount qualifier.
When posted ranges make salary bracketing pointless
The symptom is a public band and a private discount. You see the employer's range, then quote your own wider bracket anyway. The screen ends at the bottom of your range, not the middle. You leave thinking transparency changed nothing.
Salary bracketing assumed both sides hid numbers. Your range was a probe for overlap. When the posting already shows a band, your bracket doesn't discover pay. It only tells them how cheaply you'll talk.
The old script also assumed someone would split the difference. Hiring managers pick the lowest figure inside budget that you offered. The bottom of your bracket is the only number that binds you.
For which states push employers to publish ranges and how that shows up on remote reqs, read salary transparency laws by state . This page stays on what you type once a range is visible.
Why salary bracketing fails now: three causes and what to do instead
Cause 1: You bracket against a range that's already public
Symptom: the posting shows a band. You still answer with a self-invented range starting below it. The recruiter stops at your floor.
How to tell: screenshot the posting range before the screen. If your bracket bottom sits under their published low, you discounted yourself against public data.
Before: Posting shows $98,000 to $118,000. You answer $92,000 to $110,000 on the form.
After: You answer $112,000 base, noting it sits inside the posted band given your scope on the vendor side from day one.
Fix: pick one number about two-thirds up their band. Attach one sentence of scope proof. Repeat the same figure everywhere the process asks.
Cause 2: Wide ranges read as flexibility, not ambition
Symptom: you quote a twenty-percent spread to sound reasonable. They anchor at the bottom every time.
How to tell: if your spread is wider than roughly eight percent without a level fork, you're bracketing against yourself, not the market.
Before: "$90,000 to $115,000 depending on role" on a mid-level analyst req with no level question attached.
After: "$104,000 to $108,000 base aligned with posted band; final figure depends on bonus structure and level placement."
Fix: tighten the spread or switch to one number. If you truly need room, tie the fork to level, not vibes.
Cause 3: You negotiate the number before the level sticks
Symptom: perfect phrasing on the call, offer still lands at the bottom of a band that was never big enough for your scope.
How to tell: your resume reads like the lower title in a bundled posting. The band spans two levels and you got priced into the junior one.
I've screened stacks of these in Workday and Greenhouse, and the offer band is usually set from title and scope on the resume before anyone hears your bracket on a phone screen.
Fix: rewrite bullet one with ownership, scale, and tools from the posting so you're assessed at the level whose band you want. Read how salary bands work when a posting bundles multiple levels in one wide range.
How to tell which cause is yours tonight
Run three checks in order. Compare your last answer to the posted band first. Measure your spread second. Read bullet one aloud third. If it sounds like duties, fix level before you polish scripts.
Copy-paste block: replacement lines when a range is posted
{`I saw the posted range of $[low] to $[high]. Given [one scope proof from your resume],
I'm targeting $[your number] base, which sits in the upper half of your band.
If nothing is posted: "What band did you budget for this level? I'd rather answer
from your range than guess."
After you state the number: stop talking. Do not add "but I'm flexible" unprompted.`}
Edge case: commission roles. Quote one base number. Ask OTE split and quota attainment separately. Edge case: agency screeners who filter on expectations. Ask the client's approved band before you answer, then place inside it.
Bracketing habits that anchor you low
Naming below the posted band. Nobody corrects you upward. They take the number you offered.
Adding "but I'm flexible" after your number. That's a discount before they asked for one.
Answering "what's your minimum?" Redirect to role value. It's bracketing in disguise.
Drifting down across form, screen, and manager. The last number you say is the one that sticks. Keep one figure unless scope changed.
Skipping the posting before the call. Two minutes of reading beats improvising a range under pressure.
This won't fix applying to roles you're underqualified for. It stops you from surrendering band margin when the employer already published the ceiling.
Screen into the right band first
Compensation talk happens after screening picks a level. Upload your file to the free ATS resume checker with the posting pasted in. If bullet one reads like duties, you'll get priced into the lower half of the band no matter how tight your bracket sounds.
Then run job match score on the same req. For top reqs, the cover letter generator can state seniority in prose without reopening a wide bracket. A thin match plus a high number triggers early rejection. A strong match plus one placed number inside the posted band keeps the conversation on scope, not suspicion.
What to say tonight
Why salary bracketing is dead in 2026 comes down to public bands. The employer already showed the frame. Your job is one defensible number inside it, repeated consistently, backed by level proof on the resume.
- Write one target from the posted band before you open the application.
- Replace wide brackets with a placed number or a tight range tied to level.
- Fix bullet one so screening puts you in the band you intend to quote.
Open the req you're furthest along with, pick your number, then run a free resume check so the band you quote matches the level they read on page one.
Read more
Frequently asked questions
Salary bracketing is the old advice to answer compensation questions with a range whose bottom is the number you actually want. Employers rarely split the difference. They treat the bottom as your acceptance floor.
The tactic assumed you did not know what the role paid. When the employer publishes a band, inventing your own range adds no information. It only gives them a lower anchor than the posting already showed.
Use one number placed in the upper half of the employer's published band when a range exists. Use a tight range only when nothing is posted, and make the floor a figure you would sign for happily.
Keep the spread narrow, anchored to posted data rather than comfort. Quote roughly five to eight percent around your target, not twenty percent. Add that the final figure depends on level and package.
Level assessment moves more money than arguing inside one band. A resume that reads at senior scope gets screened into a higher band before anyone talks numbers. Fix level proof first.