How to Answer "What Are Your Salary Expectations?" (Real Numbers)

The salary expectations question catches most tech professionals off guard. Say a number too low, and you've anchored yourself into a lower offer. Go too high, and you risk being dismissed as unrealistic. Stay vague, and you sound unprepared. This single question can determine whether you leave $10,000–$30,000 on the table or negotiate from a position of strength.

The good news: there's a reliable framework for answering this question that works across tech roles, experience levels, and both US and Canadian markets. This guide shows you exactly what to say, when to say it, and how to back it up with data that protects your earning potential.

Why Employers Ask About Salary Expectations (And What They're Really Testing)

Hiring managers and recruiters ask about salary expectations for three specific reasons:

• Budget alignment: They need to know if you're within the approved compensation range before investing more interview time
• Market awareness: Your answer reveals whether you understand your market value and have done research
• Negotiation preview: How you handle this question signals how you'll negotiate the actual offer

According to research from the U.S. Bureau of Labor Statistics and Statistics Canada, compensation transparency has increased significantly, but many employers still ask this question early to filter candidates. Your goal is to delay specific numbers while demonstrating you're informed and reasonable.

When This Question Comes Up

Expect salary questions at three distinct stages:

1. Initial recruiter screen: Often in the first 10 minutes, sometimes even before scheduling
2. Hiring manager conversation: Usually toward the end of the first or second interview
3. Final round or offer stage: When they're ready to make a decision

Your strategy changes depending on timing. The earlier they ask, the more you should deflect gracefully. The later they ask, the more specific you can be—but only after you've demonstrated your value.

The Three-Part Formula for Answering Salary Expectations

Here's the framework that positions you for the strongest possible offer:

Part 1: Acknowledge the Question (Don't Dodge)

Start by showing you're comfortable discussing compensation professionally. Never say "I don't know" or act caught off guard. Instead:

Key takeaway: "I'm definitely open to discussing compensation. Before I share a specific range, I'd love to learn more about the full scope of the role, the team structure, and what success looks like in the first year. That context will help me give you a range that makes sense for both of us."

This response accomplishes three things: you sound prepared, you've created space to learn more, and you've shifted from "what do you want?" to "what is this role worth?"

Part 2: Research and Anchor With Market Data

When you do share numbers—typically in the second or third conversation—ground them in research. Use specific sources:

Script example for a Senior DevOps Engineer in Seattle or Vancouver:

"Based on my research of similar DevOps roles in the Seattle and Vancouver markets—using LinkedIn Salary data and Glassdoor—I'm seeing a range of $115,000 to $145,000 USD for senior-level positions, or approximately $155,000 to $195,000 CAD. Given my six years of experience with Kubernetes and AWS, plus my background leading infrastructure migrations, I'd be looking at the $130,000–$150,000 USD range, depending on the total compensation package and growth opportunities."

Part 3: Give a Range, Not a Single Number

Always provide a range with these characteristics:

• Span of $15,000–$25,000: Wide enough to negotiate within, narrow enough to show you're informed
• Bottom of your range = your target: Employers typically anchor to the lower end, so set that where you'd actually be happy
• Include total compensation context: Mention you're considering base, bonus, equity, and benefits

What to say: "I'm targeting a base salary in the $105,000 to $125,000 range, and I'm also evaluating the overall package—equity, bonus structure, health benefits, and professional development budget. If the total compensation is compelling and the role is the right fit, there's flexibility within that range."

Scripts for Different Interview Stages and Scenarios

When Asked Too Early (Recruiter Screen, First 5 Minutes)

Situation: The recruiter asks before you know anything about the role.

Your response: "I'd be happy to discuss compensation once I understand more about the role's responsibilities and impact. Can you share the budgeted range for this position? That would help me understand if we're aligned before we both invest more time."

In many US states and Canadian provinces, employers are now required to disclose salary ranges when asked. This flips the script and often gets you valuable information first.

When You're Currently Employed

Your response: "I'm currently earning [your current salary + 10–15%], and I'm looking for a role that offers both career growth and appropriate compensation for the increased scope. Based on market research for this role, I'd be targeting $X to $Y, but I'm most interested in finding the right long-term fit."

This grounds your ask in reality while signaling you won't move for a lateral offer.

When You're Between Jobs or Coming Off a Layoff

Avoid mentioning your employment status in salary discussions. Instead, focus entirely on market data:

"For a [role title] with [X years] of experience in [key skills], the market range in [city/region] is typically $X to $Y. Given the scope we've discussed and my background in [specific relevant achievement], I'd be looking at $X as a starting point for base salary."

If you're navigating a job search after a layoff, understanding realistic interview timelines can help you plan your search strategy and avoid rushed salary decisions.

When They Push for a Specific Number

Situation: "We need a number to move forward."

Your response: "I understand. Based on the role as I understand it so far, I'd target around $125,000 base, with some flexibility depending on the complete package. Does that align with what you've budgeted for this position?"

Notice the phrase "as I understand it so far"—this leaves room to adjust if you learn the role has more scope than initially described.

How to Handle the "What's Your Current Salary?" Question

In many jurisdictions, asking about current salary is now illegal (including New York City, California, Massachusetts, and several Canadian provinces). But if you're asked:

Legal in your area? Redirect anyway: "I'd prefer to focus on the value I'd bring to this role rather than what I've earned previously. Based on this position's responsibilities and market rates, I'm targeting $X to $Y. Does that work within your budget?"

Illegal in your area? Politely note it: "I appreciate the question, but I understand that salary history questions aren't permitted in [location]. I'm happy to discuss my expectations for this role specifically—would that work?"

Common Mistakes That Cost You Thousands

• Naming a number first without research: You're guessing, and it shows. Always ground your range in data
• Giving your absolute minimum: If you say "$90,000," that becomes your ceiling. Add $15,000–$20,000 to your floor
• Apologizing or hedging: "I'm not sure, but maybe around..." sounds uncertain. State your range with confidence
• Ignoring total compensation: A lower base with strong equity, bonus, and benefits can exceed a higher base-only offer
• Failing to confirm budget alignment: Always ask if your range fits their budget. It's faster to walk away early than waste weeks on a mismatch

After You've Stated Your Range: Next Steps

Once you've shared your salary expectations, follow these steps to maintain momentum:

1. Confirm Mutual Fit

Immediately after stating your range, ask: "Does that align with what you've budgeted for this role?" This surfaces any major gaps before you invest more time.

2. Shift Back to Value

Don't let salary dominate the conversation. After alignment, return to discussing your qualifications: "Great. Now, I'd love to hear more about the technical challenges your team is facing and how this role would tackle them."

Strong answers to questions like "Tell me about yourself" and "Why should we hire you?" build value that justifies your salary ask.

3. Document Everything

After the conversation, send a brief thank-you email that confirms key points—including any salary discussion. This creates a paper trail and demonstrates professionalism.

4. Prepare for the Offer

If they've confirmed your range fits, start preparing your negotiation strategy. Know your walk-away number, your target, and which benefits matter most (remote flexibility, learning budget, equity vesting schedule).

Special Considerations for US vs. Canada Markets

While the core strategy remains the same, there are regional nuances:

When researching salary data, always filter by country and city. A DevOps Engineer in San Francisco and one in Toronto have different market rates, cost of living, and total comp structures.

What If They Won't Share Their Budget First?

Some employers deflect when you ask about their range. If that happens:

Option 1 – Reframe as collaboration: "I completely understand. To make sure we're on the same page, I typically look at roles like this in the $X to $Y range based on market data. If that's within the ballpark you're considering, I'd love to continue the conversation and dive deeper into the role."

Option 2 – Offer a wider range tied to scope: "Without knowing the full details—team size, tech stack complexity, leadership responsibilities—I'd estimate somewhere between $95,000 and $130,000 for mid-to-senior level roles in this space. Does that help narrow things down?"

Final Checklist: Before Your Next Salary Conversation

1. Research three sources for salary data in your specific city and role
2. Calculate your range: Bottom = your realistic target; top = bottom + $20K
3. Prepare your script for early-stage deflection and later-stage specificity
4. Know your walk-away number (the absolute minimum you'd accept)
5. List your compensation priorities beyond base salary (remote work, PTO, equity, learning budget)
6. Practice out loud—saying salary numbers confidently takes rehearsal

The salary expectations question isn't a trap—it's an opportunity to demonstrate market awareness, professionalism, and confidence. With preparation and the right framework, you'll navigate this conversation in a way that protects your value and sets up a strong offer.

If you're preparing for the full interview process, make sure you're also ready for demonstrating executive presence and handling other high-stakes questions with the same level of preparation. The salary conversation is just one piece—but it's the piece that directly impacts your earning potential for years to come.