Pay Transparency in Job Postings (2026)

For most of the last twenty years, the dominant US hiring norm was that salary was a topic best avoided until the offer stage. The recruiter would deflect (“let’s talk about fit first”), the hiring manager would deflect (“we’ll have that conversation when we’re closer”), and the candidate would either ask too early and look mercenary, or wait too long and get blindsided. That whole choreography is dying out, and the reason is mostly legal, not cultural.

Starting with Colorado’s Equal Pay for Equal Work Act in 2021, US state and city governments have been steadily adding pay-transparency mandates — rules requiring employers above a size threshold to publish a salary range on job postings. By 2026 the covered footprint includes California, Washington, New York State, New York City, Illinois, Hawaii, Minnesota, Maryland, the District of Columbia, and a growing list of others, with the EU’s Pay Transparency Directive bringing a comparable regime online across European member states this year as well. For any company hiring remote-eligible roles into the US or EU, the operating assumption in 2026 should be that you are publishing ranges by default, on every posting, in local currency.

This article is not a legal review. It’s a hiring playbook: what to publish, how to set the range, what to expect when you do, and how to handle the conversations — with candidates, with your current team, and with your finance partner — that the published range will generate.

Why “just publish a wide range” is the wrong move

The first instinct of a lot of employers, when transparency rules took effect, was to comply on the letter and dodge on the spirit: publish a range, but make it so wide it communicates nothing. The famous internal example used to be a tech listing from a major employer that disclosed a range of roughly $80k to $400k for a single role. That clears the legal bar. It also tells candidates absolutely nothing useful and signals that the employer is approaching the law as a compliance burden rather than a useful information channel.

Two things to know about this approach. First, regulators in several states have started pushing back on ranges so wide they fail the “good-faith” standard most laws actually require. The exposure has shifted from “technically allowed” to “quietly risky.” Second — and more importantly — candidates pattern-match very quickly. A 5x range tells a senior engineer that the employer is unserious or evasive, and the strongest candidates self-deselect at exactly the rate you don’t want them to.

A 5x range tells a senior engineer that the employer is either unserious or evasive. The strongest candidates self-deselect at exactly the rate you don’t want them to.

The operationally healthy version is a range that mirrors your actual internal band for the role + level, with at most a small location adjustment for fully-remote postings. If your Senior Backend Engineer band is $185k–$230k base in the Bay Area, post that. Don’t pad to $150k–$300k to preserve negotiation room you don’t actually have — you’ll just lose candidates who’d have accepted $230k because they assumed the “real” ceiling was higher and you weren’t willing to meet it.

What gets published, and in what order

A defensible 2026 job posting has four compensation components, each addressed explicitly. The order matters — candidates pattern-match on whether you lead with the part you’re most comfortable with or the part they care most about.

How to set the base range

If you already have an internal comp band for the role + level, post it. If you don’t, the published-range process is the right forcing function to build one. The minimum-viable methodology:

1. Identify three to five competitor companies you actually compete with for talent at this level. Not aspirational peers — real peers, the ones whose engineers your team has hired from in the last twelve months and the ones whose offers your team has lost to.
2. Pull their published ranges for the equivalent role + level. Pay-transparency laws have made this dramatically easier than it was in 2022 — competitor ranges are now public artifacts you can read on any LinkedIn job posting in a covered jurisdiction.
3. Calibrate your range to the relevant percentile of that peer set. Most companies aim for somewhere between the 50th and 75th percentile; very few should be aiming below the median for engineers in 2026 and expecting to win competitive offers.
4. Stress-test the top of the range against your finance partner. Can you actually pay it? If not, lower it — an honest, tighter range beats a fictional, wider one.

What changes when you publish

Three things happen, mostly in this order.

Application volume goes down. Application quality goes up. Postings with clear ranges typically attract a smaller raw funnel but a higher share of candidates whose expectations match the range — which is the candidate population recruiters actually want. The drop in volume comes mostly from underqualified or salary-mismatched applicants self-selecting out before they take up phone-screen time. Conversion rate from application to offer goes up, even though the absolute number of offers per posting is similar.

Time-to-first-substantive-conversation shortens. Recruiters stop spending the first call discovering whether the candidate’s salary expectations are in the same universe as the role. That conversation has happened pre-application, in the candidate’s head. The first call gets to be about fit, motivation, and scope — which means the candidate experience improves measurably, and your offer-acceptance rates tend to go up too.

Your existing team will see the published range. This is the consequence most hiring leaders are quietly nervous about, and it’s the one with the highest long-run benefit if you handle it well. If you have a Senior Engineer on the team making $175k and you post a Senior Engineer role at $190k–$230k, you are going to have a comp conversation with that person. The healthy version is to get ahead of it: run a calibration review proactively against the new public ranges, adjust where the gap is unjustifiable, and have a clear story for the gaps that are justifiable (level distinctions, recent hire vs tenured, scope differences). The unhealthy version is to suppress the published range to preserve the gap, which the law in most covered jurisdictions doesn’t actually permit.

The four hardest candidate questions, and how to answer them

1. “Where in the range will my offer land?”

The honest answer is “it depends on what you bring to the role and how the interview process goes — here are the three or four factors that move offers within the range.” The dishonest version (“we always start at the bottom and there’s flexibility”) is what trained a generation of candidates to distrust recruiters. Name the factors explicitly: depth of relevant experience, scope of prior ownership, location adjustment if applicable, and competing offers. The recruiter conversation should match what your offer model actually does.

2. “What’s the equity worth?”

For public companies, this is a USD value calculation: number of shares times current share price, vesting schedule named. For private companies, the honest answer is “here’s the number of options, here’s the strike, here’s the most recent preferred price, here’s the vesting schedule, and here’s the caveat that valuations move and this represents a snapshot.” The dishonest version — quoting a single “equity value” number based on the last round price as though it’s a guaranteed payout — trained a generation of engineers to discount equity entirely, which is bad for everyone including your private company.

3. “Why is the range different in my city vs. on the careers page?”

If you use location-tier compensation, name the tiers and the cities in each tier on the posting itself. Don’t make candidates guess. If you use a single national band, say that too. The worst possible answer is “our recruiter will explain” — that’s the answer that makes candidates assume something unfavorable is being concealed.

4. “What’s the bonus actually paid out at, historically?”

Target is what you publish. Actual is what you’ve paid. If they’ve been the same for the last three years, the honest answer is “target and actual have matched over the last three years.” If they’ve differed, the honest answer is “target is X, actual has been roughly Y over the last three years because [reason].” Candidates ask this question to find out whether you tell the truth under pressure. The answer matters less than the willingness to give a real one.

What to put on the careers page itself

Pay transparency in the posting is the floor. The next layer up is making the candidate-experience parts of your company’s culture page match the transparency in the posting: the comp philosophy, the level definitions, the way performance reviews translate to compensation changes, the equity refresh policy. Companies that publish all of this on a single page reliably out-convert companies that publish only the minimum.

This is the long-tail benefit of transparency rules that most employers haven’t fully absorbed yet. The published range is a one-line signal. The reasoning behind the range — how levels are defined, how raises happen, how equity refreshes work — is a ten-paragraph signal that turns into one of the most-read pages on your careers site and one of the most cited reasons strong candidates pick you over a competitor who’s published a similar number with no story behind it.

One more thing: this isn’t going away

The trajectory through 2026 is clear: more US states adding pay-transparency requirements each legislative session, the EU directive bringing range disclosure to most of Europe this year, and the UK consulting on a similar regime. The set of jurisdictions where you can post without a range is shrinking, and the candidate norm — expecting a range, treating its absence as a yellow flag — has already shifted independently of the law.

The companies that handle this well treat it as an opportunity to do a job they’d have benefited from doing anyway: building a defensible comp model, publishing it, and developing the recruiter and hiring-manager craft to talk about it without flinching. The companies that handle it badly treat it as a compliance overhead, do the minimum, and quietly lose the candidates who would have been best for the role. The technology of hiring has changed underneath everyone in the last four years. Pay transparency is one of the bigger pieces of that shift, and 2026 is the year the “do we have to?” conversation finally ends.