What to Say When They Ask "What Are Your Salary Expectations?"

Few interview questions create as much anxiety as this one. It arrives without warning sometimes in the first five minutes of a conversation, sometimes buried in an online application before you've even spoken to a human and the pressure to answer correctly feels enormous.

Say a number too low and you've undersold yourself, possibly by thousands of dollars per year. Say a number too high and you risk being screened out before the interview even gets interesting. Deflect entirely and you can come across as evasive or unprepared.

The good news is that this question has a learnable answer. It's not about luck or confidence it's about preparation, strategy, and understanding what's actually happening on the other side of the table when this question gets asked.

This guide gives you the exact framework to answer salary expectation questions at every stage of the hiring process confidently, professionally, and in a way that protects your interests without costing you the opportunity.

Understanding the motivation behind the question changes how you approach answering it.

Employers ask about salary expectations for several reasons, and they're not all adversarial. The most common reason is genuinely practical: hiring managers want to confirm early that there's no fundamental mismatch between what the role pays and what you need to accept it. Nobody wants to invest three rounds of interviews in a candidate who ultimately can't be afforded.

But the question also serves a secondary purpose: it's an opportunity to get you to name a number first ideally a number lower than what they were prepared to pay which saves the company money. This is why the conventional wisdom "never name a number first" exists, and why it's worth taking seriously.

When a recruiter or hiring manager asks what your salary expectations are, they are simultaneously trying to qualify you as affordable and establish an anchor for the eventual negotiation. Knowing this helps you respond in a way that manages both dynamics without playing directly into either of them.

The biggest mistake people make with salary questions isn't what they say in the room it's showing up without research. If you don't know what the role typically pays before the conversation starts, you're negotiating blind.

Salary research takes less time than most people expect and dramatically improves your positioning.

Start with aggregated salary data from platforms like Glassdoor, LinkedIn Salary, Levels.fyi (particularly useful for tech roles), Payscale, and Bureau of Labor Statistics for U.S.-based roles. Search specifically for the job title, the company if possible, and the geographic location salaries for the same role can vary by 30–50% between cities and regions.

Look at multiple data points rather than relying on a single source. Different platforms pull from different data sets, and cross-referencing gives you a more accurate picture of the realistic range.

Also factor in the total compensation picture. Base salary is one component. Benefits, health insurance, retirement matching, equity, bonuses, remote work flexibility, and paid time off all have real financial value. A role offering $5,000 less in base salary but significantly better benefits and a performance bonus may be more valuable overall than it appears at first glance.

Once you have your research, identify three numbers: the bottom of the market range for the role (your floor the minimum you'd accept), the midpoint (a fair market rate), and the top of the range (what the role pays at the high end, which is what you're aiming for). Your target number should sit comfortably in the upper portion of the realistic market range not at the absolute ceiling, but closer to it than the floor.

When the salary question arrives early in the process during a screening call, in an initial application, or in the first interview the most effective strategy is a polite, professional deflection that buys you time to learn more about the role before committing to a number.

This isn't evasion. It's standard negotiation practice, and experienced interviewers will recognize and respect it.

A response that works well in early conversations sounds something like this:

"I'm still learning about the full scope of the role and what it involves, so I'd prefer to wait until I have a fuller picture before discussing specific numbers. That said, I'm confident we can find something that works for both sides could you share what budget you have in mind for this position?"

This response accomplishes three things simultaneously. It declines to anchor yourself with a number before you have full information. It signals confidence and professionalism rather than avoidance. And it flips the question back to them which is the genuinely optimal outcome, because if they name a number first, you're in a far stronger negotiating position.

Many employers, particularly at the screening stage, will simply tell you the budgeted range when asked directly. When they do, that information is enormously valuable you now know their floor and ceiling before you've committed to anything.

There are situations where deflection won't work online applications that require a number in a mandatory field, employers who push back on your redirection and ask again directly, or later-stage conversations where both sides understand a number is needed to move forward.

In these situations, give a range rather than a single number and construct that range strategically.

The range you offer should be anchored at the high end, not the middle. If your research suggests the role pays $70,000–$90,000 and your target is $85,000, your stated range should be something like $80,000–$95,000 not $70,000–$85,000. The reason is simple: most employers will aim for the lower end of whatever range you give. By anchoring high, the lower end of your range is still a good outcome.

Keep the range relatively tight $10,000–$15,000 spread for most roles, not $30,000. A wide range signals uncertainty and gives the employer too much room to maneuver toward the bottom.

A well-constructed response for this stage sounds something like:

"Based on my research into market rates for this type of role and my experience level, I'm looking for something in the range of $80,000 to $95,000. That said, I'm open to discussing the full compensation package base, benefits, and any performance incentives to find something that works for both of us."

This response is specific enough to demonstrate preparation, flexible enough to avoid appearing rigid, and broad enough to acknowledge that compensation is more than base salary.

Online applications frequently include a mandatory salary expectations field, which creates a dilemma: leave it blank and your application may be filtered out, fill it in too low and you've anchored yourself unnecessarily early, fill it in too high and you risk being screened before anyone reads the rest of your application.

The most pragmatic approach for mandatory fields is to enter the midpoint of your researched range without a range a single number in the middle of what you'd realistically accept. This gives you room to negotiate up or down once you're in the room and have more information.

Some candidates write "negotiable" or "open" in free-text fields. This works in some application systems and gets filtered out in others. If the field accepts text rather than requiring a number, "Competitive with market rate happy to discuss" is a professional response that avoids premature commitment.

Knowing what to avoid is as important as knowing what to say.

Never say "I'll take whatever you're offering." This signals a lack of self-advocacy and often results in an offer at the lowest end of the budget. Employers respect candidates who know their value it's a professional quality, not an inconvenience.

Never anchor with your current or previous salary as the starting point for your expectation. Your previous compensation reflects what a previous employer was willing to pay, not what this role is worth or what you're worth. In many jurisdictions, employers are no longer legally permitted to ask about your salary history for exactly this reason. If asked, you can decline to share: "I prefer to focus on what's appropriate for this role based on current market data rather than previous compensation."

Never apologize for having expectations. Phrases like "I know this might be too high, but..." or "I hope this isn't too much to ask..." undermine your position before the negotiation starts. State your range with the same calm confidence you'd use to describe your work experience.

Never accept the first offer without at least exploring whether there's room to move. Most initial offers have some negotiation margin built in. A simple, professional response like "Thank you I'm genuinely excited about this opportunity. Is there any flexibility on the base salary?" costs nothing to try and frequently yields an additional $3,000–$10,000.

The salary question doesn't end when an offer arrives. In many ways, that's when the real negotiation begins and it's also when candidates with good preparation have the most leverage.

Once an offer is on the table, you've been chosen. The company has invested significant time in selecting you, and the cost of going back to the candidate pool is real. That dynamic shifts power toward you, and most candidates underestimate how much room there typically is to negotiate at this stage.

Take time to review the offer it's entirely professional to ask for 24–48 hours to consider it, and any employer who pressures you to accept on the spot is showing you something worth noticing about their culture.

When you respond, lead with genuine enthusiasm for the role before addressing compensation. Then make a specific, grounded counter-proposal rather than a vague request for more:

"I'm very excited about this opportunity and would love to join the team. Based on my research and the experience I bring, I was hoping we could get to $88,000. Is that something you're able to work with?"

Specific numbers anchored to research are more effective than general requests. They signal preparation, not greed and they give the employer a concrete number to take back to their internal process.

The salary expectations question is not a trap. It's an invitation to demonstrate that you know your value, you've done your research, and you're capable of having a professional, grounded conversation about compensation which, incidentally, is a quality employers value in candidates they're considering paying well.

Preparation is everything. Know your number, know the market, know the range, and practice your response until it feels natural rather than rehearsed.

You've worked for every skill and every year of experience on your resume. The salary conversation is simply the moment when you ask to be paid accordingly and you are absolutely allowed to do that.