How to Answer Salary Expectations in an Interview (2026)

The interviewer leans forward and asks, "So, what are your salary expectations?" You have about five seconds. Say a number too low and you've capped your offer before it's even written. Stammer or apologize, and you signal you don't believe in your own worth. Learning how to answer salary expectations in an interview is less about knowing your market rate than about what comes out of your mouth—calmly, on the spot, when there's nowhere to hide.

This is the live, spoken moment no amount of spreadsheet research fully prepares you for. You can know your number cold and still tank it with a shaky voice. This guide gives you the exact phrasing to deflect early-stage asks, the script to commit to a range later, and the recovery lines for when an interviewer pushes back.

The Fast Answer: How to Answer Salary Expectations in an Interview

The short version: deflect early, anchor late, and always state a range—never a single number—with a steady, unapologetic tone. In early rounds, redirect the question back to the role and the employer's budget. Once you're a finalist or the recruiter insists, give a researched salary range with your target near the bottom of it, then stop talking.

The reason delivery matters so much: this is one of the few interview questions where being right isn't enough. You can name a perfectly reasonable figure and still lose money if your voice wavers, you trail off, or you tack on "...but that's flexible, obviously" before they've said a word. The data backs up how rarely people get this right. Only 32% of men and 28% of women asked for higher starting pay in their most recent job, meaning roughly 68–72% of workers accepted the initial offer without negotiating at all¹. Among those who didn't negotiate, 38% said they felt uncomfortable asking². Discomfort is a delivery problem, and delivery is trainable.

Why the Number You Say First Becomes Your Ceiling

Whoever says a number first sets the anchor for the entire conversation. If you under-anchor—naming a figure below what the company budgeted—you'll likely get it, and you'll never know how much you left behind. This is why "how to deflect a salary question in an interview" is the most-searched version of this problem: candidates instinctively sense that answering too early is a trap.

The stakes are real. Among workers who negotiated their starting pay, 78% received a better offer, and 51% got exactly what they asked for—only 22% saw no improvement³. The people who said a low number first weren't in that 78%, because they'd already capped the conversation. Employers expect the back-and-forth: a Salary.com survey found 84% of employers expect applicants to negotiate during interviews, and 87% said they had never rescinded an offer solely because someone negotiated⁴. The fear that asking will cost you the job is largely unfounded.

There's also a timing reality on the employer's side. Nearly half (48%) of hiring managers rank meeting candidate salary expectations among their greatest hiring challenges⁵. They are actively trying to read your number—which is exactly why you want them to show theirs first.

When to Deflect vs. When to Commit

The single biggest mistake is giving the same answer in round one that you should give in round four. Your response depends entirely on the stage of the process and who's asking.

Early-stage asks from recruiters are usually about calibration—they want to filter out anyone wildly outside band before investing more time. That's your cue to deflect and turn the question around. By the final round, the company wants you, your leverage is highest, and refusing to give any number starts to read as evasive. That's when you commit to a range.

Scripts to Deflect the Early-Stage Ask

In early rounds, your goal is to redirect without sounding cagey. Deliver these warmly, with a slight upward, curious tone—like you're collaborating, not dodging. The worst delivery is a flat, defensive "I'd rather not say." Here are scripts that work out loud.

The turn-it-around (best default):

"That's a great question. I want to make sure my expectations line up with the role—do you have a budgeted range for this position? I'm happy to tell you if that works for me."

The role-first deflection:

"I'd love to learn more about the scope and the team before locking in a number. So far everything I've heard sounds like a strong fit—what range did you have in mind for the right person?"

The transparency-driven version (great if the posting had a range):

"I saw the posted range of $X to $Y, and that works well for me. I'd want to land toward the upper end based on my experience, but I'm confident we're aligned."

The form-field version (when an application demands a number):

Never leave it blank and avoid a single figure. Enter a range or the word "Negotiable." Including salary information helps both sides—63% of hiring managers say it attracts more qualified candidates⁶—so a reasonable range signals you're an informed, serious applicant.

The Anchor Script: How to State a Range and Stop Talking

When it's time to commit—the recruiter insists, or you're in the final round—you state a researched range, anchor toward the top, and then go silent. The silence is the hardest part and the most important.

Use this structure:

1. Frame it in research, not need. "Based on my research for this role and market..."
2. State the range, with your real target near the bottom. "...I'm targeting $95,000 to $110,000."
3. Tie it to value. "...which reflects my [specific skill or result]."
4. Stop. Do not fill the pause. Do not say "but I'm flexible."

Put together, out loud:

"Based on my research for this role and the market, I'm targeting $95,000 to $110,000, which reflects the [X years / specific results] I'd bring to the team."

Then close your mouth. The person who speaks next in a negotiation often loses ground, and an awkward three-second pause feels like an eternity to you but is completely normal to them.

A critical mechanic: put your actual minimum acceptable number at the bottom of your stated range, not in the middle. Interviewers frequently hear a range and zero in on the lowest figure. If $95,000 is your true floor, $95,000–$110,000 protects you; $85,000–$100,000 quietly invites a $90,000 offer. Ground your numbers in real data using a salary research method before you ever walk in—our guide to researching your salary and market value walks through exactly how to build that range. For a fast, role-specific starting point, HiredKit's Salary Insights tool estimates a market range for the exact role and shows where your experience lands within it—with negotiation guidance—so the range you anchor with is grounded in data, not guessed.

Recovering When They Push Back

Expect pushback—it's part of the script on their side, not a rejection. The candidates who hold their number aren't the ones who memorized the best comeback; they're the ones who practiced staying calm when the room got slightly uncomfortable. Here's how to handle the three most common pushes.

"That's a bit above our range."

"I appreciate you telling me. Can you share where the range tops out? I'm genuinely interested in this role, and I'd like to see if we can find a number that works for both of us."

This keeps you in the conversation without immediately caving. You've invited them to reveal their ceiling—which is information you didn't have a moment ago.

"What's the lowest you'd accept?"

Don't answer literally. "I'm confident we can land in the range I mentioned. What's the budget you're working with for this role?" You never name your floor on demand—that just becomes the new ceiling.

"We need a single number, not a range."

Give the top of your range as the single number: "Then let's say $110,000, given the scope we've discussed." You can negotiate down from there if needed; you can never negotiate up.

Know that the pushback can carry an equity dimension worth bracing for. Among those who negotiated, women were more likely than men—38% vs. 31%—to be told they would only receive the initial offer⁷. If you hear a hard "this is final," treat it as one more move in the conversation, not the end of it, and ask what flexibility exists on bonus, equity, or review timing.

Why Practicing Out Loud Changes Everything

Reading these scripts silently and saying them under pressure are two entirely different skills. The failure mode here is almost never not knowing what to say—it's the voice cracking, the apologetic add-on, the nervous laugh after your number. You can't fix a delivery problem by reading more articles. You fix it by rehearsing the spoken moment until it's boring.

This is exactly where HiredKit's AI Interview Simulator is built differently from a static question bank or a list of scripts. It's a live, two-way voice conversation: the AI interviewer actually asks "What are your salary expectations?" out loud, listens to your answer, and—crucially—follows up the way a real recruiter does ("That's above our range, what's the lowest you'd take?"). You practice the deflect, the anchor, and the recovery as a spoken exchange, not a multiple-choice quiz.

The difference that matters most for this question: Rupert, the in-ear coach, listens in real time and can nudge you the instant your voice goes apologetic or you under-anchor—then the graded feedback afterward flags whether you stated a range or a single number, whether you stopped talking after your anchor, and whether your tone held. Because the questions are tailored to the job description you paste in, you can rehearse a salary exchange calibrated to the actual role you're interviewing for.

How HiredKit differs from a script list or question bank

The knowledge in this article gets you to the right words. Practicing them out loud—against an interviewer that pushes back—gets you to the right delivery. That's the gap that costs people money, and it's the one most prep tools ignore.

Putting It Together: A Full Mock Exchange

Here's how a confident candidate moves through the whole sequence, early deflect to final anchor.

Recruiter (round one): "What are your salary expectations?"

You: "Great question—I want to make sure we're aligned. Do you have a budgeted range for the role? Happy to confirm it works for me."

Recruiter: "We're somewhere around $90K to $115K."

You: "That works well. Based on my experience I'd be targeting the upper half of that, but I'm confident we're in the same ballpark."

Hiring manager (final round): "So where do you need to land on comp?"

You: "Based on my research for this role and the scope we've discussed, I'm targeting $108,000 to $115,000, which reflects the [specific result] I'd bring." (Then silence.)

Hiring manager: "That's a little high."

You: "I understand. Where does the budget top out? I'm genuinely excited about this team and want to make it work."

Notice what the candidate never does: name a low number first, apologize, or fill the silence. That's the entire game. After the offer lands, the tactics shift from defending a range to expanding the package—our salary negotiation strategies guide covers the offer-stage moves that come next.

Common Questions About Salary Expectations

Should I ever give a number first? Only when you're a finalist, the employer refuses to share their range after you've asked, or an application form requires one. Even then, give a range, not a single figure, and anchor your true minimum at the bottom.

What if the job posting already lists a range? Reference it directly and place yourself in the upper portion: "The posted range works well for me—I'd be aiming toward the top end given my experience." Pay transparency works in your favor here; use it.

Won't naming a high number get me screened out? Rarely, if it's within market. Employers expect negotiation—84% of them anticipate it during interviews⁴. A researched range tied to your value reads as confident, not greedy. Under-anchoring costs you far more often than a reasonable high anchor does.

How do I answer salary expectations with no negotiating experience? Lean on scripts and rehearsal. Negotiation rates are rising precisely because more people are practicing—47% of Q2 2025 new hires negotiated their offers, up sharply from 35% the prior quarter⁸. The skill is learnable, and most of it is just saying your number without apologizing.

What if I genuinely don't know the market rate? Don't wing it live. Do the research first, then deflect in early rounds to buy time while you confirm your number. Walking in without a range is how people get anchored into a low offer—and it's the easiest mistake to avoid. For broader interview composure beyond this one question, our guide to answering 'tell me about yourself' covers setting a confident tone from the opening minute.

The Bottom Line

Answering "What are your salary expectations?" well comes down to three moves: deflect in early rounds, anchor a researched range late, and stop talking after you say your number. The words are simple. The hard part is the delivery—saying your number as a plain fact, holding the silence, and staying calm when they push back. That's a spoken skill, and spoken skills only improve with spoken practice.

Know your range before you walk in. Then rehearse the exchange out loud until your voice doesn't betray you. The candidates who get paid what they're worth aren't the ones with the best spreadsheet—they're the ones who've already said the number a dozen times before it counted.