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

Few interview questions carry as much weight—or cause as much anxiety—as "What are your salary expectations?" Answer too high and you might price yourself out; too low and you leave tens of thousands on the table. For tech professionals interviewing in the US and Canada, this question requires research, strategy, and confidence.

This guide walks you through exactly how to research competitive salaries, when to deflect versus when to name a number, and the specific phrases that protect your negotiating position while keeping you in the running.

Why Employers Ask About Salary Expectations

Hiring managers ask this question early for three reasons:

• Budget alignment: They need to confirm you're within their approved compensation range before investing interview time
• Market calibration: Your answer helps them gauge whether their range is competitive
• Negotiation anchor: The first number mentioned often becomes the reference point for all subsequent discussions

Understanding this helps you see the question not as a trap, but as an opportunity to demonstrate market awareness and professionalism. According to U.S. Bureau of Labor Statistics data, software developers who negotiate see salary increases of 5-15% on average compared to those who accept initial offers.

Step 1: Research Your Market Value Thoroughly

Never walk into a salary conversation without data. Your research should cover multiple dimensions specific to tech roles in North America.

Use Multiple Salary Data Sources

Cross-reference at least three of these trusted sources:

• Glassdoor and Levels.fyi: Crowd-sourced tech salary data with company-specific breakdowns
• Payscale and Salary.com: Adjust for experience level, skills, and location
• LinkedIn Salary: Filters by job title, location, and years of experience
• Stack Overflow Developer Survey: Annual compensation data by technology stack
• Government data: U.S. Bureau of Labor Statistics and Statistics Canada for baseline occupational wages

Account for Geographic Differences

Tech salaries vary significantly by region. A senior software engineer in San Francisco commands different compensation than the same role in Austin or Toronto. Key considerations:

Factor in Your Unique Value

Adjust the median based on your specific profile:

• In-demand skills: Cloud certifications (AWS, Azure, GCP), machine learning, cybersecurity expertise typically command 10-20% premiums
• Years of experience: Each year of relevant experience generally adds 3-7% to base salary
• Education: Advanced degrees may add 5-15% depending on role and company
• Track record: Quantifiable achievements (scaled systems, led teams, shipped products) strengthen your positioning

Step 2: Choose Your Response Strategy

You have three main approaches when the salary question comes up. Choose based on timing, your research confidence, and the interview stage.

Strategy A: Deflect Early, Anchor Later

If asked during a first call or screening, deflect politely and refocus on fit. This preserves your negotiating position until you've demonstrated your value.

What to say:

"I'd love to learn more about the full scope of the role and the team I'd be joining before discussing specific numbers. I'm confident that if we're the right fit, we'll find a compensation package that works for both of us. Can you share what range you've budgeted for this position?"

This approach shifts the burden back to the employer while signaling flexibility and professionalism. It works particularly well early in the process when you have limited information about responsibilities and growth potential.

Strategy B: Provide a Data-Backed Range

If pressed or if you're confident in your research, offer a range with the bottom 10-15% above your true minimum. This gives room for negotiation while keeping you in the running.

What to say:

"Based on my research of the market for senior DevOps engineers with cloud architecture experience in the Toronto area, I'm seeing ranges from $110,000 to $135,000 CAD. Given my five years of experience scaling Kubernetes deployments and my AWS certifications, I'd be looking at the $120,000 to $135,000 range, depending on the total compensation package."

Notice how this answer:

• Grounds the number in market research, not personal need
• Highlights specific, valuable skills that justify the range
• Acknowledges total compensation (equity, bonus, benefits) matters
• Gives a range rather than a single number

Strategy C: Turn the Question Around

In many cases, the employer already has a budgeted range. Getting them to share it first gives you the advantage.

What to say:

"I appreciate you asking. I'm sure you have a range in mind for this role. Would you mind sharing that so I can consider it in the context of the full opportunity?"

This works especially well when you've already built rapport. Many recruiters will share their range, especially in jurisdictions like Colorado, New York City, and California where salary transparency laws require disclosure.

Step 3: Navigate Common Salary Conversation Scenarios

When They Share Their Range First

If the employer reveals their budget, you have valuable information. Your response depends on how their range compares to your expectations:

When They Ask About Your Current Salary

Several US states and Canadian provinces have banned salary history questions, but you may still encounter them. You're not obligated to answer, and doing so can anchor you to past—potentially inequitable—compensation.

What to say:

"I'd prefer to focus on the value I can bring to this role rather than what I've earned in the past, since the responsibilities and scope are different. I'm targeting $X to $Y based on the market for this position."

When They Press for a Single Number

Some interviewers push for a specific figure rather than a range. Resist if possible, but if you must give a number, state your ideal target—not your minimum.

What to say:

"If I had to put a single number on it, $125,000 would be ideal, but I'm flexible depending on the total compensation package, growth opportunities, and benefits."

Step 4: Practice Your Delivery

Confidence matters as much as content. Practice these tactics:

1. Say your number without flinching: Practice out loud until you can state "$135,000" with the same ease you'd say "I have five years of experience"
2. Pause after you answer: Don't rush to fill silence. Let the interviewer respond first
3. Avoid apologetic language: Never say "I'm sorry, but..." or "I hope this isn't too much..." when discussing salary
4. Maintain positive body language: Even on video calls, sit up straight and maintain eye contact when discussing compensation

Remember that hiring managers expect candidates to negotiate. According to research from Harvard Business Review, the majority of employers leave room in their initial offer specifically anticipating negotiation.

Step 5: Follow Up Strategically

After the salary conversation, reinforce your value in your thank-you note without rehashing numbers.

Example thank-you note excerpt:

"Thank you for the transparent conversation about compensation. I'm excited about the opportunity to bring my experience scaling cloud infrastructure to your team. The challenges you described around migrating legacy services align perfectly with the work I did at [Previous Company], where we reduced infrastructure costs by 30% while improving reliability."

This keeps the focus on value delivered, not dollars requested. For more on making a strong impression throughout the interview process, see our guide on how to answer "Tell Me About Yourself".

When to Walk Away

Sometimes a salary conversation reveals a mismatch that's too significant to bridge. Consider walking away if:

• The maximum of their range is 20%+ below your minimum, with no flexibility
• They pressure you to accept on the spot without time to evaluate
• The salary comes with red flags (unrealistic expectations, unclear role scope, poor benefits)
• Your research shows the offer is significantly below market for your skills and experience

Remember that landing the right role often takes multiple interviews. A low offer from one company doesn't define your market value.

Key Takeaways

Handling salary expectations questions successfully requires preparation and confidence:

• Research thoroughly using multiple sources and adjust for your location, skills, and experience level
• Deflect early when possible, and try to get the employer to share their range first
• Provide data-backed ranges rather than single numbers, with your floor 10-15% above your true minimum
• Practice your delivery until you can discuss six-figure sums without hesitation
• Remember total compensation includes equity, bonuses, benefits, and growth opportunities—not just base salary

The salary expectations question isn't designed to trip you up. It's a business conversation where both parties are trying to determine fit. With solid research, strategic framing, and confident delivery, you can navigate it successfully and set yourself up for an offer that reflects your true market value.

For more strategies on standing out in competitive tech markets, explore how reverse recruiting can help you access opportunities where compensation conversations happen earlier and more transparently.