What Are Your Salary Expectations? How to Answer This Tricky Interview Question
Say a number too high and you look out of touch. Say one too low and you leave money on the table before you've even got the job. Here's the framework that gets it right, every time.
Why This Question Is a Trap
"What are your salary expectations?" is one of the few interview questions where the answer is genuinely a negotiation move, not a competency demonstration. Every other question on this site β behavioural, situational, motivational β rewards a well-structured, honest answer. This one rewards strategic ambiguity, and that trips people up because it feels dishonest to be vague when everything else in the interview has rewarded specificity.
The trap works in both directions. Quote a number that's too high relative to the role and band, and you risk being screened out before you've had the chance to demonstrate your value β recruiters rarely come back to negotiate down, they simply move to the next candidate. Quote a number that's too low, and even if you get the offer, you've anchored the entire negotiation at a figure below what the employer was willing to pay, and it is very difficult to claw that back once an offer letter has been issued.
In any negotiation, the party who names a number first gives the other party information they didn't have to give up. Recruiters know this, which is exactly why they ask the question early β often before you've even had a first interview. Your goal is not to avoid answering (refusing to engage looks evasive), but to answer in a way that protects your position while still being genuinely helpful to the hiring process.
It's worth understanding the recruiter's side of this too. Most graduate and early-careers roles at large employers β investment banks, the Big Four, tech firms β actually have very little room to negotiate, because salaries are set centrally by band and cohort. In those cases, the question is less of a negotiation and more of a screening check: they want to confirm you're not expecting significantly more than the role pays, and that you understand the market. Recognising which situation you're in changes how much weight to put on your answer.
Do Your Salary Research First
You cannot answer this question credibly without knowing the market rate for the role, seniority level, sector, and location you're applying for. Walking into an interview without this research is the single biggest reason candidates either freeze on this question or blurt out a number that's wildly off.
Where to find reliable salary data
| Source | Best For | Limitation |
|---|---|---|
| Employer's own graduate careers page | Large graduate schemes often publish a headline starting salary directly | Rarely shows total package (bonus, benefits) or regional variation |
| Glassdoor / Indeed salary reports | Self-reported ranges from real employees at named companies | Sample sizes can be small; figures can be dated or unverified |
| LinkedIn Salary insights | Aggregated data by job title, location and experience level | Broad job title matching can pull in unrelated roles |
| University careers service graduate outcomes data | Sector-specific benchmarks for recent graduates from your course | Often lags by 1β2 recruitment cycles |
| Recruiters and current employees (network) | The most current, most specific information you can get | Requires an existing or newly built professional connection |
Cross-reference at least three sources before settling on a range. If your sources disagree significantly, that's useful information too β it tells you the role or employer has wide pay variation, and you should lean toward the middle of the combined range rather than anchoring on the highest figure you found.
Graduate offers at large employers β particularly in finance, consulting, and tech β often include a signing bonus, a performance bonus, pension contribution, and benefits that can add meaningfully to the headline base salary. When you research "market rate", make sure you're comparing total compensation, not just the number in the job advert, or you may end up requesting a base salary that's actually higher than the role's full package because you didn't know a bonus existed.
For UK graduate schemes specifically, published market data broadly places non-London graduate starting salaries in the high-Β£20,000s to mid-Β£30,000s, and London-based graduate schemes β particularly in banking, law, and consulting β meaningfully higher, often into the Β£40,000s once signing bonuses are included. These are broad market ranges, not guarantees for any specific employer, and you should always verify against current, role-specific sources before relying on them.
The R.A.R. Framework
Use this three-part framework any time you're asked about salary expectations, whether on an application form, in a phone screen, or in a final-round interview.
| Step | What It Means | Why It Works |
|---|---|---|
| R β Research | Ground your answer in real market data for this role, level, sector and location β never guess | Shows you're informed and commercially aware, not naive or greedy |
| A β Anchor with a range | Give a realistic range (not a single figure) with your genuinely acceptable minimum near the bottom | A range signals flexibility while still giving the recruiter something concrete to work with |
| R β Reaffirm fit | Close by reaffirming that the role and the opportunity matter more to you than the number | Keeps the conversation focused on mutual fit rather than turning into a price negotiation this early |
Example script
"Based on my research into similar graduate roles in [sector] at companies of this size in [location], I'd expect a package somewhere in the region of [Β£XβΒ£Y], including any performance bonus. That said, I'm genuinely open to discussing this further β the fit with the team and the opportunity to develop in this role matter more to me than hitting an exact figure, so I'd welcome your view on where this role typically sits."
A single figure invites a binary yes/no response and gives the recruiter no room to manoeuvre without you appearing to have "won" or "lost". A range achieves the same goal β giving them a workable number β while leaving room for the offer to land anywhere within it. Keep your range realistic and no more than 10β15% wide (for example Β£32,000βΒ£36,000, not Β£28,000βΒ£40,000), or it reads as unfocused rather than flexible.
What to Say Early in the Process
Many candidates are asked about salary expectations in a first screening call, sometimes before they've had a chance to properly understand the role. Answering too specifically at this stage can lock you in prematurely. The goal early on is to demonstrate that you've thought about it, without committing to a figure you might want to revise once you understand the full scope of the role.
Deflecting gracefully without evading the question
If you're asked before a first interview, it's reasonable to redirect briefly toward understanding the role first, provided you don't dodge the question entirely: "I'd like to understand a bit more about the scope of the role and what a typical progression path looks like before settling on a specific figure, but based on my research so far, I'd expect something in the region of [range] for a role at this level."
- Never say "I don't know" or "whatever you think is fair." This is the single most common mistake β it signals you haven't researched the role and hands the recruiter total control of the negotiation with no anchor from your side at all.
- Never refuse to give any number when directly pressed twice. A graceful deflection once is fine; refusing entirely after being asked again reads as evasive rather than strategic.
- Do ask what the budgeted range for the role is, if appropriate. Many recruiters will share this if asked directly and professionally β it removes the guesswork entirely and is a completely normal question to ask in 2026's hiring market.
If you're applying to a structured graduate scheme with a fixed cohort intake β most Big Four, banking, and large corporate schemes work this way β the salary is almost always fixed and published, and the "salary expectations" question at this stage is a screening check, not a genuine negotiation. Answering with a figure close to their published band is safer here than trying to anchor high, since there is no flexibility for them to move toward you.
Answering on Application Forms
Online application forms often force a numeric answer where a verbal deflection isn't possible. This requires a slightly different approach, since you can't add nuance or tone the way you can in conversation.
- If the field accepts a range, use one. Enter your researched range directly (e.g. "Β£32,000βΒ£36,000") rather than a single number, for the same reasons outlined in the R.A.R. framework above.
- If the field forces a single number, use the midpoint of your researched range. Avoid round, low-effort numbers like exactly Β£30,000 or exactly Β£35,000 unless that genuinely is your researched figure β recruiters notice when a number looks guessed rather than researched.
- If there's a free-text box, add a qualifying sentence. Something like: "Negotiable based on full package and role scope" gives you flexibility even within a form-based answer.
- If the field is truly mandatory and offers no flexibility (a hard numeric-only field), enter a figure at the higher end of your realistic range. It's far easier to be talked down slightly from a well-researched, slightly ambitious figure than to be talked up from a conservative one β most application systems use this field as a filter, not a binding commitment.
Almost all employers treat the number entered on an application form as an initial data point, not a binding offer ceiling or floor. It gets revisited properly once you reach the offer stage, after they've assessed your full performance through the process. Don't over-agonise over the exact figure at this stage β get it into a sensible range and move on to preparing for the actual assessment stages, which matter far more to the outcome.
Employer-by-Employer Negotiability
How much room you actually have to negotiate varies enormously by employer type. Understanding this before you answer helps you calibrate how much weight to put on getting the exact figure right.
| Employer Type | Typical Negotiability | What This Means for Your Answer |
|---|---|---|
| Investment banks (Goldman Sachs, JP Morgan, Morgan Stanley) | Low β base salaries are typically set by structured pay bands per analyst cohort | Focus your answer on demonstrating market awareness rather than trying to negotiate upward; bonus structure is where real variation exists, and that's determined later by performance, not the interview |
| Big Four (PwC, Deloitte, EY, KPMG) | Low β graduate scheme salaries are generally published and applied consistently across a cohort | Answer close to their published band figure if known; the question is largely a screening check at this stage |
| Large tech employers (Amazon, Microsoft) | Moderate β base pay bands exist, but signing bonuses and stock components can have more flexibility, especially with a competing offer | A well-researched range referencing total compensation (not just base) is well received; mentioning a competing offer, if genuine, can create real movement |
| Mid-size and smaller employers | Higher β no rigid cohort-wide banding structure, decisions often made role-by-role | More room to anchor toward the top of your researched range and to negotiate meaningfully at offer stage |
| Public sector / civil service schemes | Very low β pay is typically set by fixed civil service grading structures | State the published band figure directly; there is generally no negotiation to be had |
None of this is a reason to skip your own research or under-prepare for the question β even where negotiation room is minimal, giving a well-informed answer signals commercial awareness, which is itself a competency many of these employers are quietly assessing throughout the process.
7 Mistakes That Cost You Money
- Mistake 1: Naming a number with no research behind it. Guessing signals a lack of commercial awareness and often lands well outside the realistic range in either direction.
- Mistake 2: Saying "I don't have a number in mind." This hands the recruiter total control of the negotiation and can read as unprepared, even if your intention was to seem flexible.
- Mistake 3: Anchoring on a single figure instead of a range. A single number creates a binary outcome; a range keeps the door open in both directions.
- Mistake 4: Making the range too wide. A range like "Β£28,000 to Β£45,000" signals you have no real sense of the market and will likely be met with the bottom figure.
- Mistake 5: Ignoring total compensation. Quoting a base salary figure without accounting for bonus, pension and benefits can make you look like you're asking for more than the role actually pays β or accidentally underselling a package that's already generous.
- Mistake 6: Trying to negotiate hard before you have an offer. Negotiation leverage is highest after an offer has been made, when the employer has already decided they want you. Pushing hard on salary during initial screening, before any offer exists, can remove you from consideration entirely.
- Mistake 7: Being inconsistent across different stages of the process. If you quote one range on the application form and a meaningfully different one at final interview, it damages your credibility. Keep your range consistent, updating it only if you've genuinely learned new information about the role's scope.
Frequently Asked Questions
Nail the Interview Stage Before You Get to Salary
The salary conversation only matters once you've made it through the assessment stages. Practise the aptitude tests employers actually use, then master the rest of the negotiation with our full salary guide.