# How to Answer "What Are Your Salary Expectations?" (with Examples)

> It's usually the most uncomfortable question in the process, and it often comes in the first call. Here's what to say, depending on when they ask.

URL: https://immersiveconversation.ai/blog/how-to-answer-salary-expectations  
Updated: 2026-11-20

## Short answer

Early in the process, ask for their range first: "I'd like to learn more about the role. Could you share the budgeted range?" If they insist, give a researched range whose bottom is a number you'd be happy with: "Based on similar roles in this area, I'm looking at 80,000 to 90,000, depending on the overall package." Avoid a single low number, and never give your current salary unless you want to.

"What are your salary expectations?" sounds like a simple question. It isn't. Answer too low and you may leave thousands on the table for years; answer too high and you worry they'll move on. And it often arrives in the first phone screen, before you know much about the job.

The good news is that there are a few reliable ways to answer, and the right one depends mostly on *when* they ask. If you want a script tailored to your role and number, try the free [salary negotiation script generator](/tools/salary-negotiation-script).

## First, know your range

You can't answer well without numbers you can defend. Look at salary surveys, job listings that publish pay (many US states now require it), and sites where employees share salaries. Ask people in your field if you can.

From that research, set a range of about 10 percent. The bottom should be a number you'd be happy with, not your absolute minimum. Your walk-away number stays private.

## In the first call: ask for their range

Early on, you know little about the role, the level or the benefits. It's reasonable, and common, to ask them to go first:

> "I'd like to learn more about the responsibilities before I name a number. Could you share the budgeted range for this role?"

Most recruiters have a range and many will share it. If theirs is lower than yours, you've learned that early, which saves everyone time. If it overlaps, you can say: "That works for me as a starting point, depending on the overall package."

## When they insist: give a researched range

If they press, don't dodge again. Give your range, with the reason it's based on:

> "Based on what I've seen for similar product designer roles in Chicago, I'm looking for something in the range of 95,000 to 105,000, depending on the overall package."

Three things make this answer work: it's specific, it's anchored in research rather than in what you need, and "depending on the overall package" leaves room to negotiate bonus, equity, vacation or remote work later.

## In a later interview, with more information

By the final rounds you know the role better, and the question is closer to the real negotiation. You can be more precise, and connect your number to the job:

> "Now that I understand the scope, especially leading the mobile team, I'd be looking at around 110,000. Is that in line with what you had in mind?"

## Example answers for different situations

| Situation | What you can say |
| --- | --- |
| You don't know enough yet | "I'd like to understand the role better first. What range have you budgeted?" |
| They insist on a number | "Based on similar roles in this area, I'm looking at 80,000 to 90,000, depending on the package." |
| Their range is lower than yours | "Thanks for sharing. My research puts this kind of role a bit higher, around 90,000. Is there flexibility in the range?" |
| You're changing careers | "I'm focused on finding the right fit. Based on the skills I'd bring from my previous role, I'm looking at 70,000 to 78,000." |
| They ask for your current salary | "I'd rather focus on what this role is worth. Based on my research, I'm looking at…" |

## What to avoid

- **A single low number "to be safe".** It becomes the anchor for everything that follows.
- **Answering with what you need.** Rent and bills aren't arguments for an employer; market rates and your experience are.
- **"Whatever you think is fair."** It sounds polite and almost always costs you money.
- **Apologizing for your number.** Say it calmly and stop. A pause after a number is normal.

## Say it out loud before the call

Knowing the right answer and saying it calmly when a recruiter asks are different skills. Write your answer, then say it out loud until it sounds natural, including the number. Better still, rehearse with someone who pushes back: a friend playing the recruiter, or an AI partner that asks the question the way a real one would. When the question comes, you'll already have said your answer ten times.

## Frequently asked questions

### Should I give a number or a range?

A range, in most cases. It gives both sides room, and you control where it starts. Make sure the bottom of the range is a number you'd genuinely accept, because employers often anchor to it.

### What if an application form requires a number?

If the field accepts text, write "Negotiable" or "Open, based on the full package". If it only accepts a number, enter the bottom of your researched range, not a low "safe" number.

### Do I have to tell them my current salary?

In many US states and cities, employers aren't allowed to ask about salary history. Even where they can, you can redirect: "I'd rather focus on what this role is worth. Based on my research, I'm looking at…"

### Is it bad to say "I'm flexible"?

Saying only "I'm flexible" invites a low offer. It's fine as part of an answer that also includes a researched range, for example "…and I'm flexible depending on the overall package".

---

Practice these conversations out loud with an AI partner: https://immersiveconversation.ai/setdemo
