How to Answer the Salary Expectations Question in 2026 — Deflect, Anchor, or Commit

The salary expectations question is not small talk. It is an early negotiation move. When a recruiter asks, “What are your salary expectations?” they may be trying to confirm budget fit, but they are also collecting an anchor. If you answer too low, the company may build the offer around your number. If you answer too high without context, you may create unnecessary friction. The goal is to keep leverage while staying practical.

In 2026, compensation conversations are more complicated because remote bands, equity volatility, bonus structures, and tighter hiring budgets all matter. A base salary number alone rarely describes the opportunity. The right answer depends on timing, information, leverage, and whether you are willing to walk away.

You have three basic moves: deflect, anchor, or commit. Good candidates know when to use each.

What the company is trying to learn

Recruiters ask salary expectations for several reasons.

| Reason | What it means for you | |---|---| | Budget check | They want to avoid a late mismatch | | Level calibration | Your number signals seniority expectations | | Negotiation anchor | Your answer may cap the initial offer | | Location banding | Remote or geo tiers affect base/equity | | Internal equity | They need to avoid comp compression | | Closing likelihood | They want to know whether you are realistic |

None of these are evil. But the incentive is not perfectly aligned. The company benefits if you name a number inside their preferred range. You benefit from understanding the role, level, total package, and market before committing.

Move 1: Deflect when it is early

Use a deflection when you do not yet know the level, scope, location band, equity, bonus, benefits, or expectations.

Best early answer:

“I am still learning about the scope of the role and the level you have in mind, so I would rather not anchor too early. I am focused on finding the right fit, and I am confident we can find a fair market package if there is alignment. Can you share the budgeted range for the role?”

This is polite and firm. It does three things: avoids anchoring, signals market awareness, and asks them to disclose first.

If they push:

“I understand you need to confirm we are not wildly apart. For roles at this level, I am generally seeing total compensation depend heavily on base, bonus, equity, and scope. If you can share the range or level, I can tell you whether it is broadly aligned.”

Do not get flustered. Recruiters ask this all day. A calm deflection is normal.

Move 2: Anchor when you have market data and leverage

Anchor when you understand the role, know your market value, and are comfortable setting expectations. This is usually later in the process, or early only if you have strong leverage and a clear minimum.

Good anchor structure:

“Based on the scope as I understand it and current market ranges for similar roles, I would be targeting something in the range of $X to $Y base, with total compensation depending on bonus and equity. If the role is scoped at [level/scope], that range makes sense to me.”

For senior roles, anchor total comp, not just base:

“For a VP-level finance role at this stage, I would evaluate the full package: base, bonus, equity percentage, refresh approach, and severance/change-of-control terms. Depending on scope, I would expect cash compensation in the $X to $Y range, with equity calibrated to the company’s stage and ownership expectations.”

You do not need exact numbers if the user did not provide a market. But in your own interview, do the research first. Use salary bands, recruiter conversations, public ranges, Levels-style data for tech roles, and your current/competing offers.

Move 3: Commit when you know your number

Sometimes you should be direct. If you have a hard floor, say it.

Use this when:

• You would not accept below a specific number.
• The role is not worth continuing unless the range is close.
• The recruiter has disclosed a range and asked if it works.
• You have competing offers and need to save time.
• You are late in the process and ambiguity is hurting both sides.

Good committed answer:

“To be transparent, I would need a package with at least $X base and a total compensation opportunity around $Y for this to make sense. I am flexible on structure if the overall package and scope are right, but I do not want to waste your time if the role cannot get near that.”

This can be the right move. Deflecting forever is not sophistication. At some point, clarity is leverage.

Base salary vs total compensation

Never answer a total compensation question with only base unless the role truly has no bonus or equity. The package may include:

• Base salary.
• Annual bonus target and payout history.
• Equity grant, vesting schedule, refresh, and strike price.
• Sign-on bonus.
• Commission or variable compensation.
• Benefits, 401(k), health costs, relocation, remote stipend.
• Severance, acceleration, or change-of-control terms for senior roles.
• Title, scope, reporting line, and promotion path.

A $190K base with no equity may be weaker than a $170K base with a credible $80K annual equity value, depending on risk and liquidity. A startup option grant may look large but be worth less if the strike price is high, dilution is heavy, or the company is years from liquidity. Ask about the whole structure.

How to answer if the application requires a number

Online applications often force a numeric field. Use a strategy that protects you.

Options:

• If allowed, enter “Negotiable” or “Market.”
• If a number is required, enter a number near the higher end of your researched range.
• If the field asks desired base, do not enter total comp by mistake.
• If the field asks minimum, enter your true walk-away number, not your dream number.
• If the role posts a range, choose a number aligned with your experience and level.

Do not put $1 unless you know the system treats it as negotiable. Some applicant tracking systems parse numbers literally. Do not put an unrealistically low number to “get in the door” unless you are willing to fight uphill later.

State pay transparency changes the script

Many U.S. roles now include posted salary ranges because of state or city pay transparency laws. Those ranges can be wide. A posted range of $140K-$230K does not mean everyone can get $230K. It usually reflects level, location, and internal equity.

Good response when a range is posted:

“I saw the posted range of $140K to $230K. Based on my background and the scope we have discussed, I would expect to be toward the upper half of that range, assuming the level is aligned. I would also want to understand bonus and equity before evaluating the full package.”

That is better than saying, “I want the max.” It ties your expectation to scope and level.

Startup equity: ask different questions

For startups, salary expectations are inseparable from equity expectations. Ask:

• What is the company stage and last valuation?
• What percentage of the company does the grant represent on a fully diluted basis?
• What is the strike price?
• What is the vesting schedule and cliff?
• Is early exercise allowed?
• What is the post-termination exercise window?
• Are refresh grants standard?
• How does the company think about dilution after future rounds?
• Is there acceleration on change of control?

A recruiter may give share count first. Share count alone is not enough. “50,000 options” could mean very different things depending on total shares outstanding and strike price. Ask for percentage.

Scripts for common situations

Recruiter screen, early

“I am open to a market package for the right role, but I would like to understand the level and scope before giving a specific number. What range has been budgeted?”

Recruiter insists on a number

“I do not want to anchor inaccurately before I understand the full package. Broadly, for roles at this level I am usually evaluating opportunities in the $X to $Y total compensation range, depending on base, bonus, equity, and scope. Does that overlap with your range?”

You are below their range

If they disclose a range higher than expected, do not undercut yourself.

“That range is aligned with what I would expect for this scope. I would want to understand where I land based on level and experience as we continue.”

They are below your range

“I appreciate the transparency. Based on the scope and my current market, that range is lower than what I would need. If there is flexibility for the right candidate, I am happy to continue. If the range is firm, it may not be the best use of time.”

You have a competing offer

“I am currently considering another offer with total compensation around $X. I am still interested in this role because of [reason], but I would need the package to be competitive with that opportunity.”

Keep it factual. Do not bluff competing offers.

Numbers: how wide should your range be?

A good range is usually 10-20% wide for base salary and wider for total compensation if equity is variable.

Examples:

• Base range: $180K-$210K.
• Total cash range: $220K-$260K.
• Total comp range: $300K-$400K if equity structure varies.

If your range is too wide, it loses meaning. “$150K-$300K” tells the recruiter you are not calibrated. If it is too narrow too early, it may box you in. Use a narrower range when you have more information.

Mistakes that cost candidates money

• Giving current salary when asked for expectations.
• Naming a low number because you feel awkward.
• Forgetting bonus, equity, and sign-on.
• Treating posted ranges as the final offer range.
• Saying “I am flexible” without asking for their range.
• Anchoring before level is confirmed.
• Comparing startup options to public company RSUs as if risk is equal.
• Negotiating base only when equity has more room.
• Ignoring location bands for remote roles.
• Accepting verbal compensation language without written details.

The biggest mistake is trying to seem easy to work with by being vague and cheap. You can be collaborative and still protect your market value.

Final calibration

Salary expectations are a timing problem. Early, deflect and ask for the range. Once you understand the scope and market, anchor with confidence. When you know your walk-away number, commit clearly.

The best answer is calm, specific, and package-aware: “I do not want to anchor before understanding scope, but for this level I would expect a market package in this range, with total compensation depending on base, bonus, equity, and role scope.” That keeps you professional and protects your leverage.

Do not apologize for discussing compensation. You are not being difficult. You are making sure both sides are evaluating the same opportunity.

Related guides

• API Design Mock Interview Questions in 2026 — Practice Prompts, Answer Structure, and Scoring Rubric — Prepare for API design interviews with realistic prompts, REST and event-driven tradeoffs, pagination, idempotency, auth, versioning, rate limits, and a practical scoring rubric.
• AWS Mock Interview Questions in 2026 — Practice Prompts, Answer Structure, and Scoring Rubric — Use these AWS mock interview prompts, answer frameworks, scoring criteria, architecture examples, and drills to prepare for cloud engineering and senior backend interviews.
• Backend System Design Mock Interview Questions in 2026 — Practice Prompts, Answer Structure, and Scoring Rubric — Backend system design practice for 2026 with API, data, consistency, queueing, reliability, and operations prompts plus a senior-level scoring rubric.
• Behavioral Interviewing Mock Interview Questions in 2026 — Practice Prompts, Answer Structure, and Scoring Rubric — Prepare for behavioral interviews with a practical story bank, STAR-plus answer structure, scoring rubric, realistic prompts, and a 7-day mock plan.
• Culture Fit Interview Prep in 2026 — Answer Values Questions Without Sounding Fake — Culture fit interviews are not personality tests. This guide shows how to answer values, teamwork, and motivation questions with specific stories that sound grounded instead of rehearsed.