Why your best developer is leaving, and what it really costs you

It usually happens on a Friday. Your most experienced developer asks for a short meeting and hands in their notice. They have found something else, the decision is made, and they are polite about it.

The manager is surprised. The developer is not. In most cases they have been thinking about it for months, and the signs were there for anyone who knew what to look for.

This article is for the owner, the CTO or the head of development. It covers what such a departure really costs, why good developers actually leave, the signs that it is coming, and what you can still do, before and after.

What one departure really costs

Gallup estimates that replacing an employee costs between half and twice their annual salary, and calls that a conservative estimate. For a senior developer, the upper half of that range is closer to the truth, because the cost is not only the hiring. It is everything the team cannot do while the seat is empty and while the new person learns the system.

A typical timeline, as we see it in practice:

1. 1–3 monthsNotice period: still there, mentally gone
2. 2–4 monthsSearching for a replacement
3. 1–3 monthsThe new person's own notice period
4. 3–6 monthsOnboarding until fully productive

Added up, that is often six months to a year in which the team works with less capacity than planned. For an example company where a senior developer costs 70,000 € a year:

Cost	How it shows up	Rough amount
Recruiting	Agency fee, job ads, the team’s time in interviews	10,000–20,000 €
Empty seat	Features that are not built, projects that slip	15,000–35,000 €
Onboarding	The new person at half speed, colleagues explaining	15,000–25,000 €
Lost knowledge	Mistakes in parts only the leaver understood	hard to estimate, often the largest
Total		40,000–80,000 €, before lost knowledge

The numbers are illustrative, not measured, but the order of magnitude matches Gallup’s range. The last row is the one that hurts most, because nobody budgets for it. Our article on knowledge and taking over a .NET application shows what happens when the person who knew the system is gone.

Why they actually leave

Ask a developer why they left and the answer is often “a better offer”. That is the polite version. In the Stack Overflow Developer Survey 2025, the factor developers ranked highest for job satisfaction was not pay, but autonomy and trust to manage their own tasks. Pay came second, followed by solving real-world problems, working on challenging problems, and control over the quality of their work.

That matches what we see. Good developers rarely leave a job they like for 10 % more. They leave a job that frustrates them, and the better offer is simply the way out. The most common frustrations:

• Responsibility without authority. They are expected to keep quality up, but nobody gave them a say in how. We wrote a whole article on that: senior developer or tech lead.
• Constant firefighting. Every week starts with urgent production issues. Planned work never happens, and the system never gets better.
• Priorities that change every week. What was urgent on Monday is cancelled by Thursday. After a while, nobody believes the plan any more.
• A system that teaches them nothing. Years on an old platform, with no time to modernise it, while the rest of the industry moves on. Our article on technical debt and slow development describes how that builds up.
• No path forward except management. The only way to grow is to stop programming. Many excellent developers do not want that, so they grow somewhere else.
• Quality decisions made over their heads. Deadlines that force them to ship something they know will break, and to fix it later in their own time.

Pay matters, of course. Being clearly below the market is a reason on its own. But when pay is fair, the reasons above decide who stays.

Warning signs

Gallup reports that 52 % of employees who left voluntarily said their manager or organisation could have done something to prevent it. Most departures can be seen coming:

What you see	What it often means
They stopped arguing in meetings	They no longer believe their opinion changes anything
Fewer proposals and improvements	They stopped investing in the future of this system
More days off, often single days	Interviews
Their LinkedIn profile is suddenly up to date	Exactly what you think
Complaints about the same things for months	Nothing changed after they raised it
They decline new responsibilities they used to want	They do not plan to be there long enough

None of these proves anything on its own. Two or three together are a reason for a conversation, now rather than after the notice.

What you can do before the notice

The cheapest retention is a conversation that happens early enough. Not a performance review, but an honest one:

“What is the most frustrating part of your work right now? And what would you change if you could decide?”

Then listen, and do something with at least one of the answers. Things that usually help:

1. A clear role. If you expect them to lead technically, give them the mandate and the time for it. If you do not, stop expecting it.
2. Protected time for improvement. A fixed share of every sprint for paying off technical debt, tests and tooling. Even 10–20 % changes how the work feels.
3. Fewer priority changes. Not none, but fewer, and explained. A plan that lasts two weeks is worth more than a perfect plan that lasts two days.
4. A technical career path. Growth in responsibility and pay without having to become a manager.
5. Fair pay, checked against the market. If you do not know where you stand, find out before they do. Our article on .NET developer rates gives an idea of the market.

When the notice is already on the table

Sometimes it is too late, and that is fine. What matters now is the notice period.

• Secure the knowledge first. Ask: what do only you know? Which parts of the system, which passwords and accounts, which customer quirks, which scripts on which server? Write it down together, in the first week, not the last.
• Organise a real handover. Pair them with whoever takes over each area. Documentation helps, but working side by side for a few weeks helps more.
• Do not leave the seat empty for months. While you search, an external senior can cover the most important work and take over the knowledge directly from the leaver. More on that in our article on what to do while you look for a senior .NET developer.
• Part well. People who leave on good terms recommend you, answer the odd question after they leave, and sometimes come back.

Constantly changing priorities also make every deadline slip, which then gets blamed on the team. Our article on why software estimates are always wrong shows how two weeks turn into two months.

Questions we hear most

Will a raise keep them?

Sometimes for a while, rarely for good. If the reason was pay, yes. If the reason was frustration with the work, a raise buys a few months, and the frustration is still there.

Should we make a counter-offer?

Only if you are also ready to change what made them want to leave. A counter-offer without change usually just delays the departure, and the rest of the team learns that handing in a notice is the way to get a raise.

How long does it take to replace a senior .NET developer?

From notice to a fully productive replacement, often six months to a year: the search, the new person’s own notice period and the time to learn your system. That is why the handover and the bridging period matter so much.

How do we stop depending on one person?

Spread knowledge on purpose: code review, pairing on critical parts, documentation as part of every change, and no part of the system that only one person has ever touched. It costs a little every week and saves a lot on the day someone leaves.

How we work

ProCoding is a .NET studio in Split, Croatia. When a key developer leaves, we step in for the gap: we take over the knowledge during the notice period, keep the most important work moving, and help your next developer settle in. We also help teams before it comes to that, with technical leadership, tests and the paying off of technical debt. As a monthly block of days, or with a freelance .NET developer inside your team. The first step is a free 30-minute call.

Sources

• This fixable problem costs U.S. businesses $1 trillion, Gallup
• Stack Overflow Developer Survey 2025: Work, Stack Overflow