Why your best engineer just handed in their notice

Your best engineer did not wake up one morning and decide to leave. The decision built over months. By the time they handed in their notice, it was already settled. What you are dealing with now is the consequence of something that was preventable much earlier.

Here is what actually drives engineering attrition and what changes that.

The pay gap they only discovered because a recruiter called

The most common trigger for a good engineer resigning is discovering an £8,000 pay gap against the external market after an inbound recruiter call, not active dissatisfaction. Internal pay reviews measure against internal benchmarks and cost-of-living adjustments, neither of which tracks shortage-profession market movement. An annual external benchmark closes the gap before it becomes a resignation.

This is the single most common reason engineers leave, and it is also the most avoidable. They were not actively looking. They were doing their job, broadly satisfied, not scanning job boards. Then a recruiter called about a role paying £8,000 more than their current salary.

They would probably have stayed if their pay had moved with the market. It had not, because nobody had told them the market had moved, and nobody had reviewed their salary in the context of what comparable roles were paying externally. Internal pay reviews typically measure against internal benchmarks or cost-of-living adjustments. Neither reflects market movement in a shortage profession.

The fix is an annual external salary benchmark for every technical role, particularly at mid and senior level where the market moves fastest. You do not need to pay the absolute top of the market. You need to be close enough that the gap is not worth changing jobs over.

No visible progression

“You are doing really well” is not a career conversation. Engineers who have been in the same role for two to three years, consistently meeting expectations, and have not been given a clear view of what comes next, start to feel that the business does not have a plan for them.

They may be right. Many businesses manage performance adequately but manage career development poorly. The annual appraisal is the extent of the development conversation, and it typically covers the year behind rather than the years ahead.

Visible progression does not require a promotion to exist. A senior engineer who is given lead responsibility on a significant project, brought into commercial or client conversations, or given scope to develop a junior, is progressing in the ways that matter. What they need is evidence that the organisation sees them, is investing in them, and has a plan that they are part of.

Management that does not understand the technical work

This is mentioned consistently in exit interviews and less consistently addressed. An engineer who reports to a manager who has no technical background will eventually reach the limits of what that management relationship can support.

It is not that non-technical managers cannot manage engineers. Some do it well. The problem is a manager who cannot engage with the technical work, cannot advocate for resources or decisions based on engineering reasoning, and cannot provide professional development guidance because they do not understand the discipline. That relationship stops working when the engineer’s problems become technical problems.

This is particularly acute in growing businesses where engineering capability has expanded faster than technical management capacity. The engineer ends up solving technical problems in isolation and managing upward in a language the business does not speak.

Lack of investment in tools, training, and technology

Engineers notice when the organisation is not investing. An out-of-date CAD licence, a refusal to fund an industry conference, a training budget that was cut for the third consecutive year. These are signals. They tell the engineer that the business does not view their professional development as a priority.

Individual items in this list may seem minor. The cumulative message is not.

Why do counter-offers not work?

Counter-offers do not work because most engineers who accept one have left within six to twelve months anyway. The pay gap triggered the resignation conversation, but the underlying reasons (progression stall, management frustration, career direction) existed before the recruiter called. Adding money removes the trigger without addressing the cause.

The research on counter-offers is consistent: most engineers who accept a counter-offer have left within six to twelve months anyway. This is because the reasons they decided to leave were rarely just about money. The pay gap was the immediate trigger, but it surfaced issues that existed before the recruiter called: the progression stall, the management frustration, the sense that something was not working.

Offering more money removes the immediate trigger. It does not address the underlying reasons. The engineer re-engages briefly, remembers why they were leaving, and starts a new process, this time more deliberately.

What actually retains good engineers?

Good engineers are retained by structured career conversations twice a year separate from appraisals, annual external salary benchmarking against live placement data, real technical development budgets that are actually spent, and early visibility of the next interesting project. YP Recruitment market data confirms these four interventions outperform any single retention lever in shortage disciplines.

Structured career conversations twice a year, separate from appraisals, focused on the next two to three years rather than the previous twelve months. Not what went well in Q3, but what this person wants their career to look like in 2028 and what the business can do to get them there.

Annual external salary benchmarking. Not cost-of-living increments but actual market comparison against live placement data.

Investment in technical development. Training budget that is used, conference attendance that is encouraged, and scope to work on projects that expand skills rather than just deploy existing ones.

Early sight of interesting work. Engineers who know what is coming in the pipeline, and have reason to believe they will be involved in it, have a reason to stay.

Which exit interview question is worth asking?

The single exit interview question worth asking is “at what point did you start thinking about leaving?” The answer is almost never the month of resignation; it is usually six to eighteen months earlier. That timeline identifies exactly when the retention intervention needed to happen and what it needed to address for the colleagues who are still there.

“At what point did you start thinking about leaving?” The answer is almost never the month they resigned. It is usually six to eighteen months earlier. That timeline tells you when the intervention needed to happen and what it needed to address.

That information is genuinely useful if you act on it for the people who are still there.

Read more about our engineering recruitment work or find out how we approach engineering hiring if you need to replace someone or are thinking about how to restructure a team. For leadership-level challenges, our engineering leadership work is relevant here too.