An opening, nothing more. Answer it like one.

How to Respond to a Lowball Offer

Respond to a lowball offer in three moves: stay warm, make them explain the number, then re-anchor against the market. "I'm excited about the role. Help me understand how you arrived at $52K for this scope - the market for it runs $58-65K, so I want to make sure I'm not missing something." No offense taken, no offense given - and the burden of defending the number is now theirs.

What you never do is the two reflexes the lowball is designed to trigger: accepting fast because you're afraid the offer vanishes, or bristling because it reads as disrespect. A lowball is an opening position that cost them nothing to send. Treat it as information: they expect a negotiation.

The situation

First, confirm it's actually a lowball and not a market correction. Check the scope against real comps - posted bands for comparable roles, salary data for the level, what the work is getting elsewhere. If the offer sits well under that picture, you have a lowball; if your expectation was built on a different market than the one you're in, you have homework instead. Don't run the playbook until you know which conversation you're having.

Once you know, the sequencing matters. Warmth first, because the company has already decided they want you and your goal is to keep that decision intact while the number moves. The explanation ask second, because "how did you arrive at it?" forces them to defend the figure - and a defended lowball usually exposes its own softness ("well, the band technically starts at…"). The re-anchor third, sourced and specific, so the conversation now happens between the market and their open, not below it.

Say this

READING THE GAP

Sourced comps decide it - feelings and framing don't

Price the scope against posted bands and market data for the level. If the offer sits clearly below that picture, negotiate the gap with the source in hand; if it doesn't, you're looking at a market correction, and that's a different conversation.

How it sounds

First job offer. The hiring manager just delivered a number well under everything your research says.

ThemWe can offer $52K for the role - that's where we typically land for new grads.
YouI appreciate it, and I'm interested. Help me understand how $52K was set - the postings I'm seeing for this scope run $58 to $65K.

Why this works: Warmth plus the explanation ask plus the sourced range, in one breath. The hiring manager now has to defend 'typically' against the market - and 'typically' tends to fold into 'well, for the right candidate…'.

They hold the line on the first pushback.

ThemI hear you, but that's the budget we have for this position.
YouIt sounds like the budget's set at the team level. If base is locked, what does the path look like - sign-on, the six-month review, the title?

Why this works: Labeling the constraint keeps it warm; pivoting to levers the budget doesn't govern keeps it moving. A real lowball almost always has give somewhere other than base.

What not to say

Don't reveal your floor or your previous salary as the response - "I was making $58K, so this is a step down" anchors the negotiation to your history instead of the market, and in a growing list of places (including much of the US) employers can't even ask for that history. Argue scope and market, never biography.

And don't perform the insult. "This is frankly disrespectful" might feel righteous, but it converts a number problem into a relationship problem, and relationship problems don't get bridged by sign-on bonuses. If the offer signals how the company values the role - and sometimes it does - the move is to walk calmly, not to win an argument first.

Try it against someone who pushes back

Practice against a hiring manager who opens low on purpose

Free scenario · sign up in under a minute · she's run this offer a hundred times

Common mistakes

Questions people ask

Is a lowball offer a sign I shouldn't take the job?

Not by itself - plenty of good employers anchor low because it works on most candidates. The real signals are what happens when you push back professionally: a company that engages with the market data is negotiating; one that gets defensive or punitive about a polite counter is showing you how raises will go for the next five years.

Should I tell them my previous salary?

No. It anchors the negotiation to your history instead of the role's market, and salary-history questions are restricted or banned in many jurisdictions. If asked, redirect: 'I'd rather anchor on the scope of this role - the market for it runs $X to $Y.'

What if I already said a low number earlier in the process?

Update it with new information, openly: 'When we first spoke I said $X - having now seen the full scope of the role, the market for this work runs $Y, and that's where I am.' Scope changes are a legitimate, face-saving reason to move your own anchor.

How do I counter a lowball without a competing offer?

The market is your competing offer - sourced comps for the scope do the same work a rival bid does, without the bluff risk. A specific, defensible number tied to real data moves lowballs every day. Phantom competing offers, meanwhile, are the fastest way to lose the deal and your credibility together.

Practice the real thing

The techniques this uses

Drill it until it's a reflex

Practice against a hiring manager who opens low on purpose

Free scenario · sign up in under a minute · she's run this offer a hundred times