How to answer "what are your salary expectations?"
The question everyone dreads, handled gracefully, without naming a number you will regret.
2 min read · Updated Oct 2026
Recruiters ask early because it saves them time. You do not have to make it easy for them to anchor you low.
Do your homework first
Never answer before you have a range. Use the method in researching developer salaries, and check remote pay bands so you know how location moves the number.
Three answers, by situation
- If a range is published: "The posted range works for me, I'd expect to land in the upper half for my experience."
- If pressed early: "I'd rather learn more about the scope first. What range have you budgeted for this role?"
- If you must name one: give your target, not your floor, and frame it: "For a role with this scope I'm targeting [target]."
Redirect to value
If they push, talk about what you bring, the systems you have shipped, the problems you solve, before you talk about cost. Compensation is the last thing you want to be negotiating before they want you.
Keep the door open
Whatever you say, sound easy to work with. "Let's make sure it's a fit on both sides" buys room to move later, and sets up negotiating the offer when it arrives.
Related guides
Find a role that's actually remote
Search fresh, genuinely-remote developer jobs - free.
Browse jobs