"What Are Your Salary Expectations?" — Scripts That Don't Backfire

There's a specific kind of silence that follows "So, what are your salary expectations?" — the one where your brain runs three calculations at once and lands on "uhh." If you've felt it, you're not bad at interviews. You've just been handed a question designed to make whoever speaks first lose a little.

Here's the reframe that helps: the recruiter isn't trying to trick you so much as protect a budget. Once you stop reading it as an attack, you can answer it like a professional who's done their homework. And homework is the whole game.

Why the question feels like a trap (because it is)

Whoever names a number first sets the ceiling. Say a figure below their budget and they'll happily pay you less than they planned. Say one above and you risk getting screened out before anyone learns why you're worth it. Neither is a great spot — which is why the strongest first move is usually not to name a number at all.

Script 1 — Deflect (early-stage screen)

"I'd love to learn more about the role and the full scope before talking numbers. Could you share the range you've budgeted for this position?"

In the growing number of places with pay transparency laws, they often have to tell you. Let them anchor first.

Script 2 — Anchor with data (when you must give a number)

If they push, don't improvise. Give a researched range with the top quarter as your floor:

"Based on market data for this role and my experience, I'm targeting $X to $Y. Where does that sit against your range?"

Set X at roughly the market median and Y a bit above the 75th percentile. That's not greed — it's where the top quartile of people in your job already sit. Pull your real numbers from the salary data for your role so X and Y aren't vibes.

Script 3 — Redirect to value

"I'm confident we can find a number that works once we both see it's a fit. What does success in this role look like in the first six months?"

This buys time and signals you're focused on the work, not just the paycheck — which, paradoxically, is what makes people want to pay you more.

A quick worked example

Say you're a mid-level marketing manager. National median is roughly $75K, with the 75th percentile closer to $95K. Your anchored range becomes "$78K–$98K," and you let them react. Compare that to blurting "$70K because that's what I make now" — you'd have left real money on the table before lunch.

Move	What it does	Risk
Deflect	Makes them anchor first	Low
Anchor with data	Sets a strong, fair ceiling	Medium
Lowball yourself	Caps your offer permanently	High

The part people skip

Know your walk-away number before the call — the figure below which you'd politely decline. Write it down. When you have a floor in your pocket, your voice stops shaking, because you're no longer afraid of the answer. That calm is worth more than any script.

Want to check what your number should be before the next call? Run your role and city through the market-value check — it takes about a minute and replaces "uhh" with a figure you can say out loud.

FAQ

Should I ever give my current salary? You usually don't have to, and in many states employers can't ask. Redirect to your target range instead.

What if their range is below my floor? Say so kindly: "That's a little under what I'd need to make a move — is there flexibility, or should we revisit later?" A clear, warm no protects your time and theirs.

Is asking for the top quartile too aggressive? No. The 75th percentile is a salary real people in your role already earn. Asking to be paid like them is a normal request, not an outrageous one.