← All posts

29 May 2026 · Rehurz

Discussing Salary Expectations Professionally in Interviews

You are three weeks into a job search. The interview is going well. The hiring manager smiles and asks, "What are your salary expectations?" Your throat tightens. You pause too long. You either blurt out a number you immediately regret, or you fumble a vague deflection that sounds evasive.

Discussing salary expectations in an interview is a moment of truth that many candidates dread. But it does not have to be uncomfortable. The key is knowing when the question is likely to come up, how to research the market beforehand, and how to respond with confidence whether you are deflecting early or anchoring your number later.

Quick answer: Prepare a market-researched salary range before any interview (use public salary databases, industry reports, and location-adjusted benchmarks). When asked early in the process, deflect tactfully ("I am focused on the role fit first, but I have done my homework on market rates"). When you must give a number, provide a range tied to your value, never undervalue your work, and be ready to justify your expectations with experience and impact. Never disclose your current salary unless you are in a jurisdiction that already requires it.

Let us walk through how to navigate this conversation with poise, preparation, and strategy.

When Salary Discussions Happen

Salary expectations questions do not appear randomly. They come up at predictable moments in the hiring process, and understanding when helps you prepare.

Early in the funnel: Some recruiters ask during the initial phone screen or before a formal interview loop begins. This is a filtering step, not a negotiation. Their goal is to check if your expectations align with the budget before they invest time in interviews. Deflecting here is expected and usually welcome.

During the final interview rounds: After the company has invested in getting to know you, senior hiring managers or the hiring lead sometimes ask. This is closer to actual negotiation territory. You are less anonymous now, so your answer carries more weight.

After you receive an offer: This is the formal negotiation phase. The offer letter typically includes a base salary figure. At this point you respond with your counter-number, supported by your research and the value you bring.

During salary review discussions: Once hired, annual reviews may trigger a salary expectations question. That is a separate conversation, but the same principles apply: research, justification, and confidence.

The tone and timing matter. A casual "What did you have in mind?" in a phone call is different from a formal HR form asking you to fill in a number. Recognize the signal. Casual and early usually means deflect. Formal and late usually means you need a thoughtful answer.

Research the Market First

Before you walk into any interview, you need to know what the role is worth. Guessing is a losing strategy.

Use multiple data sources. No single source is perfect. Public salary databases like Glassdoor, Levels.fyi, PayScale, and Blind offer user-reported data. Professional associations and industry surveys publish annual reports. LinkedIn Salary (available in some regions) shows ranges by role and location. If you are in India, platforms like AmbitionBox and Internshala aggregate salaries and include Total Cost to Company (CTC), which includes benefits and bonuses.

Adjust for location, seniority, and company stage. A senior full-stack engineer in San Francisco earns differently from the same role in a Tier-2 Indian city. A startup pays differently from a Fortune 500 company. The same role at a Series A startup versus a public company yields different ranges. Always cross-reference your base role with the specific geography and company profile.

Look at the role, not the title. "Senior Engineer" at one company may map to "Staff Engineer" at another. Search by responsibilities and scope, not just the job title. Does the role include mentoring? System design decisions? Cross-team influence? These raise the band.

Collect 3-5 data points. Aim for at least three to five independently sourced salary ranges for a role you are targeting. This gives you a defensible middle band. If your sources cluster around 80k to 100k and one outlier says 150k, you know to discount the outlier.

Consider the full package. Salary is one component. Include stock options (if a startup), signing bonus, relocation assistance, health insurance, retirement contributions (401k, EPF), paid leave, and professional development budget in your mental math. A lower base with strong equity may outpace a higher base alone.

By the time you sit down for an interview, you should have a clear, confident range in mind. That confidence comes from homework, not hope.

The Deflect-and-Defer Tactic

When a recruiter or early-stage interviewer asks your salary expectations, you have a choice. You can answer directly, or you can deflect gracefully. Most career coaches recommend deflecting if asked early, because:

  1. The company has not yet proven the value of the role to you.
  2. You have not yet proven your value to them.
  3. Anchoring too early locks you in, or sounds like you are price-shopping.
  4. You do not yet know the full scope, team, and growth opportunities.

Here is a tactful deflect script:

"I appreciate the question. I am really focused on finding the right role fit and a team where I can make an impact. I have researched market rates for this role in this location and at this company stage, and I have a range in mind, but I would love to learn more about the scope of the role, the team, and the company roadmap first. Then we can have a more informed conversation."

This does three things: it acknowledges the question politely, it signals that you have done your homework (no wild asks), and it reframes the priority as fit, not just money. Most hiring managers respect this answer. A few will press. If they do:

"I am happy to share a range, but I want to make sure I understand the full picture first. What does a typical day in this role look like? What are the biggest challenges the team is facing right now?"

This buys you time and information. Do not be defensive. Keep your tone collaborative.

When You Must Anchor: The Number Talk

If deflecting is not working, or if you are in a later-stage conversation, you need to give a number. Here is how to do it with confidence and flexibility.

Give a range, never a single number. A range is more defensible and gives both sides room to negotiate. "I am looking at 90k to 110k based on my research and experience" is stronger than "I want 100k." A range signals that you are reasonable and understand the market.

The range should be 10-15 percent wide. This shows you have thought it through. Too narrow (e.g. 100k to 101k) looks arbitrary or rigid. Too wide (e.g. 80k to 150k) looks like you have no idea.

Lead with your value, not the number. Before you state the range, briefly anchor it to your experience:

"Based on my research of market rates for this role in [location], combined with my [X] years of experience in [domain], and the fact that I have [key achievement], I am looking at a range of 90k to 110k."

This is stronger than just blurting out the range. You are attaching it to your credentials.

If they push back low, do not capitulate immediately. If they say, "That is higher than our budget," you have options:

  1. Ask questions: "What is the budget range you were thinking?" (This may reveal their actual top end, which is often higher than their opening offer.)
  2. Pivot to the full package: "I am open to negotiating the base if there is significant equity, signing bonus, or professional development budget."
  3. Buy time: "I appreciate you sharing that. Let me think about it, and we can reconnect tomorrow."

Never drop your number by half on the first ask. Negotiate in increments. A 5-10 percent reduction is reasonable. Anything more suggests you came in overconfident or the role is not worth your time.

If they push back high, stay calm. Some companies will offer more than you asked if they love you. Do not panic or counter-offer down. Take the offer. But do ask:

  1. "I am thrilled. Just to clarify, is this the final offer or is there flexibility in the package?" (Sometimes they leave negotiation room on equity or benefits.)
  2. "When is the expected start date, and are there any signing or relocation bonuses?" (You might unlock more value.)

Handling "What is Your Current Salary?"

This question is increasingly restricted by law in many regions (parts of the US, UK, and Australia now ban it), but it still comes up, especially in India, where salary history is part of the hiring norm.

If you are in a region that allows the question: You have a choice. You can answer honestly, deflect, or ask why it matters. A straightforward deflect:

"I do not think my current salary is a good benchmark for this role, given the differences in scope, location, and company stage. I am happy to base my expectations on current market rates for this position."

If you are underpaid in your current role: Answering truthfully can anchor the company to your low number. If you are confident your current salary is below market, say:

"My current salary is [X], but I am aware that is below market for my experience level. Based on market research, I am targeting [range]."

This signals that you know your worth and are not trying to hide anything, but you are not settling for a raise from your current low base.

If you are in India and CTC is the norm: CTC (Cost to Company) includes base, bonus, gratuity, and benefits. When discussing salary in India, be clear about what you mean. "My current CTC is 18 lakhs, of which 12 lakhs is base" helps the company understand the actual cash number versus the full package.

Never lie about your current salary. It can disqualify you or come back to haunt you during background checks. Instead, frame the conversation on market value, not history.

What NOT to Do

A few common pitfalls will hurt you:

Do not guess or lowball yourself. If you do not know the market range, do your research before the interview. Guessing low locks you in and leaves money on the table. Confidence attracts better offers.

Do not confuse your personal needs with market value. Your financial situation is personal. "I need 100k to pay my student loans" is not a market argument. "Market research shows this role is worth 100k in this location" is. Stick to the latter.

Do not negotiate salary alone if equity or benefits are on the table. A lower base with strong stock options may be better than a high base with no upside. Ask to see the full offer before you decide.

Do not accept the first offer if it is significantly below your research. You are leaving money on the table. Politely counter or ask for time to think. Companies expect this. Not negotiating signals that either you do not know your worth or you do not care about compensation. Both are bad signals.

Do not be aggressive or combative. Negotiation is not a fight. Stay professional, data-driven, and collaborative. "I understand your budget constraints. Here is my counter-offer with my reasoning" lands better than "That is not enough."

Do not disclose your range first if you can help it. In a back-and-forth, the person who anchors first sometimes locks in a lower outcome. If possible, ask the company "What is your budget for this role?" before you answer. If they press, you answer. But getting their number first gives you negotiation advantage.

Common Scenarios and How to Handle Them

Here is a quick reference for scripts you might use in common situations:

Scenario 1: Early recruiter call
Recruiter: "What are your salary expectations?"
You:       "I am interested in the role. I have researched the
           market rate, and I have a range in mind, but I would
           like to learn more about the scope first. Can you walk
           me through the team and the key responsibilities?"

Scenario 2: Direct question late in process
Hiring Manager: "We would like to move forward. What would you need?"
You:           "I am excited about this. Based on my research, my
               experience in [domain], and the scope we discussed,
               I am looking at 95k to 110k. Is that in the ballpark
               for the budget?"

Scenario 3: They ask your current salary
Recruiter: "What are you making now?"
You:       "My current salary is X, but I do not think it is a good
           benchmark for this role. My research shows this position
           is worth Y to Z in this market. That is my target."

Scenario 4: Your number is too high for their budget
Hiring Manager: "That is above what we were thinking. We were
               at 80k."
You:           "I appreciate you sharing that. I understand budget
               constraints. Let me ask: is the 80k fixed, or is there
               flexibility if we look at the full package? What about
               equity, bonus, or professional development budget?"

These are templates, not scripts to memorize. Adapt them to your voice and the conversation. Authenticity matters. But the structure (acknowledge, justify, ask or counter) works across situations.

Frequently Asked Questions

Q: Should I research the specific company's salary levels? Yes, but with caveats. Sites like Glassdoor show reported salaries for specific companies. These are crowd-sourced and may be outdated or skewed, but they give directional data. Use them alongside broad industry benchmarks, not in place of them.

Q: What if I have been out of work or changed careers? Market rate for the role applies to you as much as anyone else. If you are transitioning into tech from another field, research the role in your target field, not your previous field. Your justification shifts: "I am new to the role but have [adjacent skills], and market data shows this role is worth..."

Q: Is it okay to ask for a sign-on bonus instead of higher base? Absolutely. If the company cannot budge on base, ask about equity (for startups), sign-on bonus (common for senior roles), or accelerated vesting schedules. These add real value and show you understand total compensation.

Q: What if the company says "We do not negotiate salary"? Some companies have fixed bands per level. Even then, you can ask about the band or request a promotion timeline. But if they truly do not negotiate, you decide: is the fixed offer acceptable? If not, walk. Do not accept an offer you resent.

Q: How do I handle multiple offers and negotiate them against each other? Ethically? Tell both companies you are in process with others and ask for exploding offer deadlines or time to decide. Do not lie. You can use one offer to legitimately negotiate with another: "I have another offer at X. Can you match or exceed that?" Be prepared to turn down the lower one if they cannot. This is not dirty; it is market negotiation.

Q: Should I ask for a salary review after 6 months? That is a conversation for after you are hired. Include it in your offer acceptance or first 1-on-1: "I am excited to join. I would like to align on expectations for growth and compensation reviews as I settle in." This sets the precedent but does not re-negotiate your starting offer.

Practising This with Rehurz

Salary discussions are behavioural questions with real stakes. You need to practice not just the content of your answer, but how you deliver it under pressure and follow-up questions. When a real hiring manager probes ("But is there flexibility?" "That seems high, why?"), you need to stay anchored and articulate, not defensive or scrambling.

Rehurz lets you conduct a voice-based practice interview covering behavioural topics like salary negotiation. You can work through a realistic salary discussion with an AI interviewer who will follow up with genuine objections and pressure. The platform gives you feedback on how well you justified your number, handled deflection, and negotiated under questioning, plus ideal answers to compare against. This kind of rehearsal under realistic pressure is how you move from knowing the theory to owning the conversation.

Start your free interview and practise talking through salary expectations with a skilled interviewer who will keep you honest. Or explore how Rehurz interview prep works to build your confidence in high-stakes conversations.

Final Thoughts

Salary expectations discussions are negotiations, not ambushes. They happen at predictable moments, follow a logic, and respond to preparation and composure. By researching the market beforehand, understanding when and how to deflect, and anchoring confidently when you must give a number, you move from anxiety to advantage.

You walk into the interview knowing your worth. When the manager asks, you answer with data, not desperation. That clarity and confidence is what lands you both a better offer and the respect of the hiring team.