The short answer: if you employ anyone in California, Colorado, New York, Washington, or any of the other 13 covered jurisdictions — and that's most US employers — you need a salary range in every external job listing. The right range is a good-faith band of about 30 to 50 percent width that mirrors your internal compensation tier. Posting it well doesn't just keep you compliant; it tightens your hiring funnel, raises applicant quality, and dramatically reduces late-stage offer drop-off.

This guide covers the 2026 state-by-state compliance map, how to actually write a range that holds up to scrutiny, how to handle remote roles that span multiple jurisdictions, the conversion data on what posting pay does to your applicant pool, and the operational pitfalls that send most employers from "we'll add a range" to "our recruiters are now spending three hours per week debating it."

17 + DC
US jurisdictions with active pay transparency laws in 2026
~65%
of US employers covered by at least one pay transparency law
70%
of companies posting ranges report more applicants (SHRM)

The 2026 Pay Transparency Map (Who's Required, Who Isn't)

Pay transparency went from a single-state novelty in 2018 (Colorado was first to require ranges in postings) to a multi-jurisdiction patchwork covering most of the US tech workforce by 2026. The list of covered jurisdictions has expanded almost every quarter for the last three years. Here's where things stand mid-2026.

States with mandatory salary-range-in-posting requirements

The following states require employers to include a salary range (or "wage scale" / "pay scale") directly in external job postings:

Several additional states require pay disclosure upon request or before an offer (Connecticut, Nevada, Rhode Island), and several more have laws taking effect later in 2026 or in 2027 (Massachusetts, Cleveland and Akron in Ohio, others in the queue). The trajectory is unambiguous: by 2027, the question won't be "do I have to post a range?" but "what state will require us to post it next?"

The remote-work catch that surprises employers

This is the single most common compliance miss in 2026. If a remote role could be performed from a state with a pay transparency law, that state's law applies — regardless of where the employer is incorporated, where the team is concentrated, or where the hiring manager sits. An Atlanta-based startup posting a fully-remote engineering role is, in practice, subject to California, New York, Colorado, and Washington pay transparency requirements simultaneously, because residents of all four states could apply.

The two operational responses employers actually take:

  1. Post the range nationally. This is the cleaner option and what most well-run companies have settled on by 2026. One range per role (or location-banded ranges), included in every posting on every board, full stop.
  2. Geo-exclude covered states. "Not available to residents of CA, CO, NY, WA, IL, MN, etc." This works legally in most cases, but the list of excluded states keeps growing, the optics are bad (it broadcasts that the role pays below local market), and you've just told every candidate in those high-talent-density markets that you don't want them.

Option 1 wins on every dimension that matters — compliance, recruiting brand, and ease of operation. Option 2 is a delaying tactic that won't work for much longer.

How to Write a Salary Range That Holds Up

Posting some range satisfies the letter of most pay transparency laws. Posting a good range is what separates compliance theater from a hiring funnel that actually improves. Here's the framework that works.

Step 1

Tie the range to your internal compensation band

If you have a defined internal band for the role's level, location, and function — and you should — that band is the posted range. The band-min becomes the posted minimum, the band-max becomes the posted maximum, and you've already done the hard work. If you don't have internal bands, the act of being forced to publish a range is the forcing function that finally gets your comp philosophy out of someone's head and into a document. That's a net good for the company.

Step 2

Keep the range width to 30–50%

A 30% range (e.g., $140k–$182k) signals that you've done the work and have a real sense of what the role pays. A 50% range ($120k–$180k) is the upper end of what regulators will treat as good-faith. A 100%+ range ($90k–$200k) is the band-aid that doesn't actually disclose anything, and it's exactly what enforcement actions in California, Colorado, and Washington have targeted. The optics are also terrible — candidates assume you're hiding the real number, and the most-qualified applicants drop off because they assume the high end is fictional.

Step 3

Include equity and bonus in the description, even if not in the range

Most pay transparency laws require disclosure of base salary or hourly rate. They generally don't require disclosure of equity, bonus, or benefits — but disclosing them is what turns the posting from a legal document into a recruiting tool. A line like "Base salary: $160k–$200k. Plus 0.05–0.15% equity, 10% target bonus, and full benefits including [items]" is dramatically more effective than "$160k–$200k" alone. Total compensation, not just base, is what candidates evaluate.

Step 4

Use location-banded ranges for distributed companies

If you pay differently by geo — most distributed companies do — post the band that matches each location, or post the full national range with a note. Example: "$160k–$200k (San Francisco / NYC), $144k–$180k (other US locations)." Some companies post a single national maximum and adjust down by location; others post location-specific ranges. Either approach is compliant and honest. The wrong approach is to post only the highest-tier metro number and quietly offer significantly less to candidates outside that metro — that's the practice that's now generating complaints to state labor agencies.

Step 5

Update the range when the role spec changes — not yearly

The "good faith estimate" standard requires the range to reflect what you currently expect to pay. If you re-leveled the role, expanded the scope, or shifted the location requirement, update the range. If you've been running the same posting for nine months without revisiting the range, the legal exposure isn't huge in most jurisdictions, but the comp band underneath has probably drifted — and your most-qualified candidates can tell. Treat the posted range as a living number tied to the role spec, not a one-time decision.

What Posting Pay Actually Does to Your Funnel

The pay-transparency compliance conversation tends to get framed defensively — what you have to do, what the fines are, how to avoid trouble. The more interesting framing is what posting pay does to the funnel itself. The data here is increasingly clear and increasingly hard to argue with.

Applicant volume goes up. A SHRM survey of US employers found that roughly 70% of companies that began including salary in postings saw more applicants. This is the headline number, and it matters most for roles where you've been struggling to fill the top of the funnel. Pay transparency is, for many roles, a free top-of-funnel lift.

Applicant quality goes up too. The intuition that posting a range will bring in unqualified candidates "fishing for a number" is, empirically, backward. Candidates whose expectations are outside the range self-select out before applying, which means the candidates who do apply are the ones whose expectations are inside your band. This is filtering you previously had to do via 15-minute screen calls with every candidate. Now it happens automatically before they hit submit.

Time-to-hire drops, particularly at the offer stage. The most expensive part of any hiring funnel is the candidate who makes it through five interview rounds before discovering the offer is well below their expectations. That candidate drops out, your team spent 12+ hours on the loop, and the role stays open another six weeks. Posting the range collapses that scenario — the comp expectation conversation happens up front, not at the end.

Reputational benefits compound. Engineers and senior ICs increasingly use the presence (or absence) of a salary range as a heuristic for company transparency. A posting without a range gets read as "this company isn't ready to be honest with me, what else are they hiding?" — particularly by senior candidates who have options. Posting a range moves you out of that category by default.

For a more detailed exploration of how culture and compensation signal company quality to engineers, see what engineers actually look at on careers pages — pay transparency is high on the list.

Common Mistakes Employers Make in 2026

The compliance pattern in 2026 is no longer "we haven't done it." Almost every multi-state employer has added a range somewhere by now. The mistakes have shifted to how they're doing it.

Mistake 1: The 200% range. Posting a band so wide it conveys no information ($80k–$240k) defeats the purpose of the law and is increasingly drawing regulator attention. If your real range is $130k–$170k, post that. Bands wider than ~50% read as bad-faith and damage candidate trust regardless of legality.

Mistake 2: Range drift over time. A range posted in 2024 and never updated is a legal risk in jurisdictions that require a "current" good-faith estimate. It's also a comp-band-management problem: most internal bands shift annually, but external postings often don't, which creates inconsistencies between what you advertise and what you offer.

Mistake 3: One range for a role that has three real bands. A "Senior Engineer" posting often covers what's actually three internal levels (mid, senior, senior+). Posting a single $140k–$220k range obscures the actual level being hired and confuses candidates. Post separate listings per level, or be explicit about the leveling structure inside the description.

Mistake 4: Posting the range, then offering below it. The fastest way to lose late-stage candidates and end up on enforcement radar. If your range is $160k–$200k, the offer must fall inside that range. If the candidate's experience genuinely doesn't justify the band, the right answer is a different requisition at a different level — not an offer below your posted range.

Mistake 5: Treating the posted range as a ceiling. Some recruiting teams have started treating the posted maximum as the cap on what they can offer. The posted range is supposed to reflect what you'll pay — but it doesn't preclude an above-range offer for a uniquely strong candidate. If you're consistently butting up against the posted max, the range itself is probably stale.

The Operational Playbook: Going From Zero to Compliant in 4 Weeks

If your company has been deferring the pay transparency conversation and now needs to ship a compliant range across hundreds of open postings, the work breaks into four weeks. Here's the sequence that actually works.

Week 1

Inventory and assess

Pull every open requisition. For each, tag the jurisdictions the role could be filled from (typically a function of remote/hybrid/onsite policy plus the team's location). Most multi-state employers discover at this stage that they're already legally required to post ranges on most postings, regardless of their internal policy. Categorize the roles by whether you have a current internal comp band defined. Roles without bands need bands defined before they can have postings updated — this is the bottleneck.

Week 2

Build (or refresh) internal comp bands by level × location × function

If you don't have bands, this is the actual work. Use external benchmarks (Radford, Aon, the comp survey of your choice), your own historical offer data, and a few competitive data points to define a band-min and band-max for each level/location/function combination you hire into. If you do have bands, audit them — bands set in 2024 are almost certainly stale by mid-2026, particularly in AI and senior IC roles. Expect comp leadership to push back on widening some bands; resist the urge to inflate top of band purely to make recruiting easier.

Week 3

Update postings and ATS templates

This is the lift that scales. Most companies should update both the open requisitions and the ATS posting template, so that every new req inherits the structure automatically. Build a standard salary range block: a single paragraph with base range, equity range (if disclosed), bonus target, benefits summary, and any geo qualifications. Make the block a mandatory field in the req creation flow. The cost of doing this once is much lower than the cost of recruiters manually adding ranges to every new posting forever.

Week 4

Train the recruiting org and brief the comp team

Two conversations have to happen. Recruiters need to know how to handle the new flow of candidate questions — "your range is $160k–$200k, where would I be?", "can you go higher than the top of the range?", "is the equity in the range?". The comp team needs to be available for fast escalations when a unique candidate justifies an above-range offer or a re-leveled requisition. Without these two conversations, the posted ranges will silently start to drift from reality within a quarter.

Where Pay Transparency Is Heading

The 2026 patchwork is messy. By 2028 it likely won't be — for two reasons. First, the states that have adopted disclosure laws are largely the high-population, high-tech-employment states, so the effective coverage is already at the practical "you have to comply" threshold for most employers. Second, the EU's Pay Transparency Directive (which takes full effect by mid-2026 and requires substantially more disclosure than any current US state law) will pull multinational employers toward higher disclosure standards globally.

Several specific shifts are likely in the next 18 to 24 months:

The companies that have built clean comp band infrastructure already — clear bands by level and location, regular benchmarking cycles, deliberate offer policy — are well positioned for everything that's coming. The companies still treating pay transparency as a one-time compliance project will be doing this work again every quarter for the next several years.

Why This Matters for Culture (Not Just Compliance)

Pay transparency is one of the few culture signals candidates can verify before applying. Every other culture marker — "we're flat," "we're remote-first," "we ship fast," "we care about WLB" — can be marketing copy. A salary range, by contrast, is either there or it isn't, and it's either honest or it isn't. The presence of a specific, defensible range tells a candidate that the company has done the internal work to know what it pays, is willing to put that work in front of the public, and trusts candidates to evaluate the offer on the merits.

For senior engineers and ICs evaluating multiple companies, this signal has become a meaningful tiebreaker. Companies that consistently post tight, current ranges (and pay within them) get the benefit of the doubt on other cultural claims. Companies that post 200% ranges or post nothing at all get scrutinized harder on every other claim they make. The signal compounds.

If you're thinking about how your hiring practices land with the candidates you most want to attract, browse the culture directory to see how 100+ companies present themselves — and look for the patterns that the candidates you're competing with are seeing every day. The candidates evaluating your job posting are evaluating it next to your competitors' postings, and increasingly, the salary range is the first thing they look at.

Make your culture work for hiring

Companies that win in 2026 don't just post a salary range — they make every part of their hiring experience legible to candidates. See how leading employers are presenting culture, comp, and team norms.

For Employers → See Company Culture Profiles →

Frequently Asked Questions

Which US states require salary ranges in job postings in 2026? +
As of 2026, 17 states plus Washington DC have active pay transparency laws of varying scope, including California, Colorado, Connecticut, DC, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, Nevada, New Jersey, New York, Rhode Island, Vermont, Washington, and several others either fully active or with rolling effective dates. Roughly 65% of US employers are now affected by at least one of these laws. The safest operating assumption for any multi-state employer in 2026 is to post the range in every job listing, on every job board, for every role.
Do remote job postings have to include salary ranges? +
Generally yes, if the role can be performed from a state with a pay transparency law. The dominant interpretation is that if a remote role can be filled by a resident of California, Colorado, Washington, New York, or any of the other covered states, the employer must include a pay range — regardless of where the company is headquartered. This effectively means national remote postings must include a range, since at least one covered state will almost always be eligible.
How wide can the salary range in a job posting be? +
The legal requirement is a "good faith estimate" of what the employer expects to pay. Most laws don't specify a maximum width, but enforcement actions and case law are converging on an unwritten norm of roughly 30 to 50 percent range width (e.g., a 30% range like $140k–$182k is broadly defensible; a 200% range like $80k–$240k is not). The most defensible practice is to tie the posted range to your internal compensation band for that level, location, and role family.
Does posting a salary range improve hiring outcomes? +
Yes, on multiple measurable dimensions. SHRM survey data shows that roughly 70% of businesses that included a salary range in postings saw more applicants. Beyond applicant volume, salary ranges typically improve applicant quality (fewer candidates whose expectations are outside the budget), reduce time-to-offer (the comp conversation starts and ends earlier), and reduce candidate drop-off late in the funnel.
What are the penalties for not posting salary ranges? +
Penalties vary by state but increasingly include monetary fines per violation, with each non-compliant job posting often counted as a separate violation. California, Colorado, New York, and Washington have all imposed civil penalties on employers, ranging from a few hundred dollars per posting at the low end to several thousand at the high end, with escalating fines for repeat violations. Beyond direct fines, employers face reputational risk, candidate trust damage, and increased difficulty hiring in the affected state's market.
Should startups post salary ranges before they're legally required to? +
Strongly yes. For startups specifically, posting salary ranges is one of the highest-leverage hiring-funnel improvements available. It signals confidence in your comp philosophy, eliminates candidates whose expectations don't fit before they consume interview time, and meaningfully expands your applicant pool. It also forces internal discipline — to post a range, you have to decide on one, which most early-stage companies haven't done formally. The act of writing the band is itself organizationally clarifying.