2026-09-08
How to Answer "What Are Your Salary Expectations?"

This question almost always comes up before you've even had a real conversation about the role — sometimes on a screening call in the first ten minutes. Answered poorly, it can anchor you low for the rest of the process or knock you out for seeming too expensive before anyone has assessed your fit. Answered well, it's a non-event.
1. Why this gets asked so early
Recruiters ask early to filter efficiently — for both sides. They don't want to run you through four rounds of interviews only to discover the budget is 30% below what you need, and in theory, neither do you. The problem is that it's being asked before you know the full scope of the role, the level you'd be hired at, or what the total compensation package looks like — which puts you at an information disadvantage if you answer with a single hard number too early.
2. The risk of anchoring too low or too high
Say a number that's too low, and it often becomes your ceiling for the rest of the process — companies rarely offer meaningfully more than what you stated you'd accept, even if the role is worth more. Say a number that's too high without justification, and you risk being screened out before anyone evaluates your actual fit for the role. Both mistakes come from the same root cause: answering before you've done any research.
3. Research a realistic range before the call
Before any interview where this might come up, spend twenty minutes building a rough range for the role, level, and location (or remote market) you're targeting. Useful inputs include public salary-sharing platforms, job postings that list ranges (increasingly common and a good real-world anchor), and conversations with people currently working similar roles. Aim for a range with a floor you'd actually accept and a ceiling that's ambitious but not absurd — this is your reference point for the rest of the conversation, even if you never say the exact numbers out loud.
4. Redirect to a range instead of a single number
Once you have your research, the safest response is a range slightly above your true floor, paired with a note that you're flexible depending on the full picture: "Based on my research for this type of role, I'm looking at something in the [X–Y] range, though I'm open to discussing based on the full scope and compensation package." This does three things at once — it shows you've done your homework, it gives the recruiter a workable number to check against budget, and it leaves room to negotiate later without boxing you in.
If you genuinely don't have enough information yet, it is also fair to ask a clarifying question first: "Can you share the budgeted range for this role so I can make sure we're aligned?" Many recruiters will simply answer, and it removes the guesswork entirely.
5. Handling "what's your current salary"
This question is different from salary expectations, and in a growing number of places it's restricted or banned outright — but it still comes up. Your current pay is not necessarily a fair benchmark for a new role, especially if you're changing companies, industries, or levels. You're not obligated to disclose it, and a polite redirect works well: "I'd rather focus on the value I'd bring to this role and what's appropriate for it, based on my research the range I mentioned reflects that." Said calmly and without apology, this rarely causes friction.
6. When it's actually fine to just answer directly
Not every situation calls for deflection. If you're far enough along that you trust the relationship, if the company has already been transparent about its range, or if giving a direct number clearly works in your favor (for example, your realistic target is comfortably within what you know the role pays), a straightforward answer can move things along faster and build goodwill. The redirect strategy is a tool for uncertainty, not a rule to follow rigidly in every conversation.
It also helps to walk into these conversations already knowing how you stack up. Uploading your resume to ProfileMatch against a specific job posting shows you where your experience aligns with what's being asked for, which makes it much easier to justify a number with confidence instead of guessing.
The honest takeaway
The salary expectations question isn't a trap if you prepare for it. Research a realistic range beforehand, answer with a range rather than a fixed point, redirect current-salary questions calmly when it makes sense, and don't be afraid to answer directly when directness clearly works in your favor. The goal isn't to outmaneuver the recruiter — it's to make sure the conversation starts from accurate information instead of a guess made under pressure.


