How to Answer "What Are Your Salary Expectations?" (With Scripts)

The salary expectations question isn't small talk. It's a filtering tool, and it's almost always asked by a recruiter rather than the hiring manager, usually in the first phone screen before you've met anyone else on the team.

Recruiters ask this question for a practical reason: they're managing a pipeline of candidates against a budgeted range that was set before the job was ever posted. If your number falls well outside that range, they'd rather find out in a 20-minute call than after three more interview rounds. From their side, the question isn't adversarial. It's a scheduling and resourcing decision.

That doesn't mean the question is neutral for you. How you handle salary expectations early in the process shapes the anchor for everything that follows. Research on negotiation consistently shows that whoever names a number first sets a psychological anchor that the rest of the conversation tends to orbit around. Say a number too low, and even a generous later offer may land below what you could have gotten. Say a number with no research behind it, and you risk sounding out of touch with the role or the market.

Understanding the recruiter's actual goal changes how you prepare. They're not trying to trap you. They're trying to confirm alignment before investing more time. Your job is to give them enough to move forward — a defensible range, delivered with confidence — without locking yourself into a number you haven't backed with research.

There's a second, quieter reason this question matters so much: the number you give at the screening stage often becomes the reference point for the eventual offer, even though a lot happens between that first call and the final decision. Recruiters take notes. Applicant tracking systems store your stated range. If you undersell yourself in week one, hiring managers several weeks later may still be working from that early figure, even after seeing exactly how strong a candidate you are. That's why treating this as a throwaway question, or answering it without preparation, tends to cost more than it seems to in the moment.

Most candidates are caught off guard by how early the salary expectations question arrives. It's rarely saved for the final round. It typically shows up in one of three places:

**In the application itself.** Many online application forms now include a required salary field before you've spoken to anyone. Some job boards make this mandatory; treat it the same way you would a verbal answer — as a range, not a fixed number, when the form allows it.

**On the first recruiter screening call.** This is the most common moment. After a few minutes of background questions, recruiters often ask about salary expectations early so they don't schedule further rounds for a mismatch. Expect it within the first 10 to 15 minutes of that call.

**Buried inside a broader question.** Sometimes it's phrased indirectly: "What are you currently earning?" or "What would it take for you to make a move?" These are the same question wearing different clothes, and they deserve the same prepared answer.

It's worth noting how this differs from salary negotiation later in the process. The salary expectations question during screening is about establishing a workable range before you've been evaluated. Negotiating a specific offer happens after you've received a number in writing, when you have leverage from a formal offer and can counter with specifics. The two moments call for different approaches — this guide focuses on the earlier one.

A growing number of states, including California, Colorado, New York, and Washington, now require employers to list a salary range directly in the job posting. If the range was already published, it's fair to reference it directly: "I saw the posted range was $X to $Y, and based on my experience I'd expect to land in the upper half of that." This shows you did your homework and keeps the conversation grounded in numbers the employer already put on the table.

When the application form itself asks for a number before you've spoken to anyone, treat it with the same care as a verbal answer. If the field accepts a range, use one rather than a single figure. If it forces a single number, use the top of your researched range rather than the middle — you can always come down during a conversation, but it's much harder to move a written number up later. Never write "negotiable" alone with no figure attached; some applicant tracking systems auto-screen those submissions out for lacking a data point to filter on.

The safest and most professional way to answer what are your salary expectations is with a researched range, not a single number. A range gives you room to negotiate later while still showing the recruiter you've thought seriously about compensation. This is the core of how to answer what are your salary expectations in almost any screening call: come in with numbers you can defend, not a guess pulled out of the air.

**Step 1: Research before the call, not during it.** Use sites like Glassdoor, Levels.fyi, Payscale, and LinkedIn Salary to find data for your specific title, seniority level, and location. Cross-reference at least two sources — a single data point can be skewed by outdated or self-reported entries.

**Step 2: Build a range with a strategic width.** A range that's too narrow (say, $2,000 apart) gives you no negotiating room. A range that's too wide (say, $30,000 apart) signals you haven't done the research. A workable range is usually 10 to 15% wide, anchored so your minimum is still a number you'd genuinely accept.

**Step 3: Anchor toward the upper-middle of your researched range.** If market data suggests $75,000 to $95,000 for the role, don't open at the bottom. Something like "$85,000 to $95,000, depending on the full compensation package" keeps you competitive without pricing yourself out.

**Step 4: Add a qualifier that keeps the door open.** Phrases like "depending on the full package" or "based on the scope of the role" signal flexibility around benefits, equity, bonus structure, and remote work — without undercutting your number.

Here's a full example: "Based on my research for this role and my seven years of experience, I'm looking at a range of $90,000 to $105,000, depending on the complete compensation package. I'm also open to discussing how base salary and other benefits might balance out."

This answer does three things at once: it shows preparation, it protects your floor, and it leaves room to negotiate once you actually have an offer in hand.

Sometimes the smarter move is to redirect the question back to the employer before giving your own number — but this only works if it's done cleanly, not evasively.

The classic deflection line is: "I'd love to learn more about the role and its responsibilities before landing on a number — do you have a budgeted range for this position?" This is a legitimate move. Recruiters usually do have an internal range, and getting it first tells you exactly where to anchor your own answer.

The risk is that deflection can backfire if it's your only move. Many recruiters are trained to redirect right back: "I understand, but can you give me a ballpark to make sure we're aligned?" If you deflect again at that point, you start to look like you're avoiding the question rather than genuinely trying to gather information — and that reads as evasive, not strategic.

The fix is to treat deflection as a first attempt, not a wall. Try it once. If the recruiter presses, pivot immediately to a researched range rather than deflecting a second time:

"Totally understand you need a number to move forward. Based on my research for similar roles at this level, I'd expect somewhere in the $85,000 to $95,000 range, though I'm flexible depending on the full picture."

This two-step approach — ask first, then answer with a range if pressed — gets you the best of both. You give the recruiter the chance to name a number first, which can work in your favor, but you never leave the conversation stalled or come across as unwilling to engage. Deflection is a tool for gathering information, not a strategy for avoiding the salary expectations question altogether.

It helps to walk through a full recruiter call script rather than just isolated lines, since the salary expectations question rarely arrives in a vacuum — it's usually part of a longer exchange.

**Recruiter:** "Thanks for sharing your background. Before we go further, can I ask what your salary expectations are for this role?"

**You (deflect first):** "Sure — before I give a number, is there a budgeted range you're working with for this position? That'll help me give you a more useful answer."

**Recruiter:** "We try to keep candidates' expectations in mind first, but generally we're looking somewhere in the $80,000 to $100,000 range for this level."

**You (respond with alignment):** "That's helpful, thank you. Based on my experience and what I've seen for similar roles, I'd be looking at the upper half of that range, closer to $95,000 to $100,000, depending on the full compensation package including benefits and any bonus structure."

If the recruiter doesn't offer a range and presses for your number directly, the DESC script framework is useful here: **Describe** the situation neutrally ("I want to make sure I give you an accurate number"), **Express** your position ("Based on my research, here's where I land"), **Specify** your actual range, and state the **Consequences** or conditions ("depending on the full package"). This keeps your tone collaborative rather than defensive, even when you're holding your ground on a number.

It's also worth reframing the moment using the WIIFT (What's In It for Them) lens. The recruiter isn't just collecting a number — they're checking whether continuing the process is a good use of everyone's time. Framing your answer around alignment ("I want to make sure we're both investing time in something that works for everyone") signals that you understand their goal, not just your own.

One more scenario worth rehearsing: what happens if the recruiter pushes back a second time after you've already given a range. "I hear you, but our budget is closer to $80,000 — would that work?" This is not the moment to cave immediately or to walk away. A steady response holds your ground while staying open: "I appreciate you sharing that. $80,000 is below where my research and experience put me, but I'd still like to keep learning about the role — can we revisit compensation once we're both further along and I have a clearer picture of the full scope?" This keeps the door open without pretending the gap doesn't exist, and it moves the harder conversation to a stage where you'll have more information and more leverage.

A handful of avoidable mistakes account for most of the damage candidates do to themselves when answering the salary expectations question.

**Giving a single hard number with no range.** A specific figure with no flexibility either overshoots and screens you out, or undershoots and leaves money on the table with no room to recover later.

**Sharing your current salary unprompted.** In many places this is no longer even a legal question for employers to ask directly, and volunteering it anchors the conversation to your past compensation rather than the market value of the new role.

**Apologizing for your number.** Phrases like "I know this might be a lot, but..." undercut your own answer before the recruiter has even reacted. State your range plainly and let it stand.

**Refusing to answer at all.** Some candidates try to dodge the question entirely with "I'm open to whatever is fair." This isn't deflection — it's an absence of an answer, and it usually just prompts the recruiter to ask again, more directly, while you look unprepared.

**Skipping the research step.** Walking into the call without checking market data for your role, level, and location means you're guessing in real time, which comes through in your tone even if the number happens to be reasonable.

**Letting nerves flatten your delivery.** Phone screens strip away body language, so tone and pacing carry more weight than usual. A range delivered with hesitation and filler words sounds far less confident than the same range delivered clearly, even if the content is identical.

Most of these mistakes share a root cause: candidates think through their answer but never actually say it out loud before the real call. Reading a range in your head feels fine. Saying it clearly, at a natural pace, without hedging, is a different skill entirely.

The gap between a written answer and a spoken one shows up constantly. On paper, "$90,000 to $105,000, depending on the full compensation package" reads clean and confident. Said out loud for the first time, under a little pressure, it can easily come out as "um, I guess somewhere around, maybe ninety to, I don't know, a hundred five, if that works?" Same number, completely different impression. The recruiter isn't just recording the figure — they're forming an opinion about how you handle direct, high-stakes questions, which is exactly what the rest of the interview process will keep testing.

Learning how to answer what are your salary expectations takes more than deciding on a number. It takes rehearsal, because the moment tends to arrive with little warning and some pressure to respond quickly.

**Step 1: Finalize your range in writing first.** Pull your research together and write down the exact range you'll say, along with your qualifying phrase ("depending on the full package"). Having this fixed in advance keeps you from improvising a worse number under pressure.

**Step 2: Prepare your deflection line and your fallback.** Write out both the redirect question and the researched-range answer you'll give if the recruiter pushes back. Knowing both in advance means you're never caught deciding in the moment.

**Step 3: Say it out loud, more than once.** Reading your range silently and saying it aloud are not the same exercise. Speaking under even mild simulated pressure reveals hesitations, filler words, and awkward pacing that reading never surfaces.

**Step 4: Practice the full exchange, not just your line.** The salary expectations question is a back-and-forth, not a monologue. Rehearse the recruiter's likely follow-ups — "Is that number firm?" or "What if the range is lower than that?" — so you're not building your response from scratch in real time.

**Step 5: Get feedback on tone, not just content.** It's easy to focus on getting the number right and forget that delivery is what makes a number sound confident or shaky.

SayNow AI lets you rehearse this exact exchange in a realistic recruiter screening simulation. You practice your answer to what are your salary expectations out loud, get natural follow-up questions the way a real recruiter would ask them, and receive feedback on pacing, confidence, and clarity. Running through the recruiter call a few times before it happens for real turns a moment that usually catches people off guard into one you've already handled.