How to Ask About Salary Range Before an Interview (Without Torching the Process)

A Gartner survey of nearly 3,500 candidates, published in August 2023, found that 44% had decided not to apply to a job in the prior 12 months because the description left out salary information. In the same survey, 68% said they expect postings to include pay, and 64% said they are more likely to apply when it’s there.

The appetite for the number is not controversial. The awkward part is procedural: how to ask about salary range before an interview, who to ask, and what to say when the answer comes back vague. Most advice on this stops at “know your worth,” which is useless at 9pm when you’re staring at a recruiter’s calendar link and wondering whether a question about money kills the whole thing.

It doesn’t. Asking is a screening step, and it screens in both directions.

Asking early is a screening step, not a red flag

A first-round screen costs you thirty minutes. A full loop costs a day, sometimes two if there’s a take-home attached. If the approved band tops out well below your floor, every hour after that is waste on both sides. Recruiters understand this better than candidates do, because they’re the ones who lose the req when an offer collapses over money in week six.

It also isn’t 2019 anymore. Indeed Hiring Lab found that as of August 2023, half of US job postings on Indeed included some employer-provided salary information, up from 18% in February 2020. The spread was uneven. Colorado, which has had a disclosure law in place the longest, sat at 81%. Mississippi came in at 33%.

Legislation drove much of that shift. GovDocs, which tracks employment law compliance, publishes a list of US states that require disclosure of a pay range under some set of circumstances, along with effective dates: Colorado in January 2021, California and Washington in January 2023, New York in September 2023, Illinois and Minnesota in January 2025, New Jersey in June 2025, Vermont in July 2025, and Massachusetts in October 2025, with Virginia and Maine listed for 2026 and Delaware for 2027. GovDocs is careful to note the requirements are not identical. Some jurisdictions require the range in the posting itself. Others require an employer to give an applicant the range at a specified point during the hiring process, or on request.

None of that is legal advice about your situation, and coverage varies by employer size and location. What it does explain is why the question has gotten routine. In a lot of places, employers already had to build an internal answer to “what’s the range?” Asking is no longer an ambush.

When to ask, and who to ask

The timing rule is simple: ask before you have given them more than half an hour.

In practice, the best moment is your reply to the first message from an actual human being. A recruiter sends an InMail, you reply and ask. A coordinator sends a calendar link, you reply and ask. Second best is the opening of the recruiter screen itself, before you’ve delivered your background.

Who you ask matters more than most people expect.

Recruiters are the right target almost every time. They hold the approved range, they talk about compensation all day, and they’re measured on filling the role rather than on protecting a number. A recruiter who won’t give you any band at all has told you something useful about how that company negotiates.

Coordinators and schedulers usually can’t help. They don’t have the range and often can’t get it, and pressing them just makes an awkward moment for someone with no authority. Ask them to forward instead: “Would you mind passing this along to whoever’s recruiting on the role?”

Hiring managers know the budget because it’s theirs. They’re sometimes less comfortable saying it out loud, especially at smaller companies with no formal comp structure. But if your first contact is the hiring manager rather than a recruiter, ask them. It’s their line item.

The worst time to raise it is after the final round. By then you’ve spent the interview process, the company has an internal number written down, and the question arrives sounding like the opening of a negotiation rather than a filter. It’s also the point where walking away costs you the most, which is backwards. Waiting doesn’t buy leverage. It mostly just moves the disappointment further out, with more of your evenings spent to get there.

The exact wording for how to ask about salary range before an interview

Below are the three places this question actually gets asked, with wording you can lift and edit.

Replying to recruiter outreach by email:

Thanks for reaching out, the role looks interesting. Before we find time, could you send over the range this one is budgeted at? I’d rather flag a mismatch now than take up an hour of your week. Happy to share what I’m targeting once I’ve seen it.

Opening a recruiter screen:

Quick logistics question before we get into my background: what range is this req approved at? If it lines up, I’d rather spend the rest of our time on the actual job.

The “salary expectations” field on an application form:

Don’t leave a required field blank, and don’t enter a single number. Enter a range whose bottom is genuinely your floor, because the bottom is where the conversation will start. If the field takes free text, this works:

$145,000 to $165,000 base, with some flexibility depending on the rest of the package. Happy to align with the range budgeted for the role.

If the field only accepts one integer, enter your target, not your minimum.

One adjacent thing worth knowing: GovDocs also tracks salary history bans and lists more than twenty states and localities that restrict employers from asking what you currently earn. As GovDocs summarizes the general pattern, employers can usually ask about pay expectations but not actual pay history. So if a form or a recruiter asks for your current salary rather than your expectations, redirecting is standard practice: “I’ve been targeting roles in the $X to $Y range. What’s budgeted for this one?”

There’s a fourth channel that doesn’t get scripted much, because it only exists if you’ve skipped the queue: messaging a hiring manager directly, about a role that may not even be posted yet. The tone is different. You’re not asking permission to know, you’re comparing notes:

If the team ends up opening this role, what band would it sit in? I’m currently in the $X to $Y range, and I’d rather know early whether that’s in the same neighborhood as what you’d have budget for.

Easier to send, easier to answer. Nobody is managing a process around it, so there’s no rule to break.

When they deflect, bounce it back, or post a $90k to $260k range

Deflection sounds like “we’d like to learn more about you first,” or “compensation depends on experience.” The move is to shrink the ask rather than repeat it:

Makes sense. I’m not looking for a committed number, just the band the role was approved at, so neither of us spends a whole loop on a mismatch.

A second common variant is “the range depends on what level you come in at, so we’d need to interview you first.” That one is sometimes honest. The answer is to ask for the endpoints anyway: “Understood. What’s the band for the lower level and the band for the higher one? If the lower one works for me, the leveling question stops being a risk for either of us.”

If they still won’t say, that’s an answer in itself. Companies that hold the number through three rounds tend to be the same companies that open low at offer stage. Keep going if the role is worth it, but calibrate.

Then there’s the bounce-back: “What are your expectations?” Answer it, and hand the question straight back.

Based on what I’m seeing for comparable roles at this level, I’d be looking at $150,000 to $170,000 base. Does that fit what’s approved here?

Answer once, not twice. If they take your number and still won’t confirm a band, the asymmetry is deliberate, and you should price that in.

Then there’s the posted range that means nothing. $90,000 to $260,000. Or $120,000 to $340,000 for a req titled “Senior/Staff/Principal Engineer.” Bands that wide usually cover several levels, several geographic tiers, or both, which is partly a side effect of disclosure requirements meeting a good-faith-estimate standard. Arguing about whether the range is real goes nowhere. Asking to have it resolved works:

The posting lists $90k to $260k. Which level is this req actually approved at, and where in that band do people typically come in at that level?

A sharper follow-up, if the conversation is going well: “Where did the last person hired onto this team land in that range?” Recruiters answer that more often than you’d think, and it converts a marketing range into a real one.

Why all of this is easier when you’re not applicant #400

Everything above is a workaround. It exists because the application funnel has etiquette, and etiquette is what makes a simple question feel expensive. There’s a sequence you’re supposed to follow, a recruiter juggling forty open roles who has been coached to hold the number, and a few hundred other applicants behind you who make you replaceable enough that asking feels like a risk.

Change the entry point and the etiquette evaporates. When the first conversation is with the hiring manager who owns the budget, pay is one of the logistics you sort out, next to scope and start date. Nobody is offended, because there’s no stage of a process to violate. Direct outreach also tends to reach the role before it has hardened into a posting with a $170,000-wide band, which is usually when the number is most movable.

That’s most of the case for contacting hiring managers directly instead of waiting your turn. Knowing how to ask about salary range before an interview is really a defensive skill, useful for getting through a process somebody else designed around their own interests. Start the conversation yourself and there’s a lot less to defend against. Asking about money stops being delicate once you’re a person someone wants to talk to instead of a row in an applicant tracking system.

The slow part is the research: working out who actually owns the role, finding something specific to say, and writing a message that doesn’t read like a template. Angld.AI handles that pipeline. Paste a job posting and it identifies the decision maker, researches them, and drafts a personalized outreach message in about a minute, so the compensation conversation can happen in a reply thread instead of round four.