What Are Your Salary Expectations? How to Answer + Examples

1. Why interviewers ask about salary expectations

The question sounds adversarial, and candidates often treat it that way. In most cases it isn't. The person asking has a budget for the role and a queue of candidates, and they're trying to find out early whether a conversation is worth continuing for either side. Discovering a $30,000 gap after four rounds of interviews wastes their time as much as yours.

That said, the answer does more than screen. Whatever figure you name becomes the reference point the rest of the process moves around. If you say $70,000 for a role budgeted at $85,000, very few employers will talk you upward. That's not malice; it's what any negotiator does with a number offered voluntarily. So the honest framing is: the question is a legitimate check, and your answer is also an anchor. Both things are true, and both are reasons to have a researched number ready rather than an improvised one.

There's a secondary signal too. How you answer says something about how you'd handle a client conversation, a vendor quote, or a difficult discussion with a manager. A candidate who says “I've looked at what this role pays in this state, here's my range, here's why” reads as someone who does the work. A candidate who says “whatever you think is fair” reads as someone who hasn't thought about it — and, quietly, as someone who can be paid less.

2. When the question comes up

The wording changes depending on who's asking and when, but the underlying question is always the same. You'll typically meet it in four places.

• • The application form. A written field rather than a conversation. That's a different problem with different rules — covered in our guide to what to put for desired salary.
• • The recruiter screen. The most common place. Usually asked in the first ten minutes, often before you know much about the role.
• • The hiring manager interview. Asked later, with more context available, and usually more open to discussion.
• • The offer conversation. At this point it isn't really an expectations question any more — it's a negotiation.

Earlier in the process, you know least and have the least leverage, so keeping some flexibility is reasonable. Later, you know the scope and they've invested in you, so a specific figure with a clear justification carries more weight. Adjust the precision of your answer to the stage you're at — but never adjust it to zero.

3. How to prepare your answer

Preparation takes about fifteen minutes and it's the difference between an answer that holds up and one that collapses under a follow-up question. Work through five things before your first call — ideally as part of preparing for the interview itself.

1. 1. Look up the market rate. Find the median wage for the occupation in the state where the job sits, and note the reported spread around it.
2. 2. Place yourself honestly. Early-career candidates sit lower in the distribution; people with specialised experience or credentials sit higher. Where do you actually fall?
3. 3. Read the job description again. Supervision, budget ownership, licensing, on-call duty or travel all make a role bigger than the job title suggests.
4. 4. Set three numbers. Your target, the top of your range, and the private floor you won't discuss out loud. Only the first two ever leave your mouth.
5. 5. Write one justification sentence. “Market rate for this occupation in [state], plus [number] years doing [thing].” If you can't say it in one breath, it isn't ready.

Wage figures on FindMySalary come from the U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics program, which reports wages by occupation and area. They're a benchmark for the occupation as a whole, not a forecast of any individual offer: real pay varies with experience, education, industry, employer and other factors.

4. A simple structure for the answer

Strong answers to this question tend to have the same four parts, in the same order. Once you've heard the pattern you can improvise inside it.

• • Anchor. Name the basis: market pay for this occupation, in this state.
• • Number. Give the range or the figure. Don't bury it or trail off.
• • Reason. One clause about your experience or the scope of the role.
• • Return. A short question back — their range, the scope, the wider package.

Roughly twenty seconds, spoken. Anything much longer starts to sound like justification, and long justifications invite negotiation against you. Say the number, say why, ask a question, stop talking. The silence after a number is uncomfortable for about two seconds and then someone else fills it — let that be them.

5. Range, single number, or deflect?

All three appear in advice articles, and they don't work equally well.

A range

The safest default in a spoken conversation. It signals research, leaves room for the scope of the job to change what's reasonable, and feels collaborative. The catch is well known: employers hear the bottom. Treat the lower bound as the number you're actually naming, and keep the spread tight — roughly 10–15% between the ends. As an illustration only, a candidate targeting around $78,000 might say $75,000–$85,000. Saying $60,000–$110,000 for the same role communicates nothing except uncertainty.

A single number

Stronger later in the process, when you understand the role. It's decisive, it anchors firmly, and it invites a direct response. It also removes your flexibility if the job turns out to be larger than advertised, and it needs a justification ready, because you will be asked for one.

Deflecting

“I'm flexible” or “whatever's fair for the role” rarely helps. Interviewers hear it as unpreparedness rather than tactics, and it leaves the recruiter with nothing to take to the hiring manager. A genuine deferral — asking one scoping question before giving a number — is fine once. Refusing twice tends to end with the recruiter guessing low on your behalf.

6. Example answers you can adapt

Copy any of these and replace the bracketed parts with your own details. Every figure shown is illustrative — use your own researched numbers, not these.

Based on the market rate for [occupation] in [state] and my [number] years of experience, I'm expecting somewhere in the $[lower]–$[upper] range. I'd like to hear more about the scope of the role before narrowing that down — does that line up with what you've budgeted?

I'm targeting $[figure] base. That's anchored to what [occupation] roles pay in [state], plus the [specific skill or responsibility] side of this job, which goes beyond the standard scope. I'm open to discussing the full package as well.

I'd rather give you a useful answer than a guess, so it would help to know the range you've budgeted for the role. I've researched market pay for [occupation] in [state], so I have a clear sense of what's reasonable — I just want to make sure we're comparing the same job.

I saw the posted range of $[posted lower]–$[posted upper], and that works for me. Given my experience with [relevant responsibility], I'd be looking at the upper half of it, around $[figure].

I've looked at what [occupation] roles pay in [state], and for someone at the start of their career the market sits around $[lower]–$[upper], so that's my expectation. I care more about learning [skill] in this role than about squeezing the number, but I'd like to be paid fairly for the market.

Happy to talk about it — I'd just like to understand the responsibilities a bit better first, since that changes what's fair. Could you tell me more about [scope question]? Then I can give you a specific number rather than a vague one.

I'm looking for $[figure] per hour, which matches the market rate for [occupation] in [state]. If the role includes [overtime / weekend shifts / on-call], I'd want to factor that into the conversation too.

Read them aloud once before your interview. Salary sentences that look calm on a screen can come out apologetic when spoken, and the difference between “I'm expecting” and “I was sort of hoping for maybe” is worth real money.

7. Answering a recruiter on the phone screen

The recruiter screen is where this question lands hardest, because it arrives before you know the responsibilities, the team, the hours or the benefits. It's also the least adversarial version of the conversation: recruiters are usually working to a band handed to them, and many will tell you what it is if you ask plainly.

A workable sequence is to answer with a range, attach one line of justification, and close with a question about their budget. That gives the recruiter something usable — which is what keeps you in the process — while opening the door to the information you actually want. If they share a band that sits above your range, don't scramble to revise your number on the call; note it, and let the offer stage do its job.

One practical note: some U.S. states and cities restrict employers from asking about your salary history, and several require pay ranges to be disclosed. Rules vary by jurisdiction and change over time, so check what applies where you are. Regardless of the law, “what do you currently earn?” and “what are you expecting?” are different questions, and you're entitled to answer the second one without answering the first.

8. How to ask for their range instead

Asking the employer to go first is completely normal and rarely held against you. It works best when it's paired with evidence that you've done your own homework, rather than used as a way to avoid the question.

• • Ask directly and pleasantly: “What range have you budgeted for this role?”
• • Signal your research in the same breath, so it doesn't read as a dodge.
• • If they answer, place yourself inside their band with a short reason.
• • If they decline, give your range — you asked, they passed, your turn.
• • Don't ask three times. Once is confident; repeatedly is evasive.

When they do share a band, resist the reflex to name the middle. The midpoint is where unremarkable candidates land. If your experience genuinely maps to the top half of the role's requirements, say so and name a figure in the top half.

9. Entry level, career changers and internal moves

With little experience, the temptation is to answer with gratitude instead of a number. Market data solves this: the wage distribution for an occupation includes people at the start of their careers, so you can name a range that's defensible without claiming seniority you don't have. Anchor low in the distribution, be explicit that that's deliberate, and don't apologise for naming anything at all.

Changing careers, your anchor is the new occupation, not the old one. Your previous salary is irrelevant to what this job pays — in either direction. Name the market range for the role you're moving into and point at the transferable parts of your background that shorten your ramp-up.

Moving internally, the employer already knows your current pay, which removes the anchoring problem and creates a different one: internal moves are often priced as a small adjustment to your existing salary rather than as the market rate for the new role. Bring external data anyway, and frame the conversation around what the new position is worth. The mechanics of that discussion are closer to asking for a promotion than to an outside interview.

10. Putting your expectations in writing

Sometimes the call ends before the number gets settled, or you're asked to send your expectations by email. Writing has an advantage: you can choose the words carefully, and the figure arrives without the nervous hedging that creeps into speech. Keep it to four short paragraphs — thanks, the number with its basis, a note of flexibility on the overall package, and a question.

Subject: Following up — compensation expectations

Hi [Name],

Thanks for the conversation about the [job title] role — I enjoyed hearing how the team is set up.

To put my expectations in writing: based on market pay for [occupation] in [state] and my [number] years of experience with [relevant responsibility], I'm targeting a base salary of $[lower]–$[upper].

I'm flexible on the shape of the overall package, and I'd be glad to talk through how you've budgeted the role.

Best,
[Your name]

If you've already received an offer and want to counter rather than state expectations, that's a different email with a different structure. There are copy-ready templates for it in the salary negotiation email guide.

11. When their budget is below your expectations

Occasionally the recruiter answers your range with “our band tops out below that.” That isn't a failure of your answer; it's the question doing exactly what it exists to do, early enough that neither side wastes weeks.

• • Check the gap against market data before reacting — one of you may be mispriced.
• • Ask what the total package includes; bonus, retirement match and leave are real money.
• • Ask whether the role could be scoped or levelled differently to reach your range.
• • Decide whether the shortfall is material to you, or a few thousand you'd trade for other things.
• • If it's genuinely too far apart, say so warmly and leave the door open.

If the gap is small and the role is right, the offer stage is where it gets closed. The step-by-step version of that conversation is in our salary negotiation guide.

12. Mistakes that cost candidates money

• • Naming your current salary. It answers a question about the old job, not this one, and it caps you at yesterday's price.
• • Refusing to give any number. Recruiters need something to work with; silence gets filled with a low guess.
• • A range so wide it's meaningless. A $40,000 spread says you haven't researched the role.
• • Setting the floor at your walk-away number. The bottom of your stated range is where the conversation starts, not where it ends.
• • Justifying with your expenses. Rent and childcare costs are real, but they say nothing about the value of the job.
• • Talking past the number. Every extra sentence after your figure sounds like you're negotiating against yourself.
• • Ignoring the posted range. They told you the budget; answering outside it needs an explicit reason.
• • Treating it as binding. An expectation stated in a screening call isn't a signed agreement — the offer is.

13. Frequently asked questions