Salary Expectations — What to Say Before You Know the Offer
Whoever names a number first gives up information. But refusing outright gets people filtered out, so the skill is deflecting once, gracefully, and then answering well.
When It Gets Asked, and Why
The same words mean different things at different stages, and the right answer changes with them.
Almost always a filter. They have a band and want to know whether you fit inside it before spending anyone's time. A hard refusal here is where most candidates lose the process entirely.
A required field with no room for nuance. Put the middle of your researched range, or the band's midpoint if they published one. Leaving it blank often blocks submission.
Usually genuine curiosity about whether the level matches. Here you can talk about scope and total package rather than a single figure.
Now the number matters, and now you have leverage you did not have before, because they have chosen you. This is the point to be specific.
Try to get their range first, but never at the cost of the process. Deflect once, politely and with a reason. If they ask again, answer with a researched range and say what it is based on. Deflecting twice reads as game-playing, and recruiters do filter for it.
Eight Steps to a Number You Can Defend
Every strong answer to this question is built before the interview, not during it.
Many postings, and all roles in pay-transparency jurisdictions, state one. Asking for a number they have already published is a preventable own goal.
Comparable postings, a salary site for your city and level, and one person who actually does the job. Any single source will mislead you.
The same title can differ by fifty percent between cities, and between a startup, a bank and the public sector. A national average is rarely your number.
Your walk-away floor, your realistic target, and an ambitious-but-defensible top. You will quote the top two and never mention the floor.
Pension, bonus, equity, holiday, remote allowance. A lower base with an eight percent employer pension can beat a higher base without one.
Base, bonus, and employer pension as one total. In places where asking salary history is legal you may be asked, and vagueness costs you.
Not just the digits — the justification. Based on comparable roles at this level in this city is what turns a number into a position.
It has to sound relaxed rather than evasive. The words matter less than the tone, and tone only comes from saying it aloud.
Eight Situations and Exactly What to Say
Scripts you can adapt. Each is short on purpose — this is not a topic that rewards elaboration.
The first deflection
"I would rather understand the scope properly first. Do you have a band budgeted for the role?" Said warmly, this works most of the time. It is a fair request and most recruiters answer it, because they have a band and want the same information you do.
They ask again after you deflect
"Of course. Based on comparable roles at this level in Manchester, I have been working to somewhere in the region of £52,000 to £60,000, and I am flexible depending on the rest of the package." Answer properly the second time. Deflecting twice is what gets people filtered.
A required field on an application form
Enter the middle of your researched range as a single figure, or the band midpoint if they published one. Never put zero, negotiable or a placeholder — forms are frequently filtered numerically, and a nonsense value can drop you before a human reads anything.
They ask what you currently earn
"My current package is around £48,000 including bonus. That said, I am looking at this role at the level it is scoped, which puts my expectation in the mid-fifties." In many places asking is now unlawful; where it is not, answer with the total and pivot immediately to the new role's value.
You are underpaid now
"I have been below market where I am, which is part of why I am looking. I am basing my expectation on what the role is worth rather than on my current number — around £58,000 for this scope." Say it once, without resentment, and anchor to the market.
You are asking for a big step up
"It is a step up from where I am, and I am going in with my eyes open. The scope here is materially bigger — three direct reports and the vendor relationship — and I have priced it at what that role goes for, which is around £70,000." Name the gap yourself before they do.
The range is below your floor
"That is honestly below where I can go — I am working to a minimum of about £55,000. I did not want to waste your time, so is there any flexibility at the top of the band, or is that firm?" Say it early. Continuing through four rounds you cannot accept helps nobody.
They make an offer at the bottom of the band
"Thank you — I am genuinely pleased. I was hoping for something closer to £62,000 given the vendor management piece we discussed. Is there room to move?" One specific number, one specific justification, then silence. Do not fill it.
Eight Things That Decide How This Goes
Salary conversations are lost on delivery far more often than on arithmetic.
One graceful redirect is normal and expected. A second one reads as gamesmanship and is a common reason recruiters quietly stop progressing someone.
A range shows you have researched a market rather than picked a figure. Keep it tight — about eight thousand, or ten percent — since a wide range invites the bottom of it.
Employers hear the lower number. Your stated floor should be the figure you would actually be pleased with, not the least you could survive on.
Based on comparable roles at this level converts a demand into a position. Naked numbers invite haggling; justified ones invite checking.
Pension, bonus and holiday are all real money and often more flexible than base. It also gives both sides somewhere to move when base is capped.
It anchors the whole negotiation to your past employer's budget rather than to this role's value.
The pause after a figure is the most productive silence in any interview. Whoever speaks first tends to concede.
This is a normal commercial conversation both sides have had many times. Treating it as a confrontation makes it one.
Four Questions Worth Asking
The number alone is not the deal. These reveal the rest of it.
"What is the band for this role, and where in it would I sit?"
The second half matters more than the first. Being offered the bottom of a wide band is a very different outcome from the middle.
"How does the bonus actually work, and what did it pay out last year?"
Target bonus and actual bonus are frequently different numbers. The historic figure is the honest one.
"What is the employer pension contribution?"
The most commonly ignored part of a package, and often worth several thousand a year in real terms.
"When do salary reviews happen, and what drives an increase?"
A slightly lower start with a real review cycle can beat a higher one that never moves.
"I want to make sure I understand the scope before putting a number on it — the vendor management piece sounds like it might sit above what the title suggests. Do you have a band budgeted? Happy to tell you where I am if it is easier to start there."
Six Ways This Conversation Goes Wrong
Recruiters need a band match to advance you. Deflect once, then give a researched range — total refusal is a common way to be quietly dropped.
An unjustified number invites haggling. Attach it to comparable roles at this level in this location.
It anchors your new pay to your old employer's budget. Price the role, not your history.
Twenty thousand of spread tells them you do not know the market, and they will hear only the lower end. Keep it to about ten percent.
Pension, bonus and holiday are real money and often more negotiable than base. Ask before you decide the offer is low.
Ask early. Finding out after four rounds wastes your time and theirs, and neither side gains from the politeness.