Should You Show Salary Ranges on Job Posts? The Data Says Yes

"Should we put the salary on the job post?"

It is the most common question we hear from talent leaders, and the answer has shifted decisively in the last three years. Salary transparency is no longer a progressive nice-to-have. It is a hiring lever, a trust signal, and increasingly, a legal requirement.

What the data shows

Across recent studies of developer hiring behaviour, the pattern is consistent:

• Job posts with a salary range receive roughly 2x the qualified applications of posts without one.
• More than 80% of engineers say a missing salary is a reason to skip a role entirely.
• In LinkedIn's own data, roles with a salary range get significantly more views and applies than identical roles without one.

The mechanism is simple. A developer scanning 30 job titles in an evening uses salary as the first filter. No salary, no click.

The objections - and why they no longer hold

"We do not want competitors to see what we pay."

Your competitors already know. Levels.fyi, Glassdoor, Blind, and any agency that has placed someone with you in the last year all have your bands. The only people in the dark are the candidates you are trying to hire.

"We pay for the person, not the role."

Fine - publish a band wide enough to reflect that. A senior backend engineer band of "£85k - £115k" tells a candidate they are in the right ballpark and lets you slot them honestly based on level.

"It will upset existing employees."

It might surface that you have pay compression. That is a problem with your pay practices, not with transparency. The fix is the same either way.

"We do not know what to put."

You do. You have offers out, comp benchmarks, and a budget for the role. If you genuinely cannot put a number on a role, you are not ready to hire for it.

What to actually publish

A useful salary disclosure for an engineering role contains:

A base range with a meaningful spread - usually 15-25% from low to high. 2.

The currency and frequency (annual base, gross). 3.

Equity, if material - "competitive equity for early hires" or a refresher amount band. 4.

A note on location, especially if you pay differently by geography.

What you do not need: a single point number, a band so wide it means nothing ("£60k - £180k"), or a cute "£Competitive."

The regulatory backdrop

If commercial reasons are not enough, the regulatory environment is closing the question for you:

• EU Pay Transparency Directive - applies from June 2026, requiring salary information in job ads or before interview for all member states.
• UK - increasing pressure, public-sector advertised pay already standard, private-sector regulation under discussion.
• US - already mandatory in California, New York, Colorado, Washington, Illinois, and a growing list of states.

A global tech employer that publishes ranges in some markets and not others looks inconsistent. The cheapest path is to standardise.

How to roll it out without a fire drill

Start with one role family. Engineering is a good first move - the bands are well benchmarked. 2.

Anchor bands to a comp framework, not a gut feel. Levels.fyi, Figures, Pave, or Mercer all work. 3.

Brief hiring managers on how to talk about the band in interviews. 4.

Publish, measure for 30 days, then expand.

Teams that do this typically see a measurable lift in qualified applications, a drop in time-to-fill, and far fewer offers declined at the salary stage - because candidates self-selected on the number before applying.

Where Haystack fits

Haystack is built on the premise that developers should see the things that actually matter - salary, stack, work model, team - before they apply, not after three rounds of interviews. If you are ready to make your roles more transparent, see how Haystack presents your jobs to engineers.