"What are your salary expectations?" is one of the questions that stops candidates mid-breath. Answer too low and you leave money on the table. Answer too high and you risk being screened out. Answer with "I'm flexible" and you look like you haven't done your homework.
The good news: there's a framework for this, and it works in almost every scenario.
Here's what this guide covers:
- Why interviewers ask — and what they're really evaluating
- When the question tends to come up — and how timing affects your answer
- Three strategies — give a range, deflect early, or name a number — with sample phrases for each
- How to research salary data so your range is defensible
- Application forms — what to put when forced to enter a number
- State laws — CA, CO, and NYC rules that may limit what employers can legally ask
Why They Ask — and What They're Evaluating
Hiring managers use this question for two reasons:
- Budget fit. If your expectations are far above the approved range, they'd rather know now than after three more rounds.
- Self-awareness. A candidate who has clearly researched compensation signals competence. One who names a random number signals the opposite.
The question is less of a trap than it seems. Most employers have a range in mind. Your job is to land inside it — ideally near the top — without committing to a floor before you have leverage.
When the Question Comes Up
Application forms: Some forms require a number before you even speak to anyone. See the application form section below for how to handle this.
Early-stage screening (phone or first-round): You know the least about scope, team, and growth trajectory. This is the worst time to commit. Deflecting here makes sense.
Mid-process (second or third round): You know more. If they push, give a researched range. If you've reached second interview questions at this point, you have enough context to anchor confidently.
Offer stage: Now you have leverage. This is the one moment where naming a specific number often works better than a range — it signals you've done the math.
Strategy 1: Give a Research-Backed Range
This is the right move for most mid-process conversations. A range signals you've done homework, gives the employer room to land, and protects you from locking in too low.
How to set your range:
- Set the floor at the minimum you'd genuinely accept — not what you'd be happy with, but what you'd actually say yes to.
- Set the ceiling 15–20% above that. Where you end up is usually somewhere in the middle.
- Make sure the floor is already above your current or most recent salary (if you're aiming for growth).
Sample phrase:
> "Based on my research for this role in [city], and given my background in [X], I'm targeting $90,000 to $105,000. That said, I'm open to the full package — equity, bonus structure, and benefits all factor in."
Anchoring high means the employer negotiates down from your ceiling — not up from a low number you locked in too early.
Strategy 2: Deflect Early (Without Sounding Evasive)
Early in the process — especially on a recruiter screen — you often don't know enough to give a well-informed number. Deflecting isn't dodging; it's sensible.
Sample phrases:
> "I want to make sure I fully understand the scope before I give you a number that's useful. Can we revisit this once I've had a chance to learn more about the role?"
> "I'd rather focus on fit first. If we get to the offer stage, I'm confident we can find a number that works for both sides."
> "I'm open at this stage. What's the budgeted range for this position?"
That last one is underrated. Many recruiters will just tell you — especially in states where pay transparency is required by law (more on that below). If they give you a range, you've learned something without committing anything.
When not to deflect: If they've asked twice and this is round three, deflecting signals either that you're unserious or that your number is out of range. At that point, give a range.
Strategy 3: Name a Specific Number
This works best at the offer stage, when you've decided you want the job and want to anchor the negotiation clearly.
Salary negotiation research on Wikipedia shows candidates who negotiate see an average increase of $4,913 from their initial offer. Naming a number — rather than waiting — is how that negotiation starts.
Sample phrase:
> "Given my research and the full picture of the role, I'm looking for $112,000 as a base. I think that reflects the level of experience I'm bringing and what's competitive for this market."
Rules for naming a number:
- Go specific, not round. "$112,000" reads as researched; "$110,000" reads as guessed.
- Don't apologize or hedge immediately after. Say the number, then stop talking.
- Have your research ready to back it up if pushed.
How to Research Your Number
Before any interview where salary might come up, pull data from at least two sources:
| Source | Best for |
|---|---|
| Levels.fyi | Tech roles — very granular by company, level, and location |
| BLS Occupational Employment Statistics | Baseline for any occupation nationally or by metro area |
| LinkedIn Salary | Cross-checking ranges by title and geography |
| Glassdoor / Payscale | Broader market data; useful for non-tech roles |
What to factor in beyond base salary:
- Equity (RSUs, options) — especially relevant in tech and startups
- Bonus structure (target vs. max)
- Benefits (health coverage quality, 401k match, PTO)
- Remote vs. in-office — remote roles sometimes carry market adjustments
If an employer says your range is too high, ask: "Is that just the base, or the total package?" That question often reveals room that wasn't visible before.
One note on salary data generally: ranges vary widely by geography. The same software engineering role pays $30–40K more in San Francisco than in Austin. Always filter by location.
Application Forms: What to Enter
When a form forces a number before any conversation:
Option 1 — Enter your floor. The floor of your target range is defensible and keeps you in consideration if the budget is tight. You can always negotiate up from here.
Option 2 — Enter 0 or $1. Some applicant tracking systems accept this and flag it for manual review. Use this only if you're confident the role is worth pursuing even if budget is tight.
Option 3 — Enter a mid-range number. Not your ideal, not your minimum. A neutral anchor that doesn't screen you out and doesn't lock you in.
Avoid entering wildly inflated numbers in hopes of negotiating down — ATS filters may auto-reject you before a human ever sees your application.
State Laws: What Employers Can and Can't Ask
Several states have salary history bans — meaning employers cannot legally ask what you earned at a previous job. This matters because your history is often used to anchor offers low.
California California Labor Code § 432.3 prohibits employers from requesting or using salary history to set pay. Employers with 15 or more employees must include a pay scale in every job posting. You can refuse to disclose — and they cannot use refusal as grounds for rejection.
Colorado Colorado's Equal Pay for Equal Work Act (effective 2021) requires all job postings to include a pay range. This applies to remote roles too — if a Colorado resident could do the job, the range must appear.
New York City Since November 2022, NYC employers with four or more employees must include salary ranges in job postings. Employers cannot ask about salary history or use it in hiring decisions. Civil penalties for willful violations reach $25,000 per offense.
If you're interviewing in one of these jurisdictions and the employer asks for your history, you're within your rights to decline — and you should.
Knowing Your Number Isn't Enough
Researching salary data and preparing sample phrases gets you ready for the conversation with HR. The recruiter, however, often doesn't set the final number — the hiring manager does. That's where the actual negotiation happens, and it's a different conversation.
When you ask why you want this job and back it up with specifics tied to the team's actual work, you shift from "candidate with a salary ask" to "person they want to hire." That context changes what the manager is willing to fight for in the budget conversation.
If you want to find and reach the hiring manager directly — not just wait to meet them in round three — Articuler uses semantic matching across 980M+ professional profiles to surface the specific person behind a role. You can send a personalized outreach note that gets a reply — and walk into that salary conversation with someone who already knows why they want you.
FAQ
Is it okay to ask the interviewer about their salary range first?
Yes — and it often works. Especially in states with pay transparency laws, recruiters may simply tell you. Try: "What's the budgeted range for this role?" You might get an answer without having to reveal anything first.
What if my expectations are above their budget?
Ask whether the total package has flexibility — equity, signing bonus, annual review timing. Sometimes the base is fixed but other components aren't. If there's a real gap, it's better to know early than after multiple rounds.
Should I give the same number to the recruiter and the hiring manager?
Not necessarily. Give a range to the recruiter. When you get to the hiring manager, you can refine it based on everything you've learned about the role. The hiring manager often has more budget flexibility than the recruiter does.
What does "DOE" (dependent on experience) mean on a job posting?
It means the employer hasn't committed to a public range. Use external salary data to establish your own anchor and name it — don't let "DOE" become a reason to leave your number off the table.
Can I change my salary expectations after giving a number?
Yes, within reason. If you learn the role has significantly more scope than initially described, it's fair to revisit: "Now that I understand the full responsibilities, I'd want to adjust my target to $X — does that work with your range?"