Should You Include Salary Range in Job Posts?
Should you include salary range in job postings? The data on application rates, pay transparency laws, and how to set a range you can defend. A practical guide.
Should you include a salary range in job postings? For a growing number of employers the question is settled by law, but even where it is optional, the evidence increasingly points one way. Posting pay widens your applicant pool, shortens negotiations, and builds trust before a candidate ever speaks to you. The main reason companies hold back is fear — usually misplaced — about what it reveals.
The case for posting a range
Three benefits show up consistently.
- More applicants, better targeted. Postings with salary information tend to attract more applications, and the people who apply have already accepted the band. You spend less time on calls that end at "so what's the budget?"
- Shorter, fairer negotiations. When the range is public, offers cluster around it. That narrows the gap that pay secrecy tends to widen for women and underrepresented candidates.
- Trust. Candidates read a missing salary as a red flag. Including it signals you are organised and fair — the same qualities they hope the job itself has.
The legal picture is moving fast
Pay transparency is no longer a niche policy. A number of US states and cities — including Colorado, California, New York State, and Washington — now require salary ranges in postings, and the EU Pay Transparency Directive pushes member states toward disclosure obligations by 2026. If you hire remotely across jurisdictions, the practical effect is that one covered location often means you should post for the role everywhere.
If you recruit across multiple states or countries, treat salary transparency as the default. It is simpler than tracking which posting needs which disclosure, and it is where regulation is heading anyway.
The objections, answered
The hesitation is real, so address it honestly.
"Competitors will see what we pay." They already estimate it from offers, levelling sites, and your own ex-employees. A posted range removes their information advantage in negotiations more than it gives them one.
"Current staff will be unhappy." If a public range for an open role would upset your existing team, you likely have a pay-equity problem that transparency did not create — it only surfaced it. Better to find it now.
"Our range is wide." That is fine, within reason. A band that spans two genuine levels is honest. A band so wide it is meaningless ($60k–$160k) just tells candidates you have not decided, and some transparency laws cap how wide a posted range can be.
How to set a range you can defend
A defensible range comes from a simple, repeatable process.
- Benchmark the role against market data for your location and level, not against what the last person happened to earn.
- Define the band by level, typically a 15–25% spread from minimum to maximum, mapped to clear expectations for each end.
- Tie the candidate's offer to the rubric you scored them against — skills, experience, scope — so the number reflects evidence, not how hard they pushed in negotiation.
- Write the range and reasoning down so anyone on the team can explain why a given offer sits where it does.
That last point is where structure pays off. When your scoring is transparent and consistent, the salary conversation stops being a haggle and becomes a straightforward read of where the candidate landed against the role.
Talent Tick scores every candidate deterministically against the same rubric and flags a missing salary range right inside the JD optimizer, so your postings stay compliant and your offers stay defensible. Start a free 21-day trial and post your next role with a range you can stand behind.