Answering Salary Questions in Interviews: Without Underselling Yourself

TL;DR

• 73% of hiring managers expect candidates to negotiate; 55% of candidates don't (CareerBuilder).
• Salary questions test budget fit, self-awareness, and negotiation style.
• Strong answers give a researched range, not a single number.
• Tie expectations to specific skills and demonstrated value.
• Avoid lowballing yourself, vague answers, and oversharing personal expenses.

The "what are your salary expectations?" question often catches candidates off-balance. Say too high and you might price yourself out; say too low and you've left money on the table for the entire tenure of your role. The candidates who handle this question well do specific homework before the interview and structure their answer around researched data plus demonstrated value. This guide walks through what interviewers are actually probing, how to answer confidently, and the mistakes that consistently cost candidates real money.

Why Employers Ask About Salary Expectations

Three things the question is testing.

Budget alignment

Do your expectations fit the salary band for the role? If you want $150K for a role budgeted at $90K, both sides save time by surfacing this early.

Seniority and self-awareness

Your answer signals whether you understand your market value, the role's expectations, and how those connect. A wildly miscalibrated answer signals weak research or weak self-knowledge.

Negotiation style

How you answer tells the interviewer how you'll negotiate the offer and behave in future compensation conversations. Direct + research-backed + flexible signals strong professional patterns.

How to Answer "What Are Your Salary Expectations?"

A three-step structure that consistently works.

Step 1: Research before the interview

Don't go into the interview without a research-backed range. Use:

• Glassdoor salary data
• Payscale
• LinkedIn Salary Insights
• Levels.fyi (for tech roles)
• Public salary range disclosures (mandatory in NYC, CA, CO, WA, IL, others)

Look up your specific role, your city, your industry, your experience level. The range should be evidence-based, not guessed.

Step 2: Give a range, not a single number

Single numbers signal rigidity; ranges signal flexibility while still anchoring expectations. The range floor should be the lowest number you'd accept without negotiation; the ceiling should reflect strong-performer expectations for your level.

"Based on my research and what I've seen in comparable roles in this region, I'm targeting a range of $95K-$115K for a role at this level."

Step 3: Tie expectations to value

Numbers without context look like demands; numbers with reasoning look like negotiation. Connect your range to specific capabilities and outcomes you bring.

"Given my 6 years in product management, certification in agile delivery, and track record shipping features that drove 40%+ user growth, I think $110K-$125K reflects what I'd contribute here."

Dos and Don'ts of Salary Conversations

CareerBuilder research shows 73% of hiring managers expect candidates to negotiate — but 55% of candidates don't ask. The gap costs candidates real money.

Do

• Come prepared with researched data
• Frame around value, not need ("Given my experience…" vs "I need…")
• Provide a range, not a point
• Reference the broader package (base + bonus + equity + benefits)
• Stay conversational — this is a discussion, not a contract negotiation

Don't

• Lowball yourself to seem agreeable — you're setting the floor for years
• Answer too quickly under pressure — "I'd love to learn more about the role before discussing numbers" is a legitimate response
• Give vague answers like "whatever's fair"
• Overshare personal finances — keep it professional and rooted in market data
• Skip the research — guessing typically produces underselling

How to Back Up Your Range with Data

Four data-backed phrases that consistently work in salary conversations.

Market benchmark anchor

"Based on my research, similar roles in this region typically pay between $X and $Y."

Value-based positioning

"Given my [specific experience], I'm targeting the upper end of that range — $Y-$Z."

Company-context flexibility

"I understand companies at different stages have different compensation structures, so while my target is $X-$Y, I'm open to discussing the full package."

Collaborative close

"I'm targeting a range based on market data and my background, but happy to talk through what fits your budget and the broader benefits."

These phrases combine confidence with flexibility — the combination interviewers typically read positively.

What to Do When Asked Before You Have Role Details

A common scenario: salary question comes early, before you fully understand the role.

Buy time politely

"I'd love to learn more about the role's responsibilities and expectations before discussing specific numbers. Once I have that context, I'll be able to give you a more meaningful range."

Ask their range

"Do you have a budgeted range for this role you can share?"

Many companies will share. Some won't — but asking is reasonable and often successful.

Provide a wide range if pushed

If they insist on a number before you have role details, give a wider range than you'd otherwise share, and note you'd refine after learning more.

What If Asked About Current Salary?

A trickier question. In many US jurisdictions (CA, NY, MA, several others), employers are legally prohibited from asking about prior salary. Where the question is legal, you have options.

Decline politely

"I'd prefer to focus on the value I'd bring to this role rather than what I've earned before. Based on market research, my expectation for this role is $X-$Y."

Pivot to expectations

"Rather than my current salary, I think it's more useful to look at market rates for this role. My expectation is $X-$Y based on research and my background."

You're not obligated to disclose prior salary even where it's legal to ask. Many candidates politely decline.

The Bottom Line

Salary questions are high-stakes moments that disproportionately reward preparation. The candidates who research thoroughly, anchor on data, give ranges instead of points, tie expectations to value, and stay flexible without being vague consistently end up with stronger offers. The candidates who lowball themselves, refuse to discuss, or pull numbers from thin air either miss opportunities or accept less than they could have. The 30-60 minutes of research before any serious interview can produce salary differences that compound over years. It's one of the highest-ROI activities in job-search prep.

FAQs

Should I give a single number or a range?

A range, always. Single numbers signal rigidity and rarely produce stronger outcomes than well-anchored ranges.

What if I don't know what the role pays?

Research before the interview — Glassdoor, Payscale, LinkedIn Salary, Levels.fyi (tech), public salary range disclosures in pay-transparency states. The data exists; finding it just takes time.

Can I refuse to answer the salary question?

You can decline to discuss prior salary (often required by law to be optional). For expectations, declining entirely usually hurts — better to give a researched range and stay flexible.

What if their budget is much lower than my expectation?

Either decline the role, or negotiate the package — sometimes you can recover the gap through equity, signing bonus, time off, or other terms. Just be clear that the budget gap is real.

What's the highest-leverage salary-conversation skill to develop?

Research discipline. The candidates who consistently do their homework before interviews end up earning meaningfully more across their careers than candidates who guess. The compounding effect across years is significant.