● Interview question

What to say when a recruiter asks about your salary expectations

By The Don't Wing the Interview Team ·

The salary expectations question is the one moment in a screening call where a single sentence can cost you real money, and the defense is entirely in the preparation: research a defensible range before the phone rings, and when asked, give that range with your target sitting near its top. Candidates lose here not because they negotiate badly but because they improvise a number under mild social pressure.

You are allowed one polite deflection — asking for the role's budgeted range before naming yours is reasonable and often works, especially now that many employers post or disclose ranges. But deflect once, not twice. A recruiter who asks a second time is telling you the conversation does not move forward without a number, and repeated dodging spends goodwill that a prepared range would have earned.

One thing worth knowing before the call: whether the employer must publish a salary range depends on where the job sits — several US states and a growing number of countries require ranges in postings, while others do not. Check the posting and the company's careers page first; when a published range exists, your answer should be built on top of it, not invented alongside it.

What the interviewer is listening for

  • Whether a real number arrives: endless dodging reads as either unprepared or hiding something.
  • Budget fit — the practical purpose of the question is to find mismatches before six more hours of interviews.
  • Evidence of research: a range with a rationale sounds like market data; a suspiciously round number sounds like a wish.
  • Delivery: candidates who state their range plainly are treated as knowing their worth; candidates who apologize their way to a number invite a low offer.
  • Flexibility signals — a mention of total compensation or learning more about scope tells them a deal can be shaped.
  • Self-awareness about level: a range wildly above or below the role suggests the candidate misreads either the market or themselves.

How to structure your answer: Research, range, one redirect

  1. 01

    Build the range before the call

    Triangulate from at least three sources: ranges on comparable postings (mandatory in several states and countries, so they exist to find), salary data sites, and if possible one human being who knows the market for this role. Write the range down.

  2. 02

    Redirect once, pleasantly

    “Happy to talk numbers — do you have a budgeted range for the role?” If they share it, anchor within its top portion. If they decline or ask again, move to your range immediately; a second deflection costs more than any number.

  3. 03

    State the range, target on top

    Name a band with your true target near its ceiling — wide enough to negotiate in, narrow enough to be credible — in one plain sentence with one line of justification. Employers gravitate toward the bottom of whatever range they hear, so the bottom must be a number you would still accept.

  4. 04

    Attach the flexibility clause

    Close by keeping the door open: the full picture depends on scope and total package. This lets a slightly-under employer keep talking instead of screening you out, and preserves your leverage for the offer stage.

A weak answer — and what the interviewer hears

“Oh — I don't really have a specific number in mind. Money isn't the main thing for me, I'm more interested in the opportunity. I'm currently on about 42, so… anything above that, really? I'm sure whatever you normally pay is fine. I'm pretty flexible.”
  • An invitation to make the lowest offer in the approved band — “whatever you normally pay is fine” will be taken literally.
  • The current salary was volunteered unprompted, handing over the single most useful anchor a negotiator can have.
  • “Money isn't the main thing” rarely convinces anyone; it reads as either naivety or a line, and it will not survive the first below-expectations offer.
  • No research means no market awareness — which quietly downgrades the interviewer's read of how this person prepares for anything.

Example answers that work

Illustrative examples — build yours from your real experience, never from a script.

Marketing coordinator — answering directly with a researched range

Sure — I've done my homework on this. Based on postings for marketing coordinator roles in the metro area with similar scope, the salary data I could find, and a couple of conversations with people doing this job at agencies nearby, I'm targeting the fifty-two to fifty-eight thousand range, and toward the upper end of that given that this role owns email campaigns end to end and I've run that channel solo for two years, including the marketing-automation migration at my current company. That's my base range — I think about offers in terms of the total package, so benefits and growth path genuinely factor in for me. Does that band line up with what you've budgeted for the position? If we're close, I'm confident the rest is workable once we both know the fit is right.

Why this works

  • The range arrives with its sources attached, converting a demand into a market observation.
  • The upper-end anchor is justified by a specific, role-relevant capability rather than by wanting more.
  • The total-package clause and the closing question keep the tone collaborative and the negotiation open.
  • There is no apology anywhere — the number is stated the way a prepared person states facts.

Common mistake: Shaving the range down mid-sentence after watching the recruiter's face — the flinch-discount tells them the number was soft, and every later negotiation starts from the reduced figure.

Senior product manager — one redirect, then a confident answer

Happy to get into numbers — could you share the range that's been budgeted for the role? I ask because senior PM comp varies a lot with scope, and I'd rather react to your band than guess at it. [If the recruiter declines:] No problem — here's my thinking. For a senior product manager owning a revenue line, with this company's stage and the market rates I'm seeing for equivalent roles, I'm looking at one-forty to one-fifty-five base, and I'd want to be in the top part of that range — I've shipped zero-to-one products and run monetization, which is most of this job description. Base is only one lever for me, though: equity and bonus structure genuinely move my flexibility, so if the whole package is strong I have room. Mostly I want to establish today that we're in the same neighborhood, so neither of us spends five interviews discovering we weren't.

Why this works

  • The deflection is used exactly once, with a stated reason, and the fallback answer is ready — no second dodge.
  • The range is wide enough to negotiate in but anchored explicitly at the top with evidence.
  • Naming equity and bonus as levers signals senior-level negotiation fluency without starting the negotiation.
  • The closing sentence reframes the question as mutual efficiency, which is precisely how the recruiter sees it.

Common mistake: Deflecting a second and third time to “keep leverage” — past one redirect, the recruiter stops hearing strategy and starts hearing someone difficult to close, and some will end the process right there.

Other ways this question gets asked

  • “What salary range are you looking for?”

    The recruiter-screen standard, often asked in the first ten minutes to check budget fit before anyone invests further. A prepared range answers it in one breath.

  • “What are your compensation expectations?”

    The word “compensation” invites a total-package answer. Give your base range and note that bonus and equity affect your flexibility — it shows fluency without opening a negotiation.

  • “Where do you need to be on salary for this to make sense?”

    This phrasing hunts for your floor. Do not hand it over raw — answer with the same range you prepared, target at the top, rather than confessing your walk-away number.

  • “What are you currently earning?”

    A different question wearing the same hat — and one employers in some jurisdictions may not legally ask. Redirect to expectations: what matters is what the role pays in this market, and you can decline the history politely.

Frequently asked questions

Should I give a number first or wait for theirs?

Try once to hear theirs — “I'd love to know the range budgeted for the role; I'm confident we can meet in it” — because their range is information you can anchor against. If they decline or press again, give your researched range without ceremony. Going second is a mild advantage; being visibly evasive is a real disadvantage. The prepared range makes either order safe.

What if the posting already lists a salary range?

Then the question is really asking where you sit inside it. Anchor to the upper portion and justify it in one sentence tied to the requirements you exceed. Naming a figure above a published band rarely works at screening stage; positioning at its top, then negotiating the full package at offer stage, usually does.

What if my expectation is much higher than my current salary?

Quote the market, not your paycheck. Your range should be built from what this role pays at this level in this location — your current salary is one datapoint, not a ceiling. If asked directly what you earn now, you can decline pleasantly in many places (some jurisdictions bar the question entirely) and redirect: “I'm anchoring on the market for this role, and my range is…”

Can naming a range get me screened out?

Yes — and that is partly the point. If your researched floor is genuinely above their ceiling, discovering it in the first call saves you four rounds of interviews that end in an offer you would refuse. The screening risk to actually manage is the opposite one: quoting so low, out of nervousness, that you are hired at a discount you resent within a year.

Keep preparing