Answering the Salary Expectations Question

Why the question is asked at all

It helps to know what the recruiter is doing, because it is rarely a trap. Most of the time they are screening for fit against a band that already exists — they have an approved range, they have candidates to process, and they are trying to avoid spending four rounds on somebody who was never going to accept the band. That is a legitimate use of the question.

Sometimes it is an anchoring move, particularly where the band is wide and the recruiter has discretion. If you name a number below what they were prepared to pay, very few employers will correct you upward, and that is the risk the question carries for you. Both readings can be true of the same recruiter.

Both readings point the same way. Answering with a figure you cannot support serves neither purpose well, and answering with a figure grounded in something checkable serves the screening purpose while protecting you from the anchoring one. That is what a good answer has to do at once.

The best answer where the law allows it

Redirect the question to their range before naming anything yourself. “What has been budgeted for this role?” is a natural response to a question about money, it puts the number where it belongs — on the job rather than on you — and in a growing number of states and cities the employer is obliged to tell you anyway. Asking is not presumptuous where the law already requires it.

This works better than candidates expect because it is a reasonable question rather than an evasion. The role has a band; the recruiter knows it; and a candidate asking about the range is behaving like somebody evaluating a job rather than somebody who will accept anything offered. Recruiters read that distinction more quickly than candidates expect.

If they answer, you now have their number before they have yours, which is the strongest position available in the whole exchange. If they decline, you have learned something about how the process will run and you can move to the next approach without having lost anything at all. A politely declined question costs you nothing at all.

If you have to name something

Name a range rather than a point, put your target near the bottom of what you say, and attach a source. “Based on published ranges for this role in this market, I’m looking at $95,000 to $110,000” is a sentence that does three things at once: it answers the question, it demonstrates you have done the work, and it invites a conversation about the evidence rather than about your expectations in the abstract. Evidence is much easier ground to stand on than preference.

The source is what separates a strong answer from a weak one. A figure with a basis behind it can be discussed, checked and argued with. A figure with nothing behind it can only be accepted or refused, and where it is below what the employer would have paid, it will simply be accepted.

Put your target at or near the bottom of the range you name, because employers hear the lower number as the real one. If you say $95,000 to $110,000, expect the conversation to start near $95,000, and set the range accordingly rather than hoping to be met in the middle. Nobody meets you in the middle of a range you named.

What you do not have to answer

Your salary history is a separate question and in many states and cities it is unlawful to ask. Even where it is lawful, you are not obliged to answer, and volunteering it is the one move worth avoiding — several of the laws that prohibit asking permit an employer to rely on a figure the candidate offered without being asked for it. Volunteering is the one move that waives the protection.

Keep the two apart in your own head. What you are looking for is a statement about the role and the market. What you were previously paid is a fact about a different job at a different employer, and it has no bearing on what this one is worth.

If pressed, “I’d rather focus on the value of this role — based on the market, I’m looking at X” is a complete answer that declines without refusing anything. It also moves the conversation back to the role.

Deferring, when it is genuinely early

Sometimes the question arrives before you know enough to answer it, and saying so is legitimate. “I’d want to understand the scope a bit better before putting a number on it — could we come back to this once I’ve spoken to the hiring manager?” is reasonable at a first screening call and is usually accepted without comment. It works because it is true rather than because it is clever.

It works exactly once in any given process. Deferring twice reads as avoidance and starts to cost you the goodwill you will want later, so use it when you genuinely need the information rather than as a tactic. And when you defer, come back to it yourself rather than waiting to be asked again — that keeps it collaborative.

The two failure modes

The first is naming a number with nothing behind it. It caps you, because employers rarely offer more than a candidate asked for, and it cannot be defended when questioned. If you cannot say where a figure came from, it is not ready to be said out loud.

The second is refusing to engage at all. A candidate who will not discuss compensation in any form through several conversations reads as difficult, and recruiters have other candidates. The redirect works precisely because it engages with the question rather than dodging it, which is why it is not the same thing as refusing.

Between those two there is a wide space where almost any prepared answer performs well. The preparation is the variable rather than the wording. Almost any prepared sentence outperforms an improvised one.

Preparing the answer before the call

Do the work once and then reuse it across every conversation. Establish the percentile range for your occupation in your metropolitan area, find posted ranges for comparable roles in a jurisdiction that requires them, and decide three numbers: your target, the figure below which you would decline, and the range you will say out loud. Three numbers, decided once in advance, reused in every conversation.

That takes about twenty minutes and it changes the character of every subsequent conversation. The reason people give bad answers to this question is almost never that they felt obliged to answer — it is that they were asked about money and had nothing prepared to say instead. Twenty minutes removes that entirely.

Write the sentence down and say it once before the call. It is the only part of an interview where a rehearsed sentence is straightforwardly better than an improvised one. Say it aloud once before the call.

What to do with the range once they give it

If they name a band, treat the midpoint as the realistic anchor for somebody who matches the requirements, and the upper portion as reserved for candidates exceeding them. Ask the second question too: what would put a candidate at the top of this range? The answer tells you exactly what to demonstrate in the remaining conversations.

If the range is very wide, that usually means the level is not fixed and the process is partly a leveling exercise. In that case the useful move is to make your case for the higher level explicitly and early, rather than performing well and hoping somebody places you there. Nobody levels you up on your behalf.

And if their range sits below your floor, say so warmly and immediately rather than continuing. “That’s below where I can be for a role at this scope — is there flexibility, or should we leave it here?” saves everybody time and occasionally produces a better number than any amount of further process would have. Clarity early is worth more than politeness late.