Why Don't Job Postings List the Salary?

When a job posting doesn't list a salary, it's usually for one of four commonly cited reasons: the employer wants room to negotiate (an unstated number is easier to anchor low), they worry a published range will expose pay gaps among current employees, the honest range is so wide it would look meaningless, or the compensation for the role simply hasn't been finalized. None of these reasons help you as a candidate, and survey data suggests the silence costs employers too. In the Resume Genius 2026 Job Seeker Insights survey, 72% of US job seekers say they are less likely to apply to a posting without salary information, and 79% say they distrust employers that hide pay. This guide covers why the practice persists, where US law already forces a range into the posting, and how to estimate the number when the employer won't give you one.

The four reasons employers usually give

Nobody audits employer motives, so treat what follows as the reasons recruiters and compensation teams commonly give when asked, not verified facts about any particular company.

1. Negotiation leverage. If the posting names no number, the first figure on the table is often yours. Candidates who anchor low save the company money; candidates who anchor high can be filtered out before anyone spends interview time. Keeping pay unstated preserves that asymmetry: the employer knows the band, you don't.
2. Internal equity worries. Publishing a range doesn't just inform applicants; it informs current employees. If existing staff in the same role sit below the advertised band, a transparent posting invites uncomfortable conversations and raise requests. Some companies stay quiet externally to avoid that reckoning internally.
3. Genuinely wide bands. For roles hired across levels ("Software Engineer II–IV") or across geographies with location-adjusted pay, the honest range can be so wide that publishing it looks evasive. Rather than post a span that invites mockery, some employers post nothing.
4. A sloppy or unfinished process. Sometimes there is no hidden strategy at all. The budget isn't approved, the level isn't decided, HR and the hiring manager haven't aligned, or the posting was copied from a template that never had a salary field. An absent range can signal an immature process as easily as a calculated one.

Notice that only the first two reasons are strategic. The other two are structural or accidental, which matters later, when you're deciding how much weight to put on a missing number.

What hiding pay costs employers

Whatever the internal logic, the external effect is measurable in surveys of candidates. In the Resume Genius 2026 Job Seeker Insights survey of US job seekers, 72% say they are less likely to apply to a posting that has no salary information, and 79% say they distrust employers that hide pay.

Those are perception numbers from one survey, not an audit of application behavior, but they describe the pool an opaque posting draws from. A no-salary listing skews toward candidates who didn't have the leverage to be choosy, while the candidates every employer says it wants (people with options) report screening it out. And the 79% distrust figure suggests the damage isn't limited to one application: hiding pay reads to candidates as a statement about how the company negotiates generally.

For you, the practical takeaway is the flip side: employers that do publish a range are self-selecting for confidence in their own compensation. That's worth something when you're deciding where to spend a tailored application.

Where US law already requires a range

A growing patchwork of US states and cities now requires employers to include a pay range in job postings: Colorado, California, New York, and Washington are among the best-known examples, and several other states and cities have adopted similar rules. The details differ by jurisdiction (who's covered, what counts as a "posting", whether remote roles reachable from that state are included), so check the specific rules where you live rather than assuming a national standard.

Two consequences follow for job seekers everywhere:

• Postings written for those markets carry ranges by obligation, not choice. A published range on a Colorado or New York posting tells you the law's minimum was met; it doesn't by itself signal an unusually transparent employer.
• Transparency leaks across borders. A company hiring nationally often can't maintain two versions of the truth. The range it's required to publish in one state is usually drawn from the same internal band it uses everywhere, which makes those postings a research tool, as covered next.

How to estimate the range when it's missing

When a posting is silent, you can usually reconstruct a working estimate in a few minutes:

1. Find the same company's postings in transparency states. Search the employer's careers site for the same or an adjacent title advertised in Colorado, California, New York, or Washington. The published range there typically reflects the same internal band, give or take a location adjustment.
2. Read the company's other listings at the same level. Even without a legal requirement, some employers publish pay on some roles and not others. Adjacent postings at the same seniority sketch the band the silent one likely sits in.
3. Use title and level norms. Most fields have reasonably stable conventions for what a "Senior", "Staff", or "II/III" title pays in a given market. Aggregate salary data keyed to level and city won't give you the company's exact band, but it bounds your estimate and arms you for the conversation.
4. Check the listing at its source. An employer's own hiring system (an ATS like Greenhouse, Lever, or Ashby) is where a published range lives first; copies on aggregator boards often strip or garble it. That's the pipe JoBuzzer is built on: every listing is pulled straight from the employer's own hiring system, and whenever the employer publishes a salary range there, it's displayed on the listing, so what you see is the employer's own number, not a third-party guess. Hourly Buzz alert emails can also bring new matching listings to you while they're still fresh.

When to ask about compensation

If research doesn't settle it, ask, and do it earlier than most candidates think is polite. The first recruiter screen is a reasonable and widely accepted moment, and a simple framing works: "Before we go deeper, could you share the range budgeted for this role? I want to make sure we're aligned so we don't spend each other's time." Recruiters field this question constantly; a company that reacts badly to it in 2026 is telling you something.

If the employer asks for your expectations first, give a researched range rather than a single number, and tie it to your data: the company's own postings elsewhere, level norms for the market. A range keeps the conversation open; a lone number becomes your ceiling.

A missing salary is a signal, not a verdict

Given that 72% of US job seekers in the Resume Genius 2026 survey say they're less likely to apply without salary information, skipping every silent posting might seem like the efficient move. It's usually an overcorrection. Plenty of legitimate, well-paying roles omit pay, especially at smaller companies, outside transparency jurisdictions, or where the process (not the strategy) is the problem.

Treat the missing range as one input alongside the others: how fresh the posting is, how specific the responsibilities are, whether the role is live in the employer's own system, and what the company's other listings look like. A silent posting that's fresh, specific, and verifiable at the source deserves a five-minute estimate and an early question, not an automatic pass. And when you're triaging a long list, it's fair to let the transparent listings jump the queue: on JoBuzzer, listings show the employer's own published range whenever one exists in their hiring system, alongside 400k+ jobs from 10k+ companies surfaced ahead of mainstream job sites. A built-in application tracker keeps the applications you do send organized, and the Buzz plan comes in at $7/mo.

FAQ

Why do companies not list salary in job postings? The most commonly cited reasons are negotiation leverage (an unstated number is easier to anchor low), worry that a published range will expose pay gaps among current employees, ranges so wide they would look meaningless, and compensation that simply hasn't been finalized. These are the reasons employers give, not audited facts, and the mix varies by company.

Is it a red flag if a job posting doesn't list a salary? It's a signal, not a verdict. Many legitimate employers still omit pay, especially outside the US jurisdictions that require ranges. Treat a missing salary as one data point alongside posting freshness, specificity, and the company's other listings, and ask about compensation early rather than skipping the role automatically.

How can I find the salary range if the posting doesn't list one? Check whether the same company advertises the same or a similar role in a US state or city that requires pay ranges: for example Colorado, California, New York, or Washington. The range published there usually reflects the same internal band. The company's other postings at the same level, and standard title and level norms in your field, help you triangulate the rest.

When should I ask about salary in the interview process? The first recruiter screen is a reasonable and widely accepted moment. Frame it as saving both sides time: ask what range is budgeted for the role. If you're asked for your expectations first, give a researched range rather than a single number, and anchor it to the market data you've gathered.