Should You Post Salary Ranges? What Pay Transparency Does to Your Applicant Pool

Few lines in a job post do as much work as the salary range — and few get left out as often. The usual objections are familiar: it invites negotiation, it upsets the existing team, it tips off competitors. All are real concerns. None of them outweigh what omitting the range costs you in wasted screens and late-stage collapses.

The direction of travel is one-way

A growing number of jurisdictions now require pay ranges in job postings, and candidate expectations have shifted faster than the law. Developers increasingly filter out listings without a number — not because they're only motivated by money, but because a missing range reads as a company that wants information asymmetry. If you hire across regions, you may already be required to publish for some roles. Doing it selectively is usually worse than doing it everywhere.

What actually changes when you post a range

Expect fewer applications and a better pool. That's the trade, and it's a good one:

• Self-selection replaces screening. Candidates outside your band don't apply, so your recruiters stop spending hours discovering misalignment by phone.
• Faster pipelines. The single most common cause of a hire dying in the final week is a comp conversation that should have happened in week one.
• Fewer wasted final rounds. Losing a candidate at offer stage costs you the entire loop — theirs and your team's.
• A trust signal that compounds. Transparency about money makes every other claim in the post more credible.

The apparent downside — a smaller applicant count — is mostly the removal of applications you were going to reject anyway.

What omitting the range really costs

Without a number, you pay in other currencies. You screen candidates who were never viable. You lose strong ones who assumed you were low and never applied. You spend goodwill on an awkward late conversation. And you invite the outcome you feared most: candidates who anchor high because they have nothing to calibrate against.

Pick a range you can actually defend

The range is only useful if it's honest. Before publishing:

• Decide the level first. A range that spans three seniority levels isn't a range, it's an evasion.
• Benchmark against real market data for the role, level, and the geography you hire in.
• Check internal equity. What would this range mean for the people already doing the job? Fix that before you post, not after.
• Set the top of the range at a number you would genuinely pay. If you'd never approve it, it's not the top of your range.
• Agree who can approve exceptions, so an outstanding candidate doesn't stall on an unanswerable question.

Ranges that damage trust

Some published ranges are worse than none:

• Absurdly wide bands ("$90k–$220k") tell candidates you haven't decided what you're hiring for.
• "Up to $X" is read, correctly, as a number nobody receives.
• "Competitive salary" communicates nothing and costs you the candidates who've stopped tolerating it.
• A range you never intend to honor at the top — candidates compare notes, and the reputational damage lasts far longer than the hire.

Publish the whole picture, not just base

A number in isolation invites misreading. Alongside the range, state the level and title, whether equity or bonus is included and roughly how much, whether pay is location-adjusted and on what basis, and the currency and employment structure for remote roles. A well-explained range at the market midpoint beats a vague, higher-sounding one.

Handle the internal conversation first

The most legitimate worry about posting ranges is internal: current employees will see the number and compare. They will — and they'd find out eventually regardless, usually at the worst moment.

Run a compensation review before you publish. If someone on the team is below the band you're advertising for their own job, that's a problem transparency revealed rather than caused. Fix it, then post. Teams handle "we reviewed pay and corrected it" far better than they handle discovering a new hire out-earns them.

The takeaway

Posting a salary range trades application volume for application quality, and shortens the path to a signed offer. Set the level, benchmark honestly, check internal equity, publish the full package, and only advertise a top you'd actually pay. The companies still writing "competitive salary" are quietly funding their competitors' hiring speed.

Publish a role with a range that attracts the right people — post your job on JobsList.dev.