When to talk about money in an interview
There is a version of this advice that says never bring up money first. There is another that says get the number on the table immediately so nobody wastes time. Both are wrong sometimes, and the difference is which stage you are in.
The rule
Money follows scope.
Every stage of a hiring process is answering a different question, and compensation cannot be settled before the question “what is this job?” has an answer. Once it does, money belongs on the table immediately — waiting buys nothing and costs leverage, because a company that has decided it wants you has already started spending its budget on you in its own head.
So the practical rule: do not raise money before the role is defined, do not wait once it is.
Stage by stage
Screen (first call, recruiter).
They will ask for expectations almost immediately, because the band is the first filter. Two useful answers:
“Before I anchor on a number — what’s the range for this role?”
and, if they will not name one:
“For the scope as I understand it, I’d be looking at [range]. Does that fit your band?”
You are not committing to a number; you are testing whether the process is worth continuing. A recruiter who refuses to give any range at all has told you something.
Hiring manager (first interview).
This stage is about the work. Ask what success looks like, what the team’s constraints are, what the last person in the role struggled with. You are building the case you will use later — “you said the priority this year is X, and that is what I did at Y” is the sentence that wins the raise, and you cannot say it if you did not ask.
If they raise money here, answer in scope terms: “For the level we’ve discussed, I’d expect [range]; I’m more focused on the scope right now.”
Late rounds / panel.
Now you have two things you did not have before: the real scope, and their interest. This is where you gather the last evidence — the band, the level, who decides.
Offer.
Now the negotiation happens, and it happens once. See the counter-offer question: a specific number, a reason that is not you, and a fallback you would accept.
“What are your salary expectations?”
The single most common question, and the one with the worst default answer. “I’m flexible” invites the lowest number they can justify. A bare number anchors you, and it is usually anchored low because you are guessing.
Three answers, by what you know:
If you know their range:
“You mentioned [range]. Given the scope we’ve discussed, I’d be at the top of that — does that work?”
If you do not know their range:
“I’d rather not guess before I understand the scope — what band is this role in?”
If they insist:
“Based on what we’ve discussed, [range], and I’d expect to be at the upper end because of [specific reason].”
Notice that none of these is a refusal to answer. They are answers to a different question — what is the role worth — which is the question you actually want to be negotiating.
The three things that cost the most
Naming a number too early. Everything after it is a discussion about that number rather than about your value.
Naming a range without deciding where in it you are. If you say “100 to 130”, you have offered them 100 and asked them for 130.
Accepting “we’ll discuss compensation at the end”. That is fine as a sequence, but get the band now. “Happy to leave the number until later — what’s the range for the role?” is a fair question at any stage, and in many places a required one.
The preparation that makes all of it easy
Before the first call, write down three things:
- Your number — the one you will say out loud, alone, so the first time you hear it is not in the interview.
- Your reason — the market data, the scope, the competing offer. Something they can repeat to someone else.
- Your walk-away — the number below which you decline, decided calmly and in advance.
The conversation is much easier when you have already had it once, with yourself.