Your key developer is quitting: what a team lead should do

A DM lands: "can we talk? something's come up." Ten minutes later the strongest engineer on the team — the one half the system rests on — says they've got an offer and are thinking of leaving. Your stomach drops: without them deadlines slip, the bus factor collapses, and the team gets jittery the same day.

What you do in this moment decides whether you lose a person, the knowledge, and a couple more people after them — or come out of it in control.

First, figure out if it's already too late

A resignation is rarely spontaneous. By the time of the talk the decision is usually all but made, and the offer in hand is the last chapter of a story that built up for months: unnoticed contribution, a ceiling, fatigue, conflict.

First honest question to yourself: is this a signal you can still turn around, or has the train left? If they've already said goodbye in their head, your job changes — not retain at any cost, but hand the knowledge off cleanly.

A counter-offer is almost always a trap

The temptation's obvious: outbid them. But a counter-offer treats the symptom, not the cause. Leaving over a ceiling or burnout — a raise buys you a couple of months, then the same talk repeats, now with trust dented on both sides.

Money's only worth discussing if it's genuinely about the salary market, not about what's behind the word "tired."

Count the bus factor — what only they know

While the emotions run hot, do the cold thing — size up the risk:

• which parts of the system only this person knows;
• where there's no docs and no second owner;
• what stalls if they leave in two weeks.

That list is your real problem. Even if you keep them now, that bus factor is a landmine you have to defuse anyway.

The retention talk: what to ask

Don't plead and don't guilt-trip. Listen.

"Thanks for telling me in person, not after the fact. I won't try to talk you out of it on the spot — I want to understand. What was the last straw? What would've had to be different for this talk not to happen?"

The answer tells you whether anything can actually change — and whether it's worth it. Sometimes it turns out they needed recognition and a new challenge, not an offer. Sometimes — you were six months too late.

If they do leave

A strong engineer leaving isn't just a loss, it's a test of your maturity. Make the parting clean: agree a handover plan, capture knowledge in docs and pairing (not in the leaver's head), keep the relationship. The industry's small, and a good exit comes back as referrals and boomerang hires.

Bottom line — don't panic. It rattles the nerves, but it's part of the job; you'll sort it. And you can run a talk like this risk-free ahead of time.