US Pay Transparency Laws 2026: State-by-State Guide to Negotiating When Salary Ranges Are Public

If you're job hunting in the United States in 2026, there's a decent chance you've already seen it: a salary range sitting right there in the job posting, before you've even sent a resume. That's not an accident or a generous employer being unusually candid. It's the law. Pay transparency laws 2026 now cover roughly 16 states plus Washington, D.C., and the list keeps growing — Maine adds itself to the roster on July 29, 2026, with Delaware set to follow in September 2027.

For candidates, this is a genuine shift in leverage, but it's also a source of confusion. A posted range doesn't tell you where you'll actually land, whether it includes bonus and equity, or whether the company down the street is bound by a different set of rules entirely. And because these laws are state-by-state rather than federal, the exact same job title can come with mandatory disclosure in Denver and zero disclosure in Dallas.

This guide is the US companion to our breakdown of the EU Pay Transparency Directive, which standardizes disclosure rules across the European Union. Together, the two posts cover the two biggest pay transparency regimes in the world right now — one unified continental directive, and one fast-moving American patchwork that you have to track state by state. If you're negotiating in the US specifically, here's what the law actually requires, what a posted range does and doesn't tell you, and how to negotiate when the number is already sitting in front of both of you.

Why pay transparency laws 2026 matter more than ever

Pay transparency legislation isn't new — Colorado passed the first broad statewide law back in 2021. What's changed is the pace and the coverage. In the last eighteen months alone, New Jersey, Illinois, Minnesota, Vermont, Massachusetts, and Virginia have all added statewide requirements, and dozens of cities and counties have layered on their own local ordinances on top of state law.

The practical effect is that a large and growing share of the US job market now shows salary ranges by default. Estimates from HR compliance firms suggest that well over a third of the US workforce lives in a jurisdiction with some form of mandatory disclosure, and that share rises sharply for remote and hybrid roles, because a single national job posting often has to satisfy the strictest state law among all the places it could be filled.

There's still no federal pay transparency law. Congress has introduced versions of a national Salary Transparency Act in recent sessions, but none have passed, so the current system is a genuine patchwork — and that patchwork is exactly what candidates need to understand before they walk into a negotiation assuming the rules are the same everywhere.

The state-by-state legal landscape in 2026

Every state law differs slightly in who it covers, what triggers disclosure, and how it's enforced. Broadly, the laws fall into three buckets: states that require a salary range in the job posting itself, states that only require disclosure on request or after an interview, and separate pay-data-reporting laws that require larger employers to report aggregate compensation data to a state agency (which doesn't directly affect what you see in a job ad, but signals that the state is actively watching pay equity).

States requiring a salary range in the job posting

States requiring disclosure only on request or after an interview

Connecticut, Nevada, and Rhode Island take a lighter-touch approach: employers don't have to print a range in the ad, but they do have to hand it over once you ask, or in Nevada's case, once you've interviewed for the role. Practically, this means the posting itself may look identical to one from a non-transparency state — the difference only shows up once you actually engage with the employer, which makes asking directly a much more important skill in these three states than in a posting-mandate state.

Local ordinances layered on top

Even inside states without a statewide law, cities and counties have moved on their own. New York City, Ithaca, and Westchester County (all in New York) and Jersey City, New Jersey each have their own disclosure ordinances that predate or extend beyond their state's law. In Ohio — a state with no statewide requirement — Cincinnati, Toledo, and Cleveland already require disclosure, and Columbus joins them starting January 1, 2027. If you're job hunting in a state without a statewide law, it's still worth checking whether the specific city has its own ordinance before assuming nothing applies.

Pay data reporting: a separate but related requirement

California, Illinois, and Massachusetts also require larger employers to file aggregate pay data reports with a state agency, broken down by job category, race, and gender. This doesn't change what appears in an individual job posting, but it does mean these states are actively collecting evidence on pay equity, which raises the practical stakes for employers to keep posted ranges honest rather than treating them as a box-checking exercise.

The remote work wrinkle

This is the part that trips up the most candidates. If a remote role could plausibly be filled by someone living in a state with a transparency law — even if the employer is headquartered somewhere without one — that state's disclosure rules generally apply. A Texas-based company advertising a fully remote role that's open to applicants nationwide will typically need to comply with the strictest applicable law among the states where the role could be filled, which in practice usually means treating the posting as if it's covered by California, Colorado, or New York rules even if none of those states are mentioned anywhere in the ad. If you're applying remotely and a posting from a company in a non-transparency state still shows a range, this is almost certainly why.

What a posted range actually tells you — and what it hides

A posted salary range is real information, but it's easy to over-read it. Here's what's actually going on behind that number.

The range usually spans multiple levels, not just your level. A posting for "Senior Product Manager, $135,000–$185,000" is very often covering the full band from a newly promoted senior PM up through someone one step from director. Your actual position within that range depends on your years of experience, the scope of your last role, and how the hiring team levels you internally — not just on the job title.

"Good faith estimate" doesn't mean narrow. Most laws require the range to reflect what the employer genuinely expects to pay, and regulators in several states have signaled that absurdly wide ranges (say, $50,000–$200,000 for one role) may not satisfy that standard. In practice, enforcement has been inconsistent, and you'll still encounter wide ranges — especially on remote postings compliant across multiple states with different costs of living. A wide range is a cue to ask more questions, not a guarantee of flexibility at the top.

Base salary is not total compensation. The range you see almost never includes signing bonus, annual bonus target, equity or RSU grants, 401(k) match, or benefits value — and several state laws (Massachusetts and Minnesota among them) require only a general benefits description, not a dollar figure. Two postings with an identical base range can represent very different total offers once bonus and equity are factored in. Always ask what the range does and doesn't include before you compare two offers.

A wide range can also reflect real geographic pay differences. Companies that pay differently by location sometimes post one range wide enough to cover their highest and lowest-cost markets, then apply an internal locality adjustment once you're further along. Ask directly whether the posted range is adjusted for your location, or whether it's a single national band.

Negotiation scripts for a pay-transparent market

Having the range up front changes the negotiation conversation, but it doesn't eliminate it — it just moves the question from "what's the range?" to "where in the range, and what else is on the table?" Here's how to run that conversation at each stage.

Opening the recruiter screen

Use the posted range as your entry point instead of dodging the topic:

"I saw the posting lists $110,000–$140,000. Based on my background — [specific, relevant experience] — I'd expect to be positioned in the upper half of that range. Can you share where the team typically brings in someone with my level of experience?"

This does two things: it signals you've done your homework, and it gets the recruiter to tell you, before you've invested hours in the process, roughly where they see you — which is information they're often willing to share informally even in states that don't legally require it.

Asking about the range when it isn't posted

If you're in a state without a posting mandate, or the listing is vague, ask plainly rather than waiting:

"I don't see a salary range listed for this role — could you share the range you're working with before we go further? I want to make sure we're aligned before I invest more time in the process."

Framing it as mutual time efficiency, rather than an ultimatum, keeps this low-friction. In Connecticut, Nevada, and Rhode Island specifically, you're within your legal right to ask for this at any point in the process, and the employer is obligated to provide it.

When salary history comes up anyway

More than 20 states now ban employers from asking about your prior salary, and many of the same states pairing pay transparency with a salary history ban (Vermont and Virginia both do this in 2026). If you're asked anyway:

"I'm not able to share prior compensation, but I'm happy to talk through my expectations based on the posted range and the scope of this role."

You're not obligated to volunteer a number even where it isn't explicitly banned — anchoring the conversation to the employer's own posted range keeps leverage on your side instead of resetting it to your last job's pay.

Negotiating above the top of a posted range

This is the move most candidates skip, assuming the top number is a hard ceiling. It usually isn't — it's the top of the typical band, not an absolute cap for an exceptional candidate:

"I'm excited about this role. The range tops out at $145,000, and based on [specific quantified achievement], I believe I'd bring more than average value in this seat. Is there flexibility to go above the posted range for the right candidate, or room to make up the difference through sign-on bonus or equity?"

Employers increasingly hold the base salary tight to the posted range — precisely because it's now public and subject to internal pay-equity comparisons — while retaining more flexibility on sign-on bonus, equity refresh, and title. If the base genuinely can't move, that's where to redirect the conversation.

For more line-by-line phrasing you can adapt to a specific offer stage, our general salary negotiation scripts post walks through counters, deadlines, and competing-offer language in more depth.

Common mistakes candidates make in transparent markets

Assuming the top of the range is realistic for everyone. The top of a posted band is usually reserved for candidates who exceed the role's baseline expectations on scope, tenure, or a rare skill. Don't anchor there by default — anchor there with evidence.

Only negotiating base salary. Because the posted number is base salary, candidates fixate on it and forget to negotiate bonus targets, equity vesting schedules, sign-on bonus, remote stipends, or start date — all of which are unregulated by these laws and often far more negotiable than the number in the ad.

Not asking where in the range they're being considered. Silence gets read as "the bottom of the range is fine." Ask directly and early, ideally on the first recruiter call, not after you receive a written offer.

Treating a posting without a range as a dead end. If you're in a state or role covered by a transparency law and no range is listed, that's frequently a compliance oversight, not a signal the employer won't disclose. Ask.

Assuming the posted range applies only to entry-level hires. Broad ranges on senior postings often really do cover multiple levels — ask the recruiter to clarify where the role is currently leveled internally before you self-select out of a range that looks low at first glance.

Walking into the conversation without a rehearsed case for the top of the range. A posted number only helps you if you can justify landing near the top of it with specific, structured examples of your impact. Practicing how you'll frame that evidence — using a structured format like STAR-based storytelling — makes the difference between citing a range and making a case for where you belong in it.

Frequently asked questions

Does every US state now require salary ranges in job postings? No. As of mid-2026, roughly 15 states plus Washington, D.C. require a range in the posting itself, three more (Connecticut, Nevada, Rhode Island) require disclosure only on request or after an interview, and the remaining states have no statewide requirement at all — though some of those states have cities or counties with their own local ordinances.

What counts as a "good faith" salary range under these laws? Most statutes require the range to reflect what the employer genuinely expects to pay for the role, based on their current budget and pay scales — not an arbitrarily wide band meant to satisfy the letter of the law while disclosing nothing useful. Enforcement varies by state, and extremely wide ranges are more likely to draw scrutiny in states with active enforcement agencies, like California and Colorado.

If I'm applying for a remote role and the company isn't based in a transparency-law state, does the law still apply? Usually, yes, if the role could be filled by someone living in a covered state. Most laws are triggered by where the work could be performed, not where the company is headquartered, which is why many nationwide remote postings show a range even from companies based in states with no disclosure requirement at all.

Can a recruiter still ask what I currently make? In most states, no — over 20 states now ban employers from asking about salary history, and several pair that ban with a pay transparency requirement. Even in states without a formal ban, you're not obligated to answer; you can redirect to your expectations based on the posted range instead.

Can I still negotiate above the top of a posted range? Yes. The posted range typically represents what the employer expects to pay a typical candidate for the role, not an absolute ceiling. Strong, specific evidence of added value — scope, scarce skills, competing offers — can move an employer above the top of the band, or move the conversation toward sign-on bonus and equity if base salary truly is capped.

Do these laws cover internal promotions and transfers, not just external job ads? In several states — including Hawaii, New Jersey, and New York — yes, promotional and transfer postings are covered by the same disclosure rules as external job ads. Requirements vary, so check your specific state if you're negotiating an internal move.

What happens if an employer violates a pay transparency law? Enforcement mechanisms differ by state. Some, like New York City, allow individuals to file a complaint with a local human rights commission; others allow civil penalties per violation, and Virginia's new law even includes a mandatory cure period before legal action can proceed. As a candidate, a missing or clearly non-compliant range is worth a polite, direct question — not an assumption that nothing can be done.

Is there a federal pay transparency law I should know about? Not yet. Versions of a national Salary Transparency Act have been introduced in Congress but haven't passed, so US pay transparency remains a state-by-state and city-by-city patchwork rather than a single federal standard — unlike the EU, which now has one directive covering the entire bloc.

Putting it into practice

A posted salary range is a starting point for a negotiation, not the end of one. The states above have handed candidates real information that didn't exist a few years ago — use it to open the conversation earlier and with more confidence, rather than treating the number in the listing as fixed. Knowing the law tells you what an employer has to share; knowing how to build and deliver your case is what actually moves you toward the top of that range.

If you want to rehearse that conversation before it counts — including how to answer "what are your salary expectations" once you've already seen the posted range — ClavePrep's practice tools let you run a realistic mock interview and get feedback on how your answers land. You can see how the platform works on our how it works page, and if you're comparing offers across borders as well as across states, our guide to software engineer pay by country is a useful next read.

Sources

• New York State Department of Labor — Pay Transparency Law
• NYC Commission on Human Rights — Pay Transparency
• Washington State L&I — Equal Pay and Opportunities Act
• Jackson Lewis — Navigating 2026: Pay Transparency Laws and Employer Obligations
• National Law Review — Trends of Pay Transparency Laws and Salary History Bans Continue to Grow
• GovDocs — Pay Transparency Laws by State and Province