Salary Expectations Interview Answer: Scripts
Learn the best salary expectations interview answer with scripts, ranges, and counteroffers so you can negotiate pay with confidence.
Most candidates lose money on salary talks before an offer even exists. The fix is not to dodge the question or blurt out a number too early. It is to answer with a researched range, protect your leverage, and know exactly what to say next. If you're preparing for a new role, update your materials first in our [free resume builder](/free-resume-builder) so your experience and target level support the compensation you're asking for. ## Step 1: Know what number actually matters When an interviewer asks for your salary expectations, they are usually trying to learn one of three things: 1. Whether your target fits their budget 2. Whether you understand your market value 3. Whether you will negotiate professionally Your goal is not to name the perfect number on the first try. Your goal is to avoid pricing yourself out or pricing yourself down. ### Focus on your target compensation, not one random salary number A strong **salary expectations interview answer** is based on your full compensation target: - Base salary - Bonus or commission - Equity - Sign-on bonus - PTO - Remote flexibility - Health benefits - Learning budget - Title and growth path This matters because a $95,000 offer with a 15% bonus and strong benefits may beat a $102,000 offer with weak benefits and no upside. ### Set three numbers before you interview Go into the interview with these written down: - **Target number:** what you would be happy to accept - **Acceptable range:** what you can justify in the market - **Walk-away number:** the point where the role no longer makes sense Be honest with yourself about the walk-away number. If you ignore it, you will negotiate emotionally and second-guess yourself later. ## Step 2: Research a market-backed range before the interview If you do not know **how to give salary range** answers with confidence, research is the missing step. ### Build your range from four sources Use a mix of: - Salary data sites for your role, location, and level - Job postings that list pay ranges - Recruiter conversations - Your own background: years of experience, scope, certifications, revenue impact, leadership, technical depth Then adjust for: - Geographic market - Remote vs. hybrid vs. onsite - Company size - Industry pay norms - Seniority of the actual work, not just the title ### Use a narrow, defensible range Good range: $95,000 to $105,000 Weak range: $80,000 to $120,000 A narrow range signals that you have done your homework. A huge range tells the employer you are guessing. ### Match your ask to your story Your compensation range should align with how you position yourself. If your resume and interview examples sound mid-level, a senior-level ask will feel disconnected. Before interviews, it helps to tighten your positioning in a [free resume builder](/free-resume-builder) so your title, impact, and scope support the range you want. ## Step 3: Decide when to answer and when to delay You do not always need to answer immediately. One of the most useful negotiation skills is knowing **how to delay salary discussion** without sounding difficult. ### Delay early, answer later If salary comes up in the first recruiter screen and you still need to understand the role, use a soft delay. Example script: > I'm flexible at this stage and would like to learn more about the role, team, and total compensation before giving a firm range. If you can share the budgeted range, I can tell you whether we're aligned. This works because it keeps the discussion open while inviting them to reveal their range first. ### When not to delay Do not keep dodging the question deep into the process. If you have enough context and they ask directly, answer clearly. Repeated evasiveness can read as lack of preparation. ### If the application requires a number Use one of these approaches: - Enter the posted range midpoint if the system requires digits only - Enter a reasonable target slightly above midpoint if your experience supports it - If text is allowed, write: "O