When (and When Not) to Accept a Counter-Offer as an Engineer
Counter-offers in UK engineering have hit a ten-year high. Here is the candidate-side analysis of when accepting one is rational - and when it almost never is.
Industry-wide retention data - including long-running studies from the CIPD and global recruiter surveys - suggests that 50–80 per cent of professionals who accept a counter-offer leave their employer within 12 months anyway. The reason is rarely money; it is the underlying trigger that caused the candidate to interview in the first place.
Before responding to a counter-offer, write down the three reasons you began looking. If two or more are unrelated to pay (scope, management, commute, technology, progression), a salary uplift almost never resolves them durably. If all three are pay-related and the counter materially closes the gap, the analysis is different.
There is also a reputational dimension. In tightly networked sectors - controls, drives, motion, automation systems integration - hiring managers talk. Candidates who accept counter-offers after verbally accepting another role typically find their next conversation with the spurned employer significantly harder.
The right framework is to treat the resignation conversation as data. Listen to what is offered, ask for 48 hours, and test the offer against the original reasons. If the employer required your resignation to act, ask honestly why those changes were not made before.
Where counter-offers are genuinely worth taking: a confirmed promotion with new scope, a documented project assignment, or a structural change in management. Where they almost never are: pure salary matches with no change to the working environment.