Salary Transparency Laws in 2026: How to Negotiate With the Range on the Table

You've seen that line on job postings more and more over the last few years. Sometimes it's helpful. Sometimes it's a 40-thousand-dollar shrug. And sometimes — more often than you'd think — the number you actually get offered doesn't match the number on the posting at all.

Salary transparency laws changed the negotiation game, and most job seekers haven't updated their strategy to match. This guide covers where the laws stand in 2026, what the research actually shows about their effects, and how to negotiate when the range is public — including what to do when the offer comes in below it.

Where the laws stand in 2026

Here's the landscape: 18 states plus D.C. have some form of pay-transparency law, though legal trackers count 16 that require a range in the posting itself (JD Supra / MarketWatch). The distinction matters — some states require the range right in the job ad, while others only require disclosure on request, later in the interview process, or at the point of hire. Virginia's law, for example, took effect July 1, 2026 (JD Supra), joining the growing list of states that moved this year.

The direction of travel is clear even if the details vary. And the laws are reaching further than many employers expected — many states' rules cover remote postings tied to workers in those states, so a company hiring nationally can't easily dodge disclosure by listing the role as remote. (More on that below.)

Which laws require the range in the posting vs. disclosure later?

This is the distinction most guides gloss over, and it changes what you can see as a job seeker. Pay-transparency laws generally fall into three buckets:

1. Posting-stage disclosure. The strictest version: the salary range must appear in the job posting itself. Think California, Colorado, New York, Washington, and the other states JD Supra's tracker counts in the "16 that require a range in the posting." You see the numbers before you ever apply.

2. On-request or interview-stage disclosure. Some jurisdictions require employers to provide the range when an applicant asks, or at a defined point in the hiring process — say, after the first interview or when an offer is extended. You have the legal right to the number, but you may need to ask.

3. Offer-stage / at-hire disclosure. The lightest version: the range (or the actual offered pay) is disclosed when employment terms are finalized. Useful as a check on what you're being offered, less useful as a planning tool.

Why does this matter for negotiation? Because your leverage differs. In a posting-stage state, you can benchmark the role against the market before investing hours in interviews. In a disclosure-later state, asking early — "Could you share the approved range for this role?" — is both legal and normal, and it forces the conversation onto specifics before you've anchored yourself low.

How do these laws cover remote roles?

Short version: in many cases, they do. States like California and Colorado wrote their rules to cover postings that could be performed by workers in the state — which, for a remote role open nationally, means the posting has to carry the range. Some employers tried to dodge this by excluding certain states from remote hiring ("not hiring in Colorado"), and a few still do. But the trend is toward coverage: if the job could be done from a covered state, the range goes on the posting.

Practical upshot for remote job seekers: treat the posted range as your starting data point, not the employer's final word — and know that a missing range on a remote posting from a covered-state employer is worth asking about directly.

What the research actually shows

The most interesting finding from the research is the gap between posted pay and actual pay — and it's the thing almost nobody in career media talks about.

An NBER working paper (Arnold, Quach & Taska) analyzing Colorado's 2021 law found posted salaries rose about 3.6%, while actual realized wages rose 1.3%. Let that sink in. When employers were forced to post ranges, the posted numbers went up noticeably — but what people actually earned moved less. The range on the posting and the number on the offer letter are related, but they're not the same thing. Ranges can widen, shift upward, or get padded in ways that look transparent without fully being transparent.

That doesn't mean the laws failed. A 1.3% real-wage gain across a labor market is enormous in aggregate — it represents real money in real paychecks. And the mechanism is exactly what you'd expect: when workers can see the range, lowball offers get harder to defend, and posting salaries crept up even for roles not directly covered (spillover effects).

But it does mean you should read posted ranges with a practiced eye. A wide range ($80K–$140K) tells you less than a narrow one. The top of a posted range is often aspirational — reserved for the candidate who checks every box plus some. And roughly a quarter of postings still skip the salary entirely even where disclosure rules apply: Federal Reserve Bank of New York researchers found roughly a quarter of adverts in early-adopting states still omit the salary — compliance is real, but it's not universal, so a missing range isn't proof of a bad employer (though a pattern of missing ranges is worth noting).

The bottom line from the data: transparency moved the market in workers' favor — posted and realized — but the range is a starting point for negotiation, not a promise.

How to negotiate when the range is public

Here's where most advice goes stale. The old script — "never name a number first" — assumed the employer held all the information. When the range is printed on the posting, that information asymmetry is gone, and your strategy should change with it.

Anchor to the range, not below it. The most common mistake I see: candidates treat the bottom of the range as the "real" number and negotiate upward from there. Don't. The range is the employer's own statement of what the role is worth. Your opening position should be justified within the range based on your qualifications — typically the middle to upper-middle for a strong fit, higher if you exceed the requirements.

Justify with specifics, not vibes. "I'm targeting $105K based on the posted range" is weak. "I'm targeting $105–$112K: I bring five years in this exact stack, I've led two migrations like the one in your roadmap, and comparable roles in this market are posting $100–$120K" is a negotiation. The range gives you the frame; your evidence fills it.

Remember the range isn't the ceiling on total comp. Base salary is one component. Signing bonuses, equity, remote-work stipends, title, review timelines, and PTO are all negotiable — and employers often have more flexibility there than on base. If they won't move on salary, ask what else moves.

If you're switching fields, position yourself deliberately. Career changers often undersell themselves into the bottom of the range out of gratitude for being considered. Don't. If you're moving into an adjacent field, target the lower-middle while making the case for your transferable skills — and frame the pivot properly on your resume so the hiring manager sees trajectory, not a discount candidate.

A worked example: negotiating inside a posted range

Let's make this concrete. Say you're applying for a marketing manager role posted at $85,000–$120,000. You have four years of experience; the posting asks for three to five.

Weak approach: "My salary expectations are flexible — I'm open to discussing." (You've just told them to offer the bottom.)

Strong approach: "Based on the posted range and my background — four years running paid campaigns at similar scale, including a 40% CAC reduction last year — I'm targeting $105,000 to $112,000 base. I'm flexible on structure if there's room in bonus or equity."

What this does: it names a number inside their own range (so you're not being unreasonable by their own math), justifies it with one concrete result, and opens a second front (bonus/equity) in case base is rigid. If they counter at $98K, you're negotiating within a $7–14K band, not starting from scratch.

The key insight: the posted range turned salary negotiation from a guessing game into a bounded discussion. Your job is to argue your position within the employer's own bounds — which is a much easier argument to win.

What to do when the offer comes in below the posted range

This happens more than it should. Patriot Software's 2026 survey of 1,000 U.S. adults who had applied for a job in the prior 12 months found 17% received an offer below a publicly posted range. Nearly one in five. So if it happens to you, you're not an edge case — and you have options.

The 17% problem: Patriot Software found that 17% of recent job seekers were offered less than the bottom of the range posted on the job ad (survey of 1,000 U.S. adults who applied for a job in the prior 12 months, 2026). A posted range is data, not a contract — but a below-range offer deserves a direct question.

Step 1: Ask, don't accuse. "I noticed the offer is below the posted range of $X–$Y. Can you help me understand the gap?" Sometimes there's a reason — the role was re-leveled, the range covers multiple seniorities, or (less charitably) the posting was aspirational. You need the reason before you can respond to it.

Step 2: Decide if the reason is legitimate. "This range covers levels 3 through 5, and we're hiring you at level 3" is a real answer — you can then negotiate within the level-3 band or ask what advancement to level 4 looks like and on what timeline. "The market shifted" without specifics is not a real answer.

Step 3: Counter with the range as your evidence. "Given the posted range starts at $X, I'd need us to get to at least $X to move forward — here's why my background supports it." You're not inventing a number; you're holding them to their own published math. In posting-stage states, this carries extra weight: the range was a legal disclosure, not a casual estimate.

Step 4: Know your walk-away. A below-range offer with a hand-wavy explanation tells you something about how this employer operates. Sometimes the right negotiation outcome is declining politely. The range gave you information — use all of it.

The salary history question is (mostly) dead — act like it

One more structural shift worth knowing: salary history bans are now in place in 22 states (HR Dive's tracker, updated April 28, 2026), plus a growing list of cities and counties. The old trap — "what did you make at your last job?" used as an anchor to keep your next offer low — is illegal across much of the country.

If an employer still asks where it's banned, you can decline politely: "I'm focusing on the value of this role — the posted range gives us a good frame." And even where it's legal, you're never obligated to answer precisely. Redirect to the range and your target. Your previous salary is the least relevant number in the negotiation; don't volunteer it.

Frequently Asked Questions

Do all states require salary ranges in job postings? No. As of 2026, 18 states plus D.C. have some form of pay-transparency law, but legal trackers count 16 that require a range in the posting itself (JD Supra / MarketWatch). Others require disclosure on request, at the interview stage, or at hire. Check your state's specific rule — "transparency law" doesn't always mean "range in the posting."

Can an employer offer below the posted salary range? It happens: 17% of recent job seekers received an offer below the posted range (Patriot Software, 2026 survey of 1,000 U.S. adults). A posted range generally isn't a binding contract, but in posting-stage states you can — and should — ask the employer to explain the gap and negotiate back up to the range.

Should I still negotiate if the salary range is posted? Yes — the range is a starting frame, not a final answer. Most candidates land somewhere in the middle to upper-middle based on qualifications. Failing to negotiate within the range leaves money on the table; the NBER data shows realized wages moved less than posted salaries, which means individual negotiation still matters.

What if the job posting has no salary range? First, check whether your state requires one — roughly a quarter of postings in early-adopting states still omit pay (Federal Reserve Bank of New York research), so noncompliance happens. If the law applies, you can ask directly. If it doesn't, ask anyway: "Could you share the approved range for this role so we don't waste each other's time?" It's a normal question in 2026.

Does salary transparency actually raise pay? The best evidence says yes, modestly. The NBER study of Colorado's law found posted salaries rose 3.6% and actual realized wages rose 1.3% — with spillover gains beyond directly covered roles. Transparency helps, but the gap between posted and realized pay means negotiation still does real work.

Sources: JD Supra pay-transparency trackers (2026); MarketWatch; Arnold, Quach & Taska, NBER working paper on Colorado's pay transparency law (posted salaries +3.6%, realized wages +1.3%); Federal Reserve Bank of New York research on posting compliance; Patriot Software 2026 survey (n=1,000 U.S. adults who applied for a job in the prior 12 months); HR Dive salary-history-ban tracker (updated April 28, 2026).