Fifteen minutes into a screening call, the recruiter went quiet, then asked it like it was nothing: "So, what are your salary expectations for this role?"
I said a number. It felt bold at the time. Two weeks later the offer came in at exactly that number — and when I later found out the band topped out $12,000 higher, I understood what had happened. I hadn't negotiated. I'd volunteered my own ceiling and called it confidence.
That question is the single most expensive moment in most job searches, and almost nobody treats it that way. You're relaxed. It sounds administrative. And the number you blurt out becomes the gravity the whole offer falls toward.
Here's how to answer it so you don't do what I did.
The question isn't really a question
When a recruiter asks your salary expectations early, they're not curious about your hopes. They're doing two things: screening you out if you're wildly above budget, and — more often — getting you to set a number they can anchor low against.
Think about the asymmetry. They know the band. You usually don't. They do this ten times a week. You do it every few years. When you answer first, you're the only person in the conversation negotiating blind.
So the goal on an early call isn't to give a great number. It's to not hand over your ceiling before you've seen theirs.
Your first move: turn the question around
The cleanest response deflects without dodging. You stay warm, you stay collaborative, and you put the number back where it belongs — with the people who actually know the budget.
Try some version of this, out loud, in your own words:
"I'd love to make sure this is a fit on both sides. Do you have a budgeted range for the role? I'm happy to tell you whether that works for me."
Most recruiters will give you a range, or at least a top number. That single sentence flips the entire dynamic — now they've anchored, and you get to react instead of guess. I've watched people save five figures with one redirect they almost didn't try.
Some recruiters push back: "We'd really like to hear your expectations first." That's fine. It's a script, not a standoff. You have two good options from there.
Option one: give a range anchored on research, not hope
If they won't move first, don't refuse — that reads as difficult. Give a researched range, and make the bottom of your range a number you'd genuinely accept, because they will hear the bottom.
This is the part most people get backwards. They pick a range like "$90,000 to $110,000" thinking they're aiming high. The employer hears $90,000. Your "stretch" became your floor.
So build the range deliberately: put your actual target near the bottom, and let the top be ambitious. If you'd be happy at $115,000, you say "I'm looking in the range of $115,000 to $130,000, depending on the full scope and benefits." Now the gravity pulls toward a number you already like.
The "depending on" clause matters too. It signals that salary is one lever among several, which keeps equity, bonus, and flexibility on the table instead of collapsing everything into base pay.
This is exactly where going in blind hurts you most. Before any call where this might come up, run your role and city through SalaryAsk's free analysis — you'll see the real market range for your situation in about three minutes, so the number you give is anchored to data instead of a gut guess. Walking into that question knowing the band is the difference between reacting and bracing.
Option two: anchor to your current compensation (carefully)
If you're underpaid now, never anchor to your current salary — you'll drag the new offer down with you. See what to do when you're underpaid right now for how to break that cycle instead of repeating it.
But if you're already paid well, your current total compensation can be a useful anchor: "In my current role my total comp is around $140,000, so I'm looking for a move that reflects a step up from there." You've set a high floor without naming a single demand.
One caution: in a growing number of places, employers can't legally ask your salary history at all. If they ask anyway, you don't have to answer — you can pivot straight back to the role's budget. You're not being evasive; you're declining a question they often aren't supposed to ask.
What never to say
A few answers feel safe and quietly sink you:
- "I'm flexible / open." This sounds easygoing. It reads as "I have no idea what I'm worth," and it invites a lowball to see what you'll accept.
- "Whatever's fair for the role." Same problem, dressed up politely. Fair according to whom, anchored to what? You've said nothing and given away everything.
- A single exact number, early. "I'm looking for $108,000" on a first call is the mistake I made. It caps you before anyone's discussed scope, and it leaves zero room to move up as you learn more.
- A number with an apology attached. "I was kind of hoping for maybe around, if possible, $120k?" The hedging tells them the number is soft. Say it plainly and stop talking.
That last one is underrated. After you give a number or range, go quiet. Let the silence sit. The person who fills an awkward pause first usually concedes something, and it doesn't have to be you.
When they make the first offer anyway
Sometimes you deflect successfully and they just... make an offer. Good. That's the position you wanted. But an offer is a starting point, not a verdict — 88% of job offers survive a negotiation attempt, and employers almost always leave room precisely because they expect you to ask.
So when the number lands, don't accept on the call. "Thank you — I'm really excited about this. Can I take a day to review the full package?" Then you counter in writing, calmly, with your reasons. If you want the exact wording, the salary negotiation email template walks through it line by line.
The expectations question and the counter-offer are two halves of the same skill: knowing your number, and holding it without flinching.
The real mistake isn't the number — it's answering unprepared
Every version of getting this wrong comes from the same root: the question catches you off guard and you improvise. You can't improvise your way to a number you've never calculated.
So do the boring work before the call. Know the market band. Know your target, your floor, and the one sentence you'll use to deflect. Say that sentence out loud a few times so it sounds like you, not like a script you're reading. When the recruiter goes quiet and asks the question, you won't feel the jolt — you'll feel ready.
That's the whole game. The people who win this moment aren't bolder or luckier. They just did five minutes of prep the person on the other end assumed they'd skip.
FAQ
Should I give a number first or wait for them to? Wait, if you can. Ask for their budgeted range first — it flips the anchor to your advantage. Only give a number if they genuinely won't move, and then give a researched range with your target near the bottom.
What if the recruiter insists I answer first? Give a range rather than a single figure, anchored on real market data for your role and location. Make the bottom of the range a number you'd actually accept, since that's the number they'll hear.
Is it okay to refuse to share my salary expectations? You don't have to share a number, but flat refusal can feel adversarial. Redirect instead: ask for their range, or say salary depends on the full scope and you'd like to understand the role better first. In many regions they also can't legally ask your salary history.
What salary range should I give for a job? One where your true target sits near the low end and the top is ambitious but defensible from market data — typically a spread of about 15–20%. Research the real band for your role and city first so the whole range is credible.
Does giving a high number risk getting screened out? Rarely, if it's within the realistic market band. A researched, confident range signals you know your worth. The bigger and far more common risk is anchoring yourself too low and never recovering those thousands.