← Back to Blog
September 29, 2026 · 5 min read · By Rezumz Team

How to Communicate Pay Transparency in Job Postings the Right Way

A pen poised over a check, ready to write
Photo by Moneyknack on Unsplash

Pay transparency is increasingly expected by candidates and, in a growing number of jurisdictions, legally required outright — but posting a compliance-minimum range badly (either uselessly wide or seemingly arbitrary) does little of the actual good that genuine transparency is meant to provide.

A range that's too wide defeats the purpose

A posted range of "$60,000–$150,000" is technically compliant in jurisdictions that require a range, but gives a candidate essentially no useful information to self-select on — it's wide enough to include almost any outcome. A genuinely useful range reflects the real, realistic band for this specific role at this specific level, not a maximally hedged range covering every conceivable scenario.

Decide the range before writing the posting, not after a candidate asks

A range invented on the spot when a candidate finally asks, inconsistent with what was actually budgeted or approved, undermines trust the moment the inconsistency surfaces later in the process. Confirming the real, approved range during the hiring-manager intake meeting — before the posting goes live — prevents this mismatch entirely.

Explain what moves someone within the range, if it's a wide-ish band

A range that spans a genuine level difference (e.g., covering both a mid and senior variant of the same title) benefits from a short explanation of what factors move a candidate toward the top versus the bottom of that band — years of experience, specific skills, scope. This turns a range into useful information rather than a number a candidate has to guess how to interpret.

Be consistent across postings for comparable roles

Two postings for genuinely comparable roles with meaningfully different ranges, without a clear reason (location, seniority, scope), is the kind of inconsistency that damages employer credibility if candidates notice it — and candidates increasingly do compare postings across companies and even across a single company's own listings.

Don't treat the range as the only transparency lever available

Pay transparency in a posting is table stakes rather than a complete solution — being equally clear about bonus structure, equity, benefits value, and how compensation review or advancement actually works rounds out the picture in a way a base-salary range alone doesn't. Candidates increasingly evaluate the whole package, not just the headline number.

Treat this as a genuine trust-building tool, not a compliance checkbox

Companies that approach pay transparency as a minimum legal requirement to satisfy, rather than a genuine opportunity to build candidate trust, tend to do it in the least useful way possible — the widest defensible range, the least additional context. Companies that lean into it as an actual differentiator (clear ranges, clear context, consistent application) tend to see the real recruiting benefit that transparency is capable of producing.

Frequently asked questions

How wide should a salary range be in a job posting?

Wide enough to reflect genuine uncertainty (like a level spread within one posting) but not so wide that it gives candidates no useful information — a range like $60,000–$150,000 is technically compliant in some jurisdictions but functionally uninformative.

When should the salary range for a job be decided?

During the hiring-manager intake meeting, before the posting goes live — not invented on the spot when a candidate asks, which risks being inconsistent with what was actually approved and damaging trust once that inconsistency surfaces.

Is a compensation range enough for genuine pay transparency?

It's a strong starting point but not complete on its own — being equally clear about bonus structure, equity, benefits value, and how compensation review works rounds out the picture, since candidates increasingly evaluate the whole package rather than just the base number.