9 min read
Most candidates read the posted range, notice it's higher than their current salary, feel quietly encouraged, and then never mention it again.
That's the whole opportunity, wasted. Knowing how to use salary transparency laws to negotiate means treating a published range as evidence rather than as decoration. It's the employer's own number, in writing, for the job you're discussing. Nothing else you can bring to a negotiation is that hard to argue with.
None of it matters if you don't reach the conversation, so start there. Run your file through the free ATS resume checker and make sure a parser can read your titles, dates, and scope before you worry about the number.
Quick Wins
- Screenshot the posted range for every role you apply to, today.
- Write your expectations answer as a band, not a number, before the first call.
- Check whether your current employer is advertising your title. Save it if so.
Why a published range changes everything
Salary negotiation used to run on asymmetry. The employer knew the budget, the band, and what everyone else earned. You knew what you currently made and a rough guess from a salary estimate website.
A published range collapses part of that gap. Now you know the ceiling for the level before you speak, which changes three things at once: whether it's worth applying, what number you name, and how confidently you can hold it.
It also changes the tone. Quoting a published range isn't adversarial, because you're not making a claim about your worth. You're restating something the company already decided and published. That's a much easier sentence to say and a much harder one to dismiss.
The catch: a range is not an offer. Bands cover the whole role, and most new hires land in the lower half. Your job is to move within the band, not to assume the top of it.
Build your range file
Ten minutes of collection beats an hour of arguing. You're building a small evidence pack that you can quote from memory in a call.
- Find five current postings for the same title, same level, same metro or same remote tier. Five is enough to show a pattern and few enough to gather quickly.
- Screenshot each one, including the range and the date. Listings come down, and a link that 404s is worth nothing in week six of a process.
- Write down three numbers: the lowest bottom, the highest top, and the rough midpoint across all five. That midpoint is your anchor.
- Note which are base only. Commission-heavy roles distort the picture badly if you compare base to total.
- Include your own employer's posting if they're hiring for your title. That one is worth the other four combined.
For which states publish ranges and how the rules differ, the state-by-state guide covers the landscape. For everything published ranges don't show you, the total compensation breakdown is the other half of the picture.
How to use salary transparency laws to negotiate: the five moments
Published data is useful at five specific points, and it's used differently at each one.
| Moment | What the range does | Your move |
|---|---|---|
| Before applying | Screens out roles below your floor | Don't apply below your number unless the role justifies it |
| The expectations question | Gives you a band to quote instead of a guess | Answer with the upper half of the published range |
| At offer | Shows where the offer sits in their own band | Ask what moves it up, before you counter |
| The counter | Makes your number theirs, not yours | Anchor inside their range, justified by scope |
| Internal raise | Proves the role reprices without you claiming it | Quote your employer's own posting, calmly |
The expectations question is where most value is lost. Answer it with a number below the posted band and the band stops mattering, because you've just told them they can pay less than they budgeted.
Scripts for each moment
The expectations question
"I've been looking at what this level posts at, including the range on this role. Based on that, I'm targeting $X to $Y. Where I land in that depends on the scope and the wider package."
When the offer lands at the bottom of the band
"Thanks, I'm genuinely pleased. I want to ask about the number rather than just accept it."
"The posted range for this role runs to $Y, and the offer sits near the bottom. What would move a candidate up the band? I'd like to understand whether that's about level, scope, or experience, because I think my case sits higher than this."
The counter, anchored to their own data
"Given I've run this exact process at scale before and I'd be picking up the vendor side from day one, I'd be looking for $Z. That's inside the range you published, in the upper half rather than the top."
"Inside the range you published" is doing a lot of quiet work there. It signals that you're being reasonable and that you've read what they wrote.
For the written version of the counter, the counter offer guide has full email templates you can adapt.
Using ranges for an internal raise
This is the most underused move in the entire subject. Many transparency laws cover internal postings, promotions, and transfers, not just external hiring.
Which means your own employer may be publishing, in public, what your job is worth.
Take a mid-level operations analyst who's been in post three years. Their company advertises the same title at a range starting above their current salary. That's not an opinion about their performance, and it's not a threat. It's a document their own employer wrote.
"I noticed we're hiring for my title at $X to $Y. I'm below the bottom of that. I'm not raising it as a complaint, I'd just like to understand where I sit in the band and what it would take to bring my pay in line with what we're advertising."
Save the posting first. Internal listings come down fast, and "I'm sure I saw it" is not evidence. If the answer is that there's no budget, the no-budget guide covers where to take it next.
Edge cases
The range is uselessly wide
A band spanning three levels tells you nothing on its own. Ask which level they're hiring at and where in the band a typical hire lands. That question often reveals the real range, which is much narrower.
You're in a state with no posting rule
Use other states' data anyway. If a national employer publishes a range for the same role in a covered state, that number exists and it's theirs. Adjust for location honestly rather than pretending metro rates apply everywhere.
The recruiter says the range is "just a formality"
Push politely. Ask what the actual hiring range is for this requisition. If a published range genuinely doesn't reflect the budget, that's worth knowing early rather than after four interview rounds.
You're currently paid far below the band
Don't volunteer that. Anchor entirely on the published range, and if you're asked what you currently earn in a state with a salary history ban, redirect to your expectations instead.
They ask where you got the numbers
Answer plainly. "Current postings for the same title in this metro, including yours" is a complete answer and needs no defending. You're not citing a rumour or a salary estimate site with unknown methodology; you're citing published job adverts, which is the most verifiable source available to either of you. If a recruiter pushes back on live postings as evidence, that itself tells you something about how the rest of the negotiation will go.
Commission or equity-heavy roles
A posted base range can hide most of the compensation. Ask for on-target earnings and what percentage of the team actually hits target, because the second number is the one that matters.
Mistakes that waste the advantage
- Naming a number below the published range. It happens constantly, and no employer will correct you upward.
- Quoting the range aggressively. "You said up to $Y" puts people on the defensive. "The range runs to $Y" doesn't.
- Assuming the top is available. Expect the middle, argue for the upper half, and treat the top as an outcome rather than a starting point.
- Not saving the posting. The single most common practical error.
- Ignoring everything except base. A slightly lower base with better benefits and real bonus can be the better offer.
- Treating the range as the end of the research. A band tells you the span for the level. It doesn't tell you which level they're hiring at, which is the question that actually decides your number. Ask it early, because being assessed one level up moves the whole band rather than your position inside it.
- Waiting until the offer to mention any of it. By then the level is set, the approval is drafted, and you're arguing at the margins. Raise your range early enough that it shapes the offer rather than challenges it.
Get to the negotiation first
Every tactic above assumes you have an offer to negotiate. Getting there is still the hard part, and it's decided by screening you never see.
Upload your resume to the free ATS resume checker and look at what actually parses. Roles priced at the top of a band expect visible ownership and scale, so if your file reads as a list of duties, you'll be assessed for the bottom of the range before anyone speaks to you.
Then aim at the right level. The job match score shows how close your file is to a specific posting, and the cover letter generator ties your scope to the seniority the range implies rather than to your old job title.
The short version
- How to use salary transparency laws to negotiate starts with a range file: five saved postings and a midpoint.
- Never name a number below the published band, and never assume the top of it.
- Your own employer's posting for your own title is the strongest evidence you will ever hold.
Do this today: screenshot the range on every role you're currently in process for, and write your expectations answer as a band.
Then make sure you get the offer at all. Check your resume for free so the negotiation actually happens.
Read more
- Salary transparency laws by state in 2026 — who's covered and what the rules say.
- Research-backed salary negotiation tactics — what actually moves an offer.
- Negotiating without competing offers — leverage when you have no other bid.
Frequently asked questions
Quote it as market context rather than as a demand. Say what the range for the role is across several current postings, say where your experience places you inside it, and name a number in the upper half. The published range does the arguing for you, which is exactly why it works.
Yes, and it is the strongest single piece of evidence you have. It is their number, published by them, for the job you are discussing. Reference it neutrally rather than accusingly, and have a screenshot in case the listing changes.
Ask what would move it up the band. That question is more productive than restating your number, because it forces a concrete answer about level, scope, or experience, and it gives you something you can actually address.
Yes. Three to five current postings for the same title, level, and location are strong evidence of market rate. Use the pattern across them rather than the single highest number, which is easy to dismiss as an outlier.
Often better. If your own employer is advertising your title at a range above what you earn, that is an internal fact published by your own company. Save the posting, raise it calmly, and ask where you sit in the band for your level.