How to Answer "What Are Your Salary Expectations?"
"What are your salary expectations?" shows up earlier than most people are ready for it — sometimes in the very first recruiter call, before you've even discussed the role in depth. How you answer this salary expectations question shapes the rest of the conversation, which is exactly why our broader guide to negotiating salary treats it as a distinct moment, not just a warm-up to negotiation.
The honest answer is: it depends who's asking, when, and how directly. A recruiter doing a first screen, a hiring manager pressing for a specific figure, and an online application form are three different situations that call for three different responses — even though the words used to ask are often nearly identical.
Below is a scenario-by-scenario breakdown, exact deflection and range scripts, and the myth that trips people up most: the belief that you're required to hand over a specific number the moment someone asks.
Scenario by scenario: how to respond
The same question lands differently depending on the stage and the pressure behind it. Match your response to the actual situation rather than using one script everywhere.
| Scenario | Recommended response | Why |
|---|---|---|
| Early recruiter screen, casual framing | Deflect toward the employer's range first | You have the least leverage and least information this early — get their number before giving yours |
| Recruiter pushes for a number after deflecting once | Give a researched range, anchored slightly high | Continued deflection past one attempt can read as evasive; a range keeps flexibility |
| Hiring manager asks mid-interview, after you know more about the role | Give a range, tied to what you've learned about scope | You now have enough context to be specific and credible |
| Final-stage interview, they want alignment before an offer | Give your real target range, confidently | This is close to negotiation — vagueness here can stall the process |
| Online application form field | Handled separately — see our application-form page | A form has no back-and-forth; different tactics apply |
Notice the pattern: deflect early when you have the least information and leverage, get more specific as the conversation progresses and you learn more about the role.
Template: deflection scripts
Deflection isn't refusing to answer — it's answering in a way that gets you information before you commit to a number.
"I'd love to learn more about the scope of the role first so I can give you a number that actually reflects it — what range has been budgeted for this position?"
"I'm flexible depending on the full package and the scope of the role. Can you share the range you're working with so I can make sure we're aligned?"
Both versions do the same thing: politely turn the question back without seeming evasive. Most recruiters will actually answer, because they usually do have a range in mind and asking you first is often just habit, not a hard requirement.
Template: range scripts (when you do need to answer)
When deflection doesn't work, or you're far enough into the process that a specific answer is expected, give a range — anchored toward the upper portion of your researched target, not the middle.
"Based on my research and experience with [specific skill/scope], I'm targeting somewhere in the [$X–$Y] range, though I'm open to discussing the full picture including benefits and growth path."
"For a role at this level with this scope, I'd expect something in the [$X–$Y] range. I'm flexible within that depending on the details of the offer."
Keep the range reasonably tight — a $15,000 spread reads as more researched than a $40,000 one. A too-wide range can look like you haven't actually thought about the number.
Whichever script you use, say the number plainly and then stop talking. Resist the urge to immediately justify or soften it further — a clean, confident range followed by silence reads as far more considered than the same range trailed by three qualifiers.
Know your number before the question comes up
Jobedly's AI scores every job 0–100 for fit and surfaces roles where your target range actually matches the budget — so this question stops feeling like a guessing game.
Get your free tailored resumeThe myth that you must give a specific number when asked
Some jurisdictions also have pay-transparency requirements that push employers to disclose ranges earlier in the process than they otherwise would, which changes the dynamic in your favor — worth checking whether that applies where the role is based.
Reading which move actually fits the moment
A few signals help decide whether to deflect again or just answer directly.
- Tone of the ask: a casual "just so I know what to expect" from a recruiter has more room for deflection than a hiring manager asking pointedly before extending an offer.
- How much you've learned about the role: the less you know about scope and responsibilities, the more reasonable it is to ask for their range before giving yours.
- Repetition: deflecting once is normal; deflecting three times in the same conversation starts to look evasive rather than strategic.
- Stage in the process: the closer you are to an actual offer, the more expected — and safer — it is to be specific.
When the question shows up in writing instead of out loud
Sometimes this question arrives by email from a recruiter rather than live on a call — a short note asking you to confirm your range before scheduling the next step. Treat it the same as a verbal ask: a brief, specific reply works better than an essay, and the same deflect-then-range logic applies.
"Happy to share — I'd first love to understand the budgeted range for this role so we're aligned. If it's helpful in the meantime, my general target is [$X–$Y] based on my experience and current market research."
That one reply does both things at once: answers the question so the recruiter isn't left hanging, and still asks for their number, which keeps the door open to adjust upward if their range runs higher than yours.
How this connects to the rest of the negotiation
This question is a preview of the negotiation to come, not a separate event from it. The range you state here should come from the same research behind your market salary research, not a number invented on the spot.
If this question comes up on a written application form instead of in conversation, the tactics are different enough to warrant their own page — see what to put for desired salary on a job application.
Context worth keeping in mind: unemployment sat at 4.2% as of the BLS Employment Situation, and the SHRM regularly tracks how candidate leverage and pay-transparency practices shift with labor-market conditions — both are worth a glance if you're unsure how much room you actually have to deflect or push.
Let the AI team do the grinding
Jobedly scores every role 0–100 the moment it posts, rewrites your resume to win in seconds, and drafts a matched cover letter automatically. Your first tailored resume is free.
Get your free tailored resumeFrequently asked questions
How do I answer 'what are your salary expectations?' in a first interview?
Do I have to give a specific salary number when asked?
What if the recruiter insists on a number after I deflect?
Is it bad to ask the employer's range before giving mine?
Should my answer change between a recruiter screen and a final interview?
Glossary
- Deflection
- Responding to a salary question by asking the employer to share their budgeted range first, rather than stating a number immediately.
- Anchoring
- The effect where the first number mentioned in a salary conversation influences the range the rest of the discussion moves within.
- Pay transparency law
- Jurisdiction-specific requirements that can obligate employers to disclose a salary range earlier in the hiring process.
- Target range
- A researched band of acceptable salary outcomes a candidate is prepared to state when asked directly.