How to ask for the salary range (when the posting hides pay)

The situation. A recruiter reached out, or a screen is already on your calendar, and the posting says nothing about pay. You’re being asked to invest hours of interviews in a number you’ve never seen. You want to ask what the role actually pays - and some part of you worries that asking early marks you as money-first, difficult, or both.

What’s actually happening. The range typically already exists, and the person you’re talking to commonly knows it. Companies typically approve a compensation band before a role is even posted, and the recruiter commonly works inside that band all day. When a posting hides pay, that’s commonly policy inertia rather than strategy - and hidden pay is no longer universal: per Indeed Hiring Lab’s Pay Transparency Tracker, 49.0% of US job postings on Indeed carried explicit pay information in June 2026. About half the market now shows the number up front. Asking for it isn’t a breach of etiquette; it’s asking to be treated like the other half.

There’s a second mechanic underneath. The reason recruiters ask for your expectations first is that the first number on the table typically anchors everything after it. Asking for the range flips the sequence: their number becomes the anchor, and the rest of your negotiation happens against a band you can see.

Two decisions before the words. Who: the recruiter, not the hiring manager - the recruiter owns the compensation conversation, while the hiring manager often doesn’t know the band, and the question can land awkwardly in a technical round. When: the earliest natural moment - your reply to the outreach email, or the first minutes of the screen. One more thing worth two minutes: a growing number of states require the range to be published or disclosed to candidates, so check the rules where you and the company sit before the call.

What to say. On the recruiter screen, early, in an easy tone:

“Before we go much further - could I ask what compensation range has been budgeted for this role? I’m asking early for a practical reason: I’d rather confirm we’re in the same ballpark now than discover a gap after we’ve both invested several rounds. If the band works, I’m all in on the process.”

The email version, replying to outreach before anything gets scheduled:

“Hi [Name], thanks for reaching out - the role looks genuinely interesting, and I’d be glad to talk. One question before we schedule: could you share the compensation range budgeted for this position? I’d rather confirm we’re aligned before we take up interview time on both sides. If the band works, I’m happy to move quickly.”

When they deflect. Some recruiters answer on the spot. Others reach for “we don’t share ranges at this stage” or “it really depends on the candidate.” One calm follow-up, once:

“Understood - even a rough band would help me confirm we’re in the same ballpark. What would the role pay for a strong hire?”

A rough band is commonly an easy yes for someone who knows the exact one, and recruiters typically do. If they deflect a second time and turn it around - “well, what were you looking for?” - stop. Don’t improvise a number to fill the silence; that moment has its own script, and it’s here: the salary expectations answer. And if a company won’t name any band before the onsite, that’s not a wall, it’s information: the number conversation has been moved to the offer stage, so walk in knowing how to respond if the offer lands low.

The mistakes that cost the most: waiting until the offer to learn the band (commonly the most expensive discovery in the process) · answering a deflection with your own number - you asked precisely so you wouldn’t have to go first (if it slipped out anyway, that’s recoverable) · apologizing your way into the question (“sorry, I know this is awkward” turns a routine question into a favor) · asking the hiring manager mid-loop instead of the recruiter up front.