How to Answer Salary Expectation Questions in an Interview
"What are your salary expectations?" is one of the most anxiety-inducing questions in a job interview, mostly because it feels like a high-stakes guessing game — say too high and risk looking unrealistic, say too low and risk leaving money on the table. This guide covers how to actually approach the question depending on when it comes up in the process, without treating it as a single fixed script.
Why This Question Feels So High-Stakes
Part of what makes this question uncomfortable is the perceived asymmetry: the employer usually has a real budget range in mind, while the candidate often doesn't have equivalent information about what that range actually is. This asymmetry is real, but it's manageable — the goal isn't to guess the employer's exact number, it's to give a well-researched, honest range that keeps the conversation moving productively without underselling yourself before you have full information about the role.
Researching Before You're Ever Asked
Doing this research before an interview, rather than improvising in the moment, removes most of the anxiety around the question. Look at current live postings for similar roles — many remote job listings disclose salary ranges directly, which gives a far more accurate, current picture than generic online salary aggregators that can be outdated or based on unrelated markets. RemoteAI's job board shows posted ranges directly on many listings, which is a useful starting point for calibrating your own expectations for a comparable role.
Before any interview, research current salary ranges for comparable roles using real, current job postings rather than generic aggregators. This gives you a well-informed range to reference confidently if asked, rather than guessing under pressure or relying on outdated data.
How to Answer Early in the Process
If a recruiter asks for your expectations early — often during an initial screening call, before you've learned full details about the role — it's reasonable to give a researched range while keeping some flexibility:
> "Based on my research into similar roles, I'm generally looking in the range of [X to Y], though I'm flexible depending on the full scope of the role and the complete compensation package."
This avoids either anchoring too low or refusing to engage with the question at all, which can come across as evasive this early in a process.
How to Answer After You Understand the Full Role
Later in the process — after a more detailed conversation about responsibilities, team structure, and expectations — you're in a better position to give a more specific, confident number rather than a wide range:
> "Having learned more about the scope of this role, I'd be looking for something in the range of [specific number], based on my experience and the responsibilities we've discussed."
Narrowing your range as the process progresses signals that your expectations are grounded in a genuine understanding of the role, not just a generic number pulled from research alone.
How to Answer When You Genuinely Don't Have a Number Yet
If you're earlier in your career, or moving into an unfamiliar market or role type, and genuinely don't have a confident number yet, it's fine to be honest about that while still engaging with the question rather than deflecting entirely:
> "I don't have a fixed number in mind yet since I'm still learning about the specifics of this role, but based on what I've seen for similar positions, I'd expect something in the range of [X to Y]. I'm open to discussing further once we're further along."
This is more constructive than refusing to give any number, which can read as unprepared rather than appropriately cautious.
What to Do If You're Asked for Your Current Salary
In many places, employers are legally restricted from asking about current or past salary directly, though this varies by location and it's worth knowing the rules relevant to where you and the employer are based. If you are asked and are comfortable answering, you can choose to share it, but you're also within reason to redirect the conversation toward your expectations for this specific role rather than your history:
> "I'd prefer to focus on what I'm looking for in this role specifically, based on the scope and my research into similar positions, which would be in the range of [X to Y]."
This keeps the conversation forward-looking rather than anchored to a potentially unrelated past compensation structure.
Handling the Question in Writing (Application Forms)
Some applications require a salary expectation field before you've had any conversation at all. In this case, giving a reasonably researched range (rather than an artificially narrow single number) keeps you from either underselling yourself or accidentally pricing yourself out before a conversation even happens. If the form allows a text field alongside a number, a brief note like "flexible depending on full role scope and total compensation" adds useful context that a bare number alone doesn't convey.
Checklist for written salary fields:
- Research a realistic range for the specific role and market beforehand
- Provide a range rather than an artificially narrow single figure, if the form allows it
- Add a brief note about flexibility if a free-text field is available
- Avoid leaving it blank if the field is required — an unanswered required field can sometimes be treated as a non-response by an ATS
Common Mistakes When Answering This Question
The most common mistake is giving a number without having done any research at all, which risks either underselling yourself or citing a number so far outside the realistic range that it undermines credibility. The second is refusing to answer at all early in the process, which can come across as evasive rather than appropriately cautious — a researched range is almost always better received than a flat refusal to engage. The third is treating the first number mentioned, by either side, as fully binding — compensation conversations typically remain somewhat flexible until a formal offer, and treating an early exploratory number as a rigid commitment on either side isn't necessary.
A Simple Decision Framework
- Situation: Asked early, before understanding full role; Recommended Approach: Give a researched range, note flexibility based on full scope
- Situation: Asked after a detailed conversation about the role; Recommended Approach: Give a more specific, narrower number grounded in the discussion
- Situation: Genuinely uncertain due to limited experience or unfamiliar market; Recommended Approach: Be honest about the uncertainty, still offer a researched range
- Situation: Asked for current/past salary; Recommended Approach: Redirect toward expectations for this specific role where comfortable doing so
- Situation: Required field on a written application; Recommended Approach: Provide a researched range with a brief flexibility note if possible
How Location-Based Pay Affects This Conversation
For remote roles specifically, it's worth understanding upfront whether a company uses location-based compensation (adjusting salary based on where an employee lives) or a single global band regardless of location, since this changes what a realistic range actually looks like for your specific situation. If this isn't mentioned in the posting, it's a reasonable, direct question to ask early in the process — "Does compensation for this role adjust based on location, or is there a single band regardless of where someone is based?" Knowing this before you state a range helps you calibrate your answer to the actual structure you're negotiating within, rather than researching a generic average that may not reflect how this specific company actually sets pay.
Practicing the Answer Out Loud Before an Interview
Even with solid research, many candidates stumble when actually asked this question live, simply because it feels different saying a specific number out loud under real interview pressure compared to having it written down in preparation notes. It's worth practicing saying your researched range out loud, ideally to another person, before an actual interview — this small rehearsal step reduces the hesitation and awkward pausing that can otherwise undercut an already well-prepared answer.
FAQs
Is it bad to give a wide salary range when asked?
No — a reasonably wide but still researched range (not an implausibly broad one) is a normal and appropriate way to answer, especially earlier in a hiring process before the full role scope is clear.
Should I say "I'm flexible" instead of giving a number?
It's better to pair flexibility with an actual researched range rather than offering flexibility alone, since a completely open-ended non-answer can read as unprepared rather than genuinely accommodating.
What if the employer's budget is lower than my stated range?
This is a normal, expected part of the negotiation process rather than a failure on your part — it's an opportunity to discuss whether there's room to move, or whether other parts of the offer (benefits, flexibility, growth opportunities) could help bridge the gap.
Can I change my salary expectations later in the process?
Yes, reasonably — as you learn more about the role's actual scope and responsibilities, it's normal and expected for your expectations to become more specific or shift somewhat, as long as any change is grounded in genuine new information rather than an arbitrary shift.
Is it okay to ask the employer for their budget range instead of giving my own number first?
Yes, it's a completely reasonable question to ask directly, and many recruiters will share a range if asked — though be prepared to still offer your own researched range if they redirect the question back to you.
There's no single universally "correct" answer to a salary expectations question — the right response depends on where you are in the process, how much you know about the role, and how confident your own research is. Preparing a researched range in advance, and adjusting it honestly as you learn more, replaces the anxiety of guessing with a grounded, confident answer at every stage.
Ready to prepare for your next interview? Browse current openings with posted salary ranges on RemoteAI's job board to calibrate your own research, and keep your resume ready with the resume builder.
Jordan Lee
Technical Recruiter