How to Answer “What Are Your Salary Expectations?” Without Underselling Yourself

The Biggest Mistake: Treating Salary as a Guessing Game

Candidates often approach salary conversations like this:

“What number will make them happy?”

That's backwards.

Your goal isn't to guess the number the interviewer wants to hear.

Your goal is to understand the value range of the opportunity and position yourself appropriately within it.

Think about three variables:

The Market

What does someone with your skills, experience, location, and level typically earn?

The Role

What is this particular company asking the person to own?

Your Value

What evidence do you have that you can perform at that level?

Your salary expectation sits at the intersection of all three.

That's why:

Market + Role + Evidence = Stronger Salary Position

Not:

Previous salary + random internet number = expected salary

The Salary Positioning Framework™

Before giving a number, understand four things:

Scope → Market → Value → Range

This is the framework you can use before almost any salary conversation.

1. Scope: What Are You Actually Being Asked to Own?

Two people can have the same job title and completely different jobs.

Consider two companies hiring a:

“Product Manager.”

Company A wants someone to:

• maintain the backlog,
• coordinate with engineering,
• write requirements,
• support existing products.

Company B wants someone to:

• own product strategy,
• define a new product,
• manage senior stakeholders,
• influence pricing,
• drive growth,
• manage a team.

Same title.

Very different scope.

And therefore potentially very different compensation.

So before thinking about salary, ask:

“What is the actual scope of this role?”

Look beyond the title.

Look at:

• decision-making authority,
• team size,
• budget,
• revenue responsibility,
• customer exposure,
• complexity,
• strategic responsibility,
• leadership expectations.

The bigger the responsibility, the more carefully you should think about where you position yourself.

2. Market: What Does the Market Pay for This Capability?

The second mistake candidates make is looking only at their current salary.

Your current salary is historical information.

It isn't necessarily the market value of your next role.

You might have been underpaid.

You might be changing industries.

You might be moving into a higher-responsibility role.

You might have developed significantly since your last compensation review.

So the question isn't:

“What percentage increase should I ask for?”

The better question is:

“What does the market pay for the capability and scope this role requires?”

Research compensation based on:

• role,
• seniority,
• location,
• industry,
• company size,
• experience,
• specialist skills,
• management responsibility.

You want a range, not a single number.

Because compensation isn't perfectly precise.

3. Value: Why Are You Worth That Range?

This is where your interview preparation becomes incredibly important.

You shouldn't justify compensation by saying:

“I believe I'm worth ₹X.”

That's a conclusion.

You need evidence.

What have you done that demonstrates your ability to operate at the level you're asking to be paid for?

For example:

Weak:

“I have strong leadership skills.”

Stronger:

“I led a team of eight through a restructuring that reduced project delays by 30%.”

Weak:

“I'm experienced in growth.”

Stronger:

“I redesigned our acquisition funnel and increased qualified leads by 42% over two quarters.”

The salary conversation becomes easier when your interview has already established your value.

This creates an important principle:

Your compensation conversation starts long before someone asks about compensation.

4. Range: Don't Pretend There's One Perfect Number

Candidates often obsess over finding the exact number.

But compensation is usually a range.

Suppose your research suggests that a role could reasonably fall somewhere between:

₹18–24 lakh

Your objective isn't necessarily to say:

“₹21,37,000.”

That's false precision.

Instead, you might position yourself around the relevant range based on the scope and your experience.

For example:

“Based on the scope of the role and what I've seen for similar positions, I'd be targeting something in the ₹21–24 lakh range, although I'd also want to understand the overall compensation structure and expectations of the role.”

That answer does several things.

It:

• gives a real answer,
• demonstrates preparation,
• establishes a range,
• leaves room for discussion,
• avoids sounding rigid.

Should You Give a Number First?

This is one of the most common salary questions.

“Should I tell them my expected salary or make them give the number first?”

There isn't one universal answer.

If you have very little information about the role, you may want to understand the compensation structure and scope before committing to a number.

For example:

“I'd love to understand the full scope of the role and the overall compensation structure before giving a precise expectation. Could you share the range budgeted for the position?”

That's completely reasonable.

But don't turn this into an endless game of refusing to answer.

If the interviewer asks again, be prepared.

You can say:

“Based on what I understand about the role so far and the market for similar positions, I'd be targeting around X to Y, depending on the overall package and scope.”

That's much stronger than:

“I'm flexible.”

Why “I'm Flexible” Is Usually a Weak Answer

Candidates think flexibility makes them attractive.

Sometimes it does the opposite.

Imagine two candidates.

Candidate A

“I'm flexible and open to whatever you think is fair.”

Candidate B

“Based on the scope of the role and comparable positions, I'm targeting ₹20–23 lakh, although I'm open to discussing the overall package.”

Which candidate sounds more prepared?

Candidate B.

Flexibility isn't the problem.

Unanchored flexibility is.

You can be flexible while still knowing your market.

The Difference Between Flexibility and Uncertainty

This distinction matters.

Uncertainty sounds like:

“I don't really know.”

Flexibility sounds like:

“I have a range in mind, but I'm open to discussing the complete package.”

One communicates uncertainty.

The other communicates judgment.

And judgment is exactly what you want your interview to communicate.

This reflects the same communication shift explored in Stop Talking Like a Candidate. Start Talking Like a Colleague.

What If They Ask for Your Current Salary?

This can feel even more uncomfortable.

The interviewer may ask:

“What are you currently making?”

But your current compensation doesn't necessarily determine your market value.

A better approach, where appropriate, is to redirect toward the role.

For example:

“My current compensation reflects my current role and scope. For this opportunity, I'd prefer to focus on the responsibilities and market range for the position. Based on what we've discussed, I'm targeting X–Y.”

The goal isn't to become evasive.

It's to prevent your current salary from becoming the only anchor for the new role.

The Anchoring Problem

Here's why the first number matters.

If someone says:

“We're thinking ₹15 lakh.”

Your brain now evaluates everything around ₹15 lakh.

Even if you originally thought ₹20 lakh was reasonable.

That's anchoring.

The same thing happens in reverse.

If you say:

“I'd expect ₹25 lakh.”

You may establish a strong anchor — but if the role is actually budgeted around ₹18–20 lakh, you may create unnecessary friction.

That's why your number should be:

defensible, researched, and connected to the role.

Not aggressive for the sake of being aggressive.

Don't Just Negotiate the Number

One of the biggest salary mistakes is treating compensation as a single number.

It isn't.

Your total compensation might include:

• base salary,
• bonus,
• equity,
• commission,
• joining bonus,
• retention bonus,
• benefits,
• insurance,
• retirement contributions,
• paid leave,
• flexible work,
• relocation support,
• professional development.

Two offers with the same base salary can have very different total values.

So ask:

“What does the overall compensation package look like?”

This is particularly important for senior roles and startups.

The Total Compensation Lens™

Think about compensation in four layers:

Cash

Base salary + variable compensation.

Ownership

Equity, stock options, or long-term incentives.

Benefits

Insurance, retirement contributions, leave, allowances, etc.

Career Value

Learning, responsibility, brand, network, exposure, and future opportunity.

The fourth category is easy to ignore.

But it matters.

A role that gives you significantly more responsibility, better learning, stronger leadership exposure, or access to a valuable domain may have career value beyond the immediate paycheck.

That doesn't mean you should accept an unfair salary because “the opportunity is great.”

It means you should evaluate the whole opportunity.

What If You Are Changing Careers?

This is where salary conversations become especially difficult.

Suppose you're moving from:

Marketing → Product Management

Your previous salary may not map neatly to the new role.

So don't frame your value entirely around what you used to earn.

Instead, emphasize transferable capabilities.

For example:

“My previous role was in marketing, but a significant part of my work involved customer research, experimentation, analytics, and cross-functional product decisions. I'm now looking for a product role where those capabilities are central.”

Now the conversation is about what you bring to the new role.

Not just where you came from.

What If You're Early in Your Career?

Early-career candidates often make the opposite mistake.

They assume:

“I don't have enough experience to negotiate.”

You don't need ten years of experience to have a market position.

You can still research:

• comparable roles,
• location,
• industry,
• skill requirements,
• internship or graduate-market compensation,
• company size.

And you can still demonstrate value.

For example:

“Based on the role, market range, and the technical and analytical experience I've built through my internships and projects, I'd be targeting X–Y.”

You're not pretending to be senior.

You're demonstrating that you've done your homework.

What If You Are Changing Companies for a Bigger Role?

This is another common situation.

Suppose you're currently:

Senior Analyst

and interviewing for:

Analytics Manager.

If you only negotiate based on your current salary, you're allowing your previous scope to determine the value of your new scope.

Instead, evaluate:

• team responsibility,
• decision authority,
• stakeholder exposure,
• strategic expectations,
• management responsibility.

Your new compensation should reflect the new job, not simply your old job plus a percentage.

Never Use “I Need More Money” as Your Main Argument

Your personal financial needs are real.

But they aren't usually the strongest negotiation argument.

Avoid:

• “My rent has gone up.”
• “I need a 30% increase.”
• “I have family responsibilities.”

Those may explain why you want more money.

They don't explain why the company should pay more.

Instead, connect compensation to:

• scope,
• market,
• capability,
• experience,
• outcomes,
• responsibility.

That is a professional compensation argument.

The Strong Salary Answer Formula

When you're asked:

“What are your salary expectations?”

A strong response can follow this structure:

Context → Range → Reason → Flexibility

For example:

“Based on the scope of the role and the market for similar positions, I'm targeting a range of ₹20–24 lakh. That reflects my experience in leading cross-functional projects and the level of responsibility we've discussed. I'm open to discussing the overall package depending on the role's scope and compensation structure.”

Notice what's missing.

There's no apology.

No nervous explanation.

No:

“I don't know if that's reasonable…”

No:

“But I'm flexible…”

No:

“I'm not really sure…”

It's simply a professional position.

The same principle applies when answering Why You Keep Giving Good Interview Answers but Still Don’t Get the Job: make the evidence behind your position clear.

What If You Have No Idea What Number to Give?

Then don't invent one.

Instead, buy yourself context.

You can say:

“I'd like to understand the scope and expectations of the role a little better before giving a precise number. Could you share the range you've budgeted for the position?”

Or:

“I'm still calibrating based on the role and the overall package. What range has the company established for this position?”

This is especially useful early in the process.

What If They Say, “We Need a Number”?

Give one.

Don't keep dodging.

Use your research.

For example:

“Based on similar roles and the scope we've discussed, I'd be targeting around ₹22–24 lakh, depending on the overall package.”

You don't have to defend every rupee.

You just need to be able to explain your thinking.

What If They Say Your Number Is Too High?

Don't panic.

This is not necessarily rejection.

It may simply mean there is a gap.

Ask:

“Could you tell me a little more about the range you're working with?”

Then understand the difference.

If they say:

“Our budget is ₹18–20 lakh.”

You now have information.

You can decide whether the role is still worth pursuing.

You might respond:

“Thanks for sharing that. That's below the range I had in mind, but I'm still very interested in the role. I'd be happy to understand the complete package and scope before deciding whether we're aligned.”

That's negotiation.

Not confrontation.

What If They Say Your Number Is Too Low?

It happens.

And it reveals something important.

You may have under-researched the market.

Don't immediately lock yourself into the lower number simply because you said it.

You can clarify:

“As I've learned more about the scope of the role, I think the position carries more responsibility than I initially understood. I'd like to revisit the compensation discussion based on that broader scope.”

The lesson:

Don't rush to give a number before you understand the job.

The Interviewer Is Also Selling You the Job

Candidates sometimes forget this.

An interview isn't simply:

Company evaluates candidate.

It's:

Candidate evaluates company + company evaluates candidate.

That becomes increasingly important as you become more senior.

The company needs to convince you that:

• the role is meaningful,
• the scope is appropriate,
• the team is strong,
• the leadership is credible,
• the compensation is fair,
• the opportunity is worth taking.

So asking about compensation isn't inherently uncomfortable.

It's part of evaluating whether the two sides are aligned.

That two-way evaluation is why The Interview Isn’t a Test. It’s a Simulation of How You’ll Work.

Salary Negotiation Is Not a Fight

This mindset is important.

You don't need to “win” the negotiation.

You need to find alignment.

The best outcome is not:

“I extracted the maximum possible salary.”

It's:

“Both sides believe the compensation fairly reflects the role and the value being exchanged.”

That mindset changes how you communicate.

You become curious rather than defensive.

You ask questions.

You understand constraints.

You explain your position.

You look for trade-offs.

That's much closer to how strong professionals actually negotiate.

The Salary Conversation Rep™

And this is where interview preparation becomes practice rather than information.

Don't just read five articles about salary negotiation.

Practice saying the number.

Out loud.

Because knowing:

“I should ask for ₹22–24 lakh”

is completely different from calmly saying:

“Based on the scope of the role and market benchmarks, I'm targeting ₹22–24 lakh.”

The second is a performance skill.

And performance skills require reps.

Try this:

Rep 1 — Say your number

Give your range without explaining it.

Rep 2 — Defend it

Explain why the range makes sense.

Rep 3 — Handle pushback

Practice:

“That's above our budget.”

Rep 4 — Handle a low offer

Practice:

“We're offering ₹18 lakh.”

Rep 5 — Negotiate the whole package

Practice discussing:

• base,
• bonus,
• equity,
• benefits,
• title,
• scope.

You don't need a two-hour mock negotiation.

You need repeated exposure to the uncomfortable moment.

Because the goal isn't to memorize the perfect salary answer.

The goal is to become comfortable having the conversation.

Strong answers become natural through evidence-rich practice, which is also why The Best Candidates Don’t Have Better Answers. They Have Better Stories.

The Bigger Lesson About Career Value

Salary conversations reveal something deeper about careers.

Your value isn't a fixed number.

It changes as your:

• capabilities grow,
• responsibilities increase,
• judgment improves,
• track record compounds,
• network expands,
• market demand changes.

That's why career growth shouldn't only mean collecting titles.

It should mean becoming capable of handling increasingly valuable problems.

The more valuable the problems you can reliably solve, the stronger your position becomes.

That's the real career compounding effect.

Don't Ask “What Should I Ask For?” Ask Better Questions.

Instead of asking:

“What salary should I ask for?”

Ask:

• What is this role worth in the market?
• What is the actual scope?
• What capabilities does it require?
• What evidence do I have?
• What does the total package look like?
• What trade-offs am I willing to make?
• What number would make this opportunity genuinely worthwhile?

Those questions produce a much better answer.

Clear positioning also depends on knowing What Recruiters Notice in the First 90 Seconds of Reading Your Resume.

A Simple Salary Preparation Checklist

Before your next interview, write down:

1. My market range:

What do comparable roles pay?

2. My target:

What number or range would I ideally like?

3. My floor:

At what point would accepting the role no longer make sense?

4. My evidence:

What results justify my position?

5. The role's scope:

What am I actually being asked to own?

6. The total package:

What else matters besides base salary?

7. My response:

Can I say my expectation confidently in one or two sentences?

If you can answer all seven, you're much less likely to get caught off guard.

The Best Salary Answer Doesn't Sound Like a Negotiation

Ironically, the strongest salary answers often sound very ordinary.

Something like:

“Based on the scope of the role, my experience, and the market for similar positions, I'd be targeting around ₹22–25 lakh. I'm open to discussing the overall package and understanding how you structure compensation for the role.”

That's it.

No speech.

No defensive justification.

No aggressive negotiation tactics.

Just:

• Research.
• Positioning.
• Evidence.
• Flexibility.

Key Takeaways

If you remember only a few things:

• Don't guess your salary expectation. Research the market and understand the role.
• Your previous salary isn't automatically your future market value.
• Understand scope before choosing a number. Titles alone don't tell you what a role is worth.
• Use a range rather than false precision.
• Don't confuse flexibility with uncertainty.
• Think about total compensation, not only base salary.
• Connect your expectation to evidence and responsibility, not personal financial needs.
• If you don't know the range, ask. That's better than inventing a number.
• Practice saying your number out loud. Confidence in compensation conversations is a skill.
• Salary negotiation isn't a battle. It's a process of finding alignment between value, scope, market, and expectations.

The biggest mindset shift is this:

You're not asking the interviewer to decide what you're worth.

You're entering a conversation about what the role is worth, what you bring to it, and whether the two sides can agree on the exchange.

That's a very different conversation.

And it starts with being prepared to have it.

Your Next Rep

Knowing what to say is one thing.

Being able to say it calmly when someone is sitting across from you is another.

Take the salary range you've researched.

Say it out loud.

Then imagine the interviewer responds:

“That's above our budget.”

What do you say next?

That's the rep.

Start your first AI Interview Rep →

For deeper interview preparation: Explore Uinspyr Interview Prep →

Related Uinspyr Articles

Why You Keep Giving Good Interview Answers but Still Don’t Get the Job

The Interview Question You Should Never Answer in One Sentence

Why Interviewers Ask “Why Should We Hire You?” — And What They’re Actually Trying to Find Out

Stop Talking Like a Candidate. Start Talking Like a Colleague.

The Interview Isn’t a Test. It’s a Simulation of How You’ll Work.

The Best Candidates Don’t Have Better Answers. They Have Better Stories.

What Recruiters Notice in the First 90 Seconds of Reading Your Resume