I have been collecting counter-offer stories from a small network of mid-to-senior engineers over the last 90 days. Twelve of them ran a real counter-offer cycle in that window: their current employer learned they had an outside offer, presented a counter, and the engineer made a decision.
Of those twelve:
- Four took the counter and stayed (good outcome — money up, role intact).
- Three took the counter and left within 6 months (bad outcome — money up, but the role got worse).
- Five rejected the counter and left for the outside offer (mostly good — clean exit).
This post is the comparison between the four "good counter" outcomes and the eight that didn't go well. The pattern is not the one I expected when I started collecting.
What I expected to find
Conventional wisdom says: never accept a counter-offer. Your manager will mark you as a flight risk. Your peers will find out. Your raise will be smaller than market in two years.
That advice is not wrong. But it is also not the whole story. The four cases where the counter worked all share three structural features that the conventional advice misses.
The four counter-offers that worked
Common features across all four:
1. The counter included a role change, not just a comp bump. Two of the four moved into a new title (one IC track upgrade, one IC-to-tech-lead). One moved to a different team where they had wanted to be. One stayed in the same role but received a published, vested promotion path with milestones. In all four cases, the company gave them something money couldn't buy somewhere else — a specific career step inside this specific company.
2. The conversation was started by the engineer, not by the recruiter pulling them out. All four had brought up wanting more (more money, more responsibility, a different team) before the outside offer existed. The outside offer accelerated the conversation. It did not start it. So when the counter came, it landed inside an existing dialogue, not as a panic reaction.
3. The counter was signed by both sides as a formal raise, not a promise. Title change, base bump, RSU refresh — all in writing, all effective within 30 days. None of "we'll work on this in your next review."
The "stay or leave" decision became easy in those four cases because the counter was structurally different from the original job. The engineer wasn't choosing between "same job + more money" and "new job." They were choosing between "new job here" and "new job there."
The three counter-takers who left within 6 months
Different pattern. All three:
- Took the counter primarily for the comp delta.
- Did not get a role change. Same title, same team, same scope.
- Quietly noticed within 60 days that they had become "the person who almost left."
By month 4-5, all three reported the same set of frictions: ambiguous reassurance from leadership, fewer mentions in promotion conversations, and one of them being passed over for a project they had previously been a lead candidate for. By month 6, they were on the market again. The counter bought them six months of cash, not retention.
The lesson here matches the conventional wisdom. Money-only counters age badly.
The five who rejected and left
This was the largest cohort and, in the data, the cleanest. None reported regret about leaving. Comp at the new role landed at or above what the counter would have paid. Three of the five reported being "happier in the new role within 90 days." Two reported neutral-to-mildly-positive transitions. None said the counter would have been the right move in retrospect.
The pattern: when the counter is only money, the rational move is almost always to take the outside offer. Money equalizes either way. The thing that doesn't equalize is the trajectory.
What this changes about the advice
The classic advice "don't take a counter" is right when the counter is just cash. It is right most of the time, because most counters are just cash.
But there is a meaningful minority of counter-offers that bundle a role change, a team change, or a formal promotion. In this small sample, all four of those cases worked out. The cohort isn't large enough to be statistical, but it is large enough to question the universal advice.
A more useful framing:
- Cash-only counter: decline. The conventional advice is right. Either there is something structurally limiting the role at this company, or there isn't, but in either case the cash alone won't fix it.
- Cash + structural change counter (role, title, team, formal promotion path): consider. This is closer to a re-hire conversation than a retention conversation. The same logic that made you valuable enough to counter applies to the new structure.
- Counter that asks you to "stay 6 months and we'll figure it out": decline. This is bucket-1 with a delay attached.
Two practical questions to ask
If you are inside a counter-offer conversation, two questions cut through the ambiguity fast.
1. "What changes about my role, in writing, effective within 30 days?" If the answer is nothing, you are in bucket 1. If the answer is something specific, ask question 2.
2. "If I had asked for this role change without the outside offer, would the answer have been yes today?" This is uncomfortable to ask but the answer reveals whether the company is buying retention or fixing a thing they should have fixed earlier. If the answer is "yes, we should have done this anyway," the counter is real. If the answer is "we'd have done it eventually," it isn't.
The thing the counter does to you that nobody talks about
One more pattern across all twelve cases. The counter-offer process itself, regardless of outcome, accelerated the engineer's career trajectory by about a year.
Forced compensation transparency. Forced role conversation. Forced manager reassessment. Even the engineers who took a money-only counter and left six months later reported that the cycle clarified what they actually wanted from a job. The five who rejected and left reported the cleanest version of this — they had a fully-priced view of their own market value going into the next negotiation.
So the counter-offer is not just a yes/no decision. It is a high-information event. Treat it that way regardless of which way you go.
Free tools I built for the job search: resume-checker, job-keywords, resume-bullets. All free, all in the browser, no signup.
Earlier in this series:
- How to Negotiate a Developer Salary (With the Actual Email I Sent) — the original
- What to Say When They Counter Your Counter-Offer — round-2 scripts
- 5 Things to Read in Your Equity Grant Before You Sign — equity-side complement
