How to Answer Salary Expectation Questions on Applications and in Interviews

Salary expectation questions feel simple, but they do a lot of work. Employers use them to screen out mismatched candidates, recruiters use them to test whether the process is worth starting, and candidates often answer too quickly because they want to seem easy to work with. The goal is not to sound agreeable. The goal is to stay credible, protect your options, and avoid boxing yourself into a number too early.

How to answer salary expectation questions: the 3-part decision tree

Start by asking what format you are dealing with. The right answer depends on whether the question is written, semi-written, or live.

  1. Forced number on an application form. Give the most defensible number you can justify from market data and the role's scope.
  2. Free-text box on an application form. Give a tight range and say it depends on the full package, remit, and location.
  3. Live recruiter or interview question. Use the conversation to test budget, then give your range in a way that keeps room to move.

Most mistakes happen when people use the same answer for all three. A single number that works in a mandatory form field can sound rigid in a live conversation. A vague "negotiable" answer that sounds harmless on the phone can get you filtered out on a form.

UK salary research: the range you can actually defend

Before you answer anything, build a three-number model: floor, target, and stretch.

  • Floor is the minimum total package that makes the move worth it.
  • Target is the realistic number you expect for this role in this market.
  • Stretch is the upper end you could defend if the scope is bigger than the advert suggests.

Use current salary data from three places, not one: public job adverts, recruiters who work your niche, and recent hires in comparable companies. A London-based product marketing manager will not use the same reference points as a hybrid operations lead in Leeds. Sector and location still matter, even when the role is remote.

Say your research shows most similar roles land between £52k and £58k, with the better-funded employers paying up to £62k. Your answer should come from that band, not from hope and not from the number you saw in one Glassdoor screenshot.

This is also where good job-search strategy helps. If you are talking to companies before they advertise, you can often test salary expectations earlier and with better context. That is one reason how to find unadvertised jobs in the UK can shorten the awkward part of the process.

If the application form forces a number

When the form forces a number, you do not have much room for nuance. Pick the number that best protects your floor without pushing you out of range.

The practical rule: if you know the market well, use either your target number or the lower end of your acceptable range. That keeps you credible while leaving space to negotiate package, bonus, or scope later.

For example, if your realistic range is £55k to £60k, writing £57k is usually stronger than writing £60k. It signals that you know the market and are not trying to win a bidding contest before anyone has spoken to you.

What not to do:

  • do not enter your absolute minimum if you would feel underpaid the second you accepted
  • do not inflate the number in the hope that they will negotiate down
  • do not type zero, one, or a joke figure just to get through the form

If the next stage includes written screening answers, keep the same level of specificity there too. how to answer common job application questions is the right model for the rest of the form once the salary field is out of the way.

If the application form gives you a free-text box

Free-text is better because you can show flexibility without sounding vague. The safest structure is: range + scope qualifier + package qualifier.

Based on the role as described, I would expect a package in the £55k to £60k range. I would be happy to discuss that in more detail once I understand the full remit, progression path, and broader package.

That works because it sounds informed, not evasive. It also signals that you know salary is not the only lever that matters.

Keep the range tight. A range of £45k to £65k says you have not done the homework. A range of £55k to £60k sounds like someone who understands the market and their own level.

If the role is genuinely hard to price because the title is vague, say that explicitly. A Head of Operations title in one company might manage six people and one office; in another it might own a national function. The answer should reflect that uncertainty rather than pretending the market is clearer than it is.

What to say when a recruiter asks on the phone

Phone screens are where many candidates give away leverage because silence feels awkward. You do not need to fill the silence instantly.

Start by turning the question into a two-way check.

Happy to share a range. Before I do, has the team set a budget for the role yet?

If they answer clearly, great. You now know whether the process is viable. If they dodge, give your range and tie it to scope.

For roles at this level, I am usually looking at something around £58k to £62k, depending on the package and how broad the remit is.

That answer is calm, specific, and easy to compare against their internal range. It also avoids one common mistake: answering the question as though base salary is the only variable. Pension, bonus, commission structure, remote allowance, and progression can all shift the right number.

How to answer salary expectations in interviews when the budget is vague or low

Interviews are different because by then you know more about the role. That means your range can get sharper, not broader.

If the budget is vague, ask for clarity before you negotiate against yourself.

I am keen on the role, but the right figure depends on how you are defining the level. From what we have discussed so far, I would expect it to sit around £60k. Is that close to the range you have in mind?

If the number comes back lower than expected, do not rush to close the gap yourself. Ask what is fixed and what is flexible. Sometimes the base is capped but the package, review cycle, or title level is not. Sometimes the budget is simply wrong for the market and the conversation should end there.

You are not being difficult by testing that early. You are preventing both sides from wasting three more interviews on a mismatch.

When to hold firm and when to walk away

The best answer to a salary expectation question is sometimes a polite no.

Hold firm when the employer clearly wants a higher level of experience than the budget supports. Walk away when the package is far below your floor and there is no credible route to close the gap. Keep talking when the role is unusually strong on progression, flexibility, equity, or scope and the employer is transparent about how compensation grows.

The point is not to maximise every offer. It is to make deliberate trade-offs rather than accidental ones. A lower-paid role can still be the right move. A flattering title attached to a weak package usually is not.

If the slow part of your application process is writing salary answers that sound specific to the role instead of generic, draft a tailored answer in seconds with AI Job Answers. Paste the question, pair it with your CV and the job description, and you get a cleaner first draft that you can then tune to your actual range and priorities.

Common questions

Should I give a salary range or a single number?
A range is usually safer because it shows you know the market without locking yourself to one figure too early. Keep the range tight, usually within 5 to 10 percent, and make sure the bottom number is still acceptable to you. A single number only makes sense when the form forces it or you already know the budget.
What if an employer asks for my current salary?
You do not have to answer with a precise figure if you would rather anchor on the role instead. In the UK, a practical response is to say you are focused on the level, scope, and package for this position, then give the range you are targeting. That keeps the conversation on market value rather than salary history.
Can I just write negotiable on a job application?
Only if the form allows free text and the role's scope is still unclear. On a forced-number field, 'negotiable' either will not submit or reads evasively. Give a defensible number or range instead, then add flexibility later in the process.
What should I do if the advertised salary is below what I earn now?
Ask whether there is flexibility before you invest heavily in the process. If the gap is small, the role, bonus, pension, remote setup, or progression path might still make it worth a conversation. If the gap is large and fixed, it is better to find out early and move on.