How to answer “What are your salary expectations?” — research, scripts, and pressure-tested responses

This question shows up at awkward points in the process: on an application, in a first call, or midway through an interview loop. How you handle it shapes whether you get paid fairly and whether you stay in the running.

Below you'll find a simple process to research a defensible range, answers for different moments in the process (before and after you know the scope), tactics for when an interviewer pushes for a single number, and ready-to-use scripts you can adapt.

Start with research: build a defensible salary range

Before you speak numbers, do three types of research so you can give a range that’s realistic and justified.

First, look up market data. Use multiple sources: salary sites (Glassdoor, Levels.fyi, PayScale, LinkedIn Salary), job postings for similar titles in your region, and compensation reports from industry associations. Note the typical range, median, and confidence bands (low, typical, high).

Second, factor role scope and level. Titles vary wildly. Compare the responsibilities, the seniority, and required skills. A "Product Manager" in one company can be an entry-level role in another. Put jobs into buckets (entry, mid, senior) and match your experience to the right bucket. Adjust the range up or down based on direct reports, ownership, or technical depth required. If the role requires skills you have that are rare, move the range higher; if it’s a stretch, reduce it slightly and be honest about growth needs. Third, include location and total compensation. Adjust for cost of living, local pay norms, or remote policies. Also consider bonuses, equity, benefits, and perks. If equity matters, convert its expected value to a yearly number for apples-to-apples comparisons. After this step you should have a 2–3 point range (for example, $95k–$115k) with a clear reason why you chose the bounds.

• Use 3+ salary sources and record medians
• Compare actual job responsibilities, not just titles
• Adjust for location, level, and variable pay components

Answer before you know the full scope: graceful and strategic

Sometimes you’ll be asked early—on an application or a quick recruiter screen—before you’ve seen a full job description. You don’t have to lock yourself to a single number. Give a researched range and a qualifier that shows flexibility.

Start with a range you computed, then add context and a soft close that invites more discussion: say you’ll confirm after you learn more about the responsibilities, the team, and the total comp package. That stance keeps you negotiating room while appearing reasonable.

Script (early stage): “Based on market data for roles like this in [city/region] and similar levels, I’m targeting roughly $X–$Y base. I’m flexible depending on responsibilities and total compensation—can you share the role’s scope and on-target bonus or equity?”

Answer after you know the scope: firm range and priorities

After you’ve reviewed the job description, talked to the recruiter, or completed interviews, you should give a tighter range and state your priorities. By now you’ve matched your skills to the role and can justify the top or bottom of your range.

Name a 2–3 point range that reflects what you found in your research and explains why the midpoint fits. If you have non-salary priorities (remote days, career growth, sign-on, equity), mention them so negotiations can include trade-offs.

Script (scope known): “Given the role’s ownership of the roadmap, expected cross-functional leadership, and the market for comparable positions in [city], I’m targeting $X–$Y base, with a preference toward the higher end because of the leadership responsibilities. I’d also like to discuss equity and performance bonus structure.”

• Give a tighter range after learning responsibilities
• Explain why the range maps to the role and your level
• Mention trade-offs you care about (equity, title, flexibility)

When they pressure you for a single number: stay strategic

Interviewers often push for a single number to anchor the negotiation. That’s intentional—numbers stick. You don’t have to give one right away. Use techniques to resist anchoring while appearing cooperative.

Option 1: deflect and repeat your range. Reiterate your researched range and ask the interviewer to share their budget. Example: “I prefer a range of $X–$Y. What range has the company budgeted for this role?”

Option 2: give a preferred number near your range’s low-to-mid point. That prevents you from unintentionally anchoring high and making yourself unattractive, but also avoids setting your ceiling too low. If you use this, be ready to justify it and to push back later if the offer is below market value. Option 3: ask for more information. Request data on total comp, bonus targets, and equity. Sometimes that makes them reveal budget before you anchor. If they still insist, choose the tactic that fits your leverage and timeline—give a number if you’re far in the process and you want to keep momentum; hold firm on the range if you need negotiation room.

• Ask for the company’s budget first
• If pushed, offer a single number near your low-to-mid point
• Use clarifying questions to convert to total compensation

Scripts for common scenarios

Here are short, ready-to-use scripts for different moments. Tweak numbers and wording to match your comfort level.

Scenario: Application form asks for salary expectations: “Based on market data for this role in [city], my expectation is $X–$Y base. I’m open to discussing total compensation, including bonus and equity.”

Scenario: Recruiter asks on a call early: “I’m targeting $X–$Y based on similar roles and my experience. I’d like to learn more about the scope and total compensation before finalizing.” Scenario: Interviewer insists on one number: “If I need to give a single number today, I’d say $Z base, which is within the range I shared. I’m also interested in the bonus/equity mix—can we review that?” Scenario: After interviews, negotiating: “Given the role’s responsibilities and the market, my target base is $X–$Y. I’m looking for a strong equity package and a performance bonus around [percentage/target]. Is that in line with what you’re offering?”

Practical tips for negotiating later

Keep documentation: screenshots of job posts, salary site printouts, and notes from conversations. These make your argument factual, not emotional. Be ready to justify the top of your range with specific examples: similar projects, leadership scope, revenue or impact metrics. That offers concrete reasons for the higher figure.

If the initial offer is below your range, open with a positive restatement, then provide a counter with a number and reasons. For example: “I’m excited by the team and this offer. Based on market data and my experience, I was expecting $X–$Y. Could we move the base to $Z and discuss equity or a sign-on to bridge the gap?”

Remember that total comp matters: sometimes a slightly lower base but stronger equity or bonus makes sense. If cash now is critical, prioritize base and sign-on; if long-term upside matters, push on equity and vesting cliffs.

• Document research and comparable roles
• Justify higher numbers with impact examples
• Use counteroffers that combine base, sign-on, and equity

The goal is to answer confidently, not to win every point in the first sentence. Research gives you credible ranges, and clear scripts keep you calm under pressure. If you can pivot between a range and a single number depending on timing and leverage, you’ll avoid common traps and land a fairer offer.

Practice your responses aloud so you sound natural. With preparation you’ll handle early screens, pressured asks, and final negotiations in a way that protects your options and shows you understand real market value.