Picture the whole sequence, start to finish: a long parade of interviews, hours of cognitive testing, weeks of scheduling gymnastics — and then, at the very end, an offer that comes in below what the candidate currently makes. Not level. Below. After all that time and effort.
Reactions to that kind of story split between “take it, the market's brutal” and “run.” Both reactions skip the most useful question: why does this keep happening at the end of long processes specifically? Because once you see the mechanism, the response writes itself.
The lowball is not an accident
Here's the position, stated plainly: an offer that lands under your current salary after a marathon process is rarely a budgeting error. It's a posture. The company has watched you invest evening after evening into their process. They're betting that all that sunk effort — plus the general fear in the market — means you'll swallow a number you'd have laughed at on day one. The length of the process isn't incidental to the lowball. The length of the process is what funds the lowball.
Sometimes it really is incompetence — a hiring manager and a finance team who never agreed on the band, and nobody checked until offer stage. It happens. But you can't tell the two apart from the outside, and conveniently, the correct response is the same for both.
First move: make them say it out loud
Do not open with anger, and do not open with a counter. Open with a question that forces them to own the number:
I want to make sure I'm reading this right — the offer is below my current package. Was that intentional, or is there a mismatch somewhere?
Flat tone. Genuine curiosity, or a good impression of it. This question is quietly brutal because there's no comfortable answer. If it was intentional, they now have to defend paying you less to switch jobs — a position that sounds absurd the moment it's spoken. If it wasn't intentional, you've just given them a graceful exit: mismatch, the band was stale, let me go back to finance. Either way, the number is now their problem to justify instead of your problem to absorb.
What you'll often hear next is some version of “there's growth potential” or “the total package tells a different story.” Fine — make that concrete too: “Walk me through it. What does the package include that closes the gap, and when?” Vague futures are how gaps stay open. If the growth story is real, it survives being written down.
Countering without a bluff
You don't need to name a magic figure to counter. You need a floor and a reason:
For me to move, the offer needs to clearly beat what I'm on now — switching jobs is a risk, and the risk has to be paid for. Where's the top of the band for this role?
Two things are happening there. You've anchored the logic — moving costs something, so moving must pay something — which is much harder to argue with than any specific figure. And you've asked for the band, which they've had all along and simply chose not to show you. If they won't reveal the band even at offer stage, write that down somewhere in your head. Companies that hide the band at the moment of maximum good faith don't get more transparent after you join.
And never bluff a competing offer that doesn't exist. Not for ethics points — for mechanics. A bluff invites “we understand, good luck with the other role,” and you have no move left. Only fire ammunition you actually have.
The exploding offer
Some lowballs arrive with a fuse: accept by tomorrow, or it's gone. Treat the fuse as data. A company confident in its offer gives you room to think, because thinking makes strong offers look better. Pressure only helps weak offers. Say so, politely: “I don't make career decisions overnight, and I don't think you want employees who do. I can give you an answer by end of week.” If the offer genuinely can't survive a few days of thought, it was never an offer. It was a trap with a salary attached.
If you're lucky enough to hold two
Someone who'd been out of work for months had the opposite problem — nothing, then two offers at once. Champagne problem, still a problem, because the offers never move on the same clock.
- Tell the slower company the truth. “I've got another offer with a deadline. You're the role I'm more excited about — can you compress your timeline?” Companies can move shockingly fast when they believe the scarcity is real, and this costs you nothing because it's true.
- Compare managers and processes, not just salary. Salary is the most visible variable and the least predictive one — you didn't leave your last job over base pay. Which manager talked straight, gave real feedback, told you things that weren't in the pitch? The process is a free sample of the company: the one that ran you through hours of tests and went quiet for weeks — that's not their interview behaviour, that's their behaviour.
- Don't accept one and keep shopping the other after signing. Renege if you truly must — it's survivable — but do it before anyone's turned down their other candidates on your word if you can possibly help it.
Never accept on the call
One more thing about that marathon sequence: the candidate sat through hours of software-scored assessments — the kind worth sorting into “grind” or “walk” before you invest the evenings — and the output of all that measurement was… a lowball. The tests get sold to candidates as objectivity. Then the offer arrives and the objectivity turns out to be negotiable in exactly one direction. What you can control is refusing to let the effort of being measured turn into obligation to accept whatever follows. You don't owe a company a yes because their process was long. The process being long was their choice, and quite possibly their strategy.
Last rule, no exceptions. However good the number sounds in the moment — and especially after a drought, any number sounds like rain — say thank you, say you're excited, and ask for it in writing. Every offer survives a night of sleep. The ones that don't were never real.
Back to all articles