No Salary on the Job Posting? How to Find the Number Before You Interview

Your Actual Odds, Counted

As of August 3, 2026, ForgeApply's job corpus holds 67,929 active US tech postings, pulled directly from company career systems and dropped the moment a role closes. 27,386 of them — 40.3% — publish a salary range. Flip that around: three of every five postings you open won't tell you what the job pays.

The reasons are mundane. Most companies disclose only where a state law makes them, and keeping the band private preserves negotiating room and hides internal pay structure. A missing range isn't a red flag by itself. But interviewing blind has a real cost: a comp mismatch discovered at offer stage burns an entire loop — usually weeks — on both sides. The point of this playbook is to get the number, or a defensible estimate of it, before you invest that time. The three plays below are ordered by effort; the first two take about five minutes combined.

Play 1: Check the Company's Other Live Postings

This is the play almost nobody runs, and it's the one we can quantify. Among the 2,149 companies in our corpus with at least two open roles and at least one posting missing a range, 1,280 — 59.6% — publish a range on at least one *other* live posting. The company that won't tell you what your role pays has, about three times out of five, already written a pay band on a different posting.

Why would a company disclose on some postings and not others? Because transparency laws trigger by location. An employer hiring in California, Colorado, New York, or Washington has to post a range on roles that can be worked there, and many post ranges only on exactly those roles.

How to run it: follow the posting's apply link to the company's actual careers board — not an aggregator's copy — and scan every open role for a range. The best match is the same or an adjacent title marked remote-US or based in a disclosing state. Two caveats when you translate what you find: many companies adjust bands by metro, so treat an out-of-state range as the shape of the band rather than your exact number; and match the level — a Senior range tells you less about a mid-level role than a same-level posting one team over.

Play 2: Comp the Role From Postings That Do Disclose

If the company discloses nowhere, the market still does. The 27,386 postings in our corpus that publish ranges are enough to compute a median and a typical band for most common roles and metros — that's what the salary explorer is: employer-committed ranges from live postings, refreshed daily, not self-reported survey numbers from three years ago. Look up your role and city — for example, software engineer salary — and note the median and the typical range. That's your anchor for the conversation in Play 3, and it's checkable: a recruiter can verify live posted ranges in minutes, which makes the anchor hard to wave away.

If you want the fuller method — what posted ranges do and don't include, how to read a wide band — that's covered in how to find real salary data, and the market-wide disclosure picture is in our pay transparency report.

Play 3: Ask — Earlier Than Feels Polite

The norm has genuinely shifted: asking for the range at first contact is now a normal, answerable question, and recruiters would also rather not run a full loop that dies at offer stage over comp. The right moment is the first recruiter touchpoint — not the hiring manager, and not after three interviews.

When a recruiter emails to schedule a screen, reply with your availability plus one line: "Before we book time — could you share the budgeted base range for this role? I want to make sure we're in the same ballpark." If you're already on the screen and it hasn't come up, ask the same question in the last five minutes. You'll get a real answer most of the time; a company that refuses to name any number after being asked directly is giving you information too.

One targeting note: if you're doing hiring-manager outreach alongside your application, don't spend that note on comp. The outreach note has one job — getting your application looked at. Salary questions belong with the recruiter, whose job is the process.

If the Application Form Forces a Number

Some forms include a salary-expectations field. In order of preference: leave it blank if it's optional; if it's free text, write something like "Flexible depending on total compensation — for reference, the median disclosed base for comparable roles in this metro is around $X," using your Play 2 number; if it forces a single number, give one at or slightly above the comp median that you can defend out loud. A defensible number from live market data won't disqualify you the way the folklore says it will — and it beats anchoring yourself low with a guess.

The Legal Lever Is Weaker Than You'd Hope

A growing list of states requires posted ranges, so it's tempting to assume any remote-eligible role legally owes you a number. Our data says that assumption doesn't hold in practice: 41.8% of active remote postings in our corpus disclose a range, versus 39.8% of on-site postings — barely different. Scope carve-outs, small-employer exemptions, and thin enforcement mean the laws move the market slowly, not per-posting.

The lever's practical use isn't filing complaints. It's that a company hiring in a disclosing state already has your role's band written down somewhere — which is exactly why Play 1 works, and why the Play 3 question is easy for a recruiter to answer.

The Bottom Line

Run the plays in order: two minutes on the company's other postings (3-in-5 odds the band is already public), two minutes comping the role from live disclosed ranges, then ask the recruiter at first contact with your anchor in hand. Don't start an interview loop blind — the number exists, someone has it written down, and one of these three plays usually shakes it loose. And if you'd rather weight your search toward employers that just say the number: our job browser pulls live roles straight from company boards and drops them the moment they close, and every figure in the salary explorer traces back to a live posting an employer chose to publish.