What are your salary expectations?
The complete answer guide: what this question really tests, two example strong answers in different angles, the common weak answer rewritten, and the trap most candidates fall into. This is a why this company / role archetype question — see the broader pattern guide for the structural shape.
What this question is really testing
The interviewer isn't actually trying to negotiate with you right now. They're testing whether you've done your homework, whether you understand your market value, and most importantly, whether this conversation will be a waste of everyone's time. The binary read they're making is: "Will this person's expectations align closely enough with our budget that we should continue investing hours in this process?" A hiring manager who has $95K budgeted doesn't want to spend three more interviews with someone expecting $140K, only to have the process collapse at the offer stage.
Beyond budget alignment, they're reading your self-awareness and professionalism. Do you know what people at your level actually make, or are you wildly off-base? Can you handle a potentially uncomfortable question with grace, or do you get defensive and evasive? The worst signal you can send is that you haven't thought about this at all, because it suggests you're not serious about the role or don't understand how hiring works. The second-worst signal is rigidity—naming a single number with no context suggests you'll be difficult to work with on this and other negotiations.
Two strong answers, two angles
Angle A: Range with research anchor
"Based on my research looking at comparable roles in this market—senior product managers with 6-8 years of experience at Series B SaaS companies in Boston—I'm seeing a range of $145K to $170K base. Given my background leading a team of five and my track record with enterprise launches, I'd be looking for something in the $155K to $165K range, but I'm flexible depending on the total compensation package, equity structure, and growth opportunities here. What range did you have in mind for this role?"
Angle B: Total comp focus with context
"I'm currently at $128K base with about $35K in bonus and equity that vests this year, so my total comp is around $163K. I'm not necessarily looking to maximize salary in my next move—I'm more focused on the right opportunity and team—but I would want to be in the same ballpark or slightly higher to make a move make sense. I know compensation can vary a lot based on company stage and structure, so I'm curious what you've budgeted for this position and how you're thinking about the equity component?"
The common weak answer
"I'm flexible on salary and open to discussing whatever you think is fair. I'm really just excited about the opportunity and I'm sure we can work something out."
This answer sounds collaborative and enthusiastic, but it actually signals that you either don't know your worth or you're afraid to advocate for yourself—neither of which inspires confidence. The interviewer now has no idea if you're expecting $80K or $180K, which means they still need to extract a number from you or risk wasting everyone's time. Worse, by deferring entirely to their judgment, you've positioned yourself as the less powerful party before negotiations have even begun, which often leads to lower offers because the company now knows you won't push back.
Reframe: "I'm flexible within a range—based on market research, I'm targeting $145K to $165K base, but I'm definitely open to discussing the full package once we're both confident about the fit."
The one trap most candidates fall into
The trap is answering first without gathering any information about their budget, structure, or constraints. You think you're being direct and transparent by immediately naming your range, but you're actually negotiating blind. If their budget was $180K and you say $145K-$165K, you've just anchored them lower and cost yourself $15K-$35K. If their budget was $120K and you say $145K-$165K, you've potentially ended the conversation before learning about other levers like equity, bonus structure, or signing bonuses that could bridge the gap.
The sophisticated move is to answer and immediately redirect: give them enough information to know you're in the right ballpark, but then turn it back to them to understand the full picture. Notice how both strong examples above end with a question. This isn't evasive—you've given them real numbers—but it transforms a one-way interrogation into a two-way conversation. The best salary discussions happen when both parties share information iteratively, not when one person names a number and waits to be judged. If they pressure you for a single number before sharing anything about their range, that's actually useful information about how they negotiate and whether you want to work there.
Common questions
How long should my answer to "What are your salary expectations?" be?
Aim for 60-120 seconds spoken (250-350 words). Long enough to land the situation, action, and result; short enough that the interviewer has room to follow up. Anything past two minutes risks losing them.
Should I memorize my answer word-for-word?
No — that reads as canned and falls apart the moment the interviewer asks a follow-up. Memorize the structure (the bones of the story) and the specific numbers/names that anchor it. Let the words come naturally each time.
What if I have a really good story but it was years ago?
Recent is better, but a strong story from 3 years ago beats a vague story from last quarter. If the example is older than 5 years, frame it as the moment that crystallized the lesson, then briefly bridge to how you've applied it since.
Can I use the same story for multiple questions?
Often yes — strong stories tend to demonstrate multiple competencies. The trick is reframing the angle each time. Same situation, different opening sentence: lead with the conflict for conflict questions, lead with the leadership move for leadership questions.
How do I know if my answer is actually good?
Practice it out loud and have it scored. The fastest way is a mock interview where the AI flags exactly what's vague, where you used 'we' when the question asked about 'I,' and rewrites the weakest sentence. Reading example answers helps; getting yours scored is what moves performance.
Reading isn't practicing.
Try answering this question right now before checkout, with real Claude-scored feedback in 5 seconds.
Practice this question free →