Yashveer Singh
Connect
<- All posts

Engineering Retention: Why People Leave and How to Stop It

Engineers leave for predictable reasons. Boredom with the work. A manager they do not respect. Compensation that drifted below market. An opportunity that offers what is missing. The companies that retain well diagnose the reasons honestly and address them before the engineer is leaving. The companies that lose engineers regularly explain departures with stories that miss the actual cause. The diagnosis is the work.

Written by Yashveer Singh, founder of Yashveer Labs.

What you actually need to know

  • Engineers leave for the work, the manager, or the comp. In that order usually.
  • Compensation is rarely the top reason but often the trigger.
  • Counter offers usually fail six months later.
  • Exit and stay interviews are the diagnostic tools.
  • Patterns of departures matter more than individual stories.
ReasonFrequencyResponse
Boring workTop reasonMatch assignments to interests
Bad managerClose secondManager development or replacement
Below market compensationFrequent triggerAnnual compensation review
No career progressionFrequentDocumented ladder and conversations
Family or life changeSometimesCannot prevent. Communicate well.
Higher impact opportunitySometimesHard to compete with. Match where possible.

The core argument

Engineers leave for predictable reasons. The literature on this is large. My own observation across many client teams matches the literature. The work is the top reason. The manager is a close second. Compensation is the third. Each cause has signs that are visible months before the departure. The companies that watch for the signs and address them retain well. The companies that do not see the signs lose engineers and explain each departure with a unique story.

The work cause is about engagement. The engineer is no longer growing. The assignments are repetitive. The impact is unclear. The engineer starts to wonder what they would do at a different company. The wondering becomes searching. The searching becomes interviews. The interviews become offers. The departure follows.

The manager cause is about trust and advocacy. The engineer does not feel heard. The manager does not develop them. The manager does not advocate for them when it matters. The engineer concludes that the relationship is not going to improve. The engineer leaves for a manager they hope will be better.

The compensation cause is usually a trigger rather than a root cause. The engineer who loves the work and respects the manager tolerates a small compensation gap. The engineer who is bored and badly managed uses compensation as the trigger to leave. The compensation conversation looks like the cause when it is actually the catalyst.

The diagnosis is the work. Exit interviews. Stay interviews. Skip level conversations. The team that asks the questions gets answers. The team that does not ask explains every departure as something other than what it was.

The signs to watch for

SignWhat it might mean
Engineer takes less ambitious workBoredom or low engagement
Skips optional team eventsDisconnection
Quiet in design meetingsLost interest
Short answers in one on onesDistance from manager
Updated LinkedIn or GitHub recentlyLooking
Asks about external opportunitiesLooking
Stops mentoring othersPulling back
Pushes back on long term commitmentsPlanning to leave

How much does the retention work cost

The cost is manager attention and culture investment. Weekly one on ones. Quarterly career conversations. Annual comp reviews. Recognition. Skip levels. Exit interviews that produce lessons. The dollar cost is the comp that keeps the team at market. The time cost is the manager's attention. Both are modest relative to the cost of replacing engineers.

Features the retention program must have

  • Manager development for one on ones and career conversations.
  • A documented career ladder.
  • Annual compensation review against market.
  • Skip level conversations.
  • Stay interviews for at risk engineers.
  • Exit interviews that capture honest reasons.
  • A pattern recognition practice across departures.
  • A way to address surfaced issues.

Expert opinion

The companies that retain engineers well diagnose departures honestly. The work. The manager. The comp. The opportunity. The companies that lose engineers regularly explain each departure with a story that misses the pattern. The diagnosis is the work. The fix follows from the diagnosis. The retention investment is modest relative to the cost of replacement. The math is consistently favorable.

>

Yashveer Singh, founder of Yashveer Labs

How this played out on a real project

A client SaaS engineering team lost five engineers in eight months. The founder explained each one with a different story. Family move. Better opportunity. Different stack. We did exit interviews with the engineers who had left.

The pattern was consistent across four of the five. The work had become repetitive. The same engineer had been on the same surface for three years with no rotation. The manager had not had career conversations. The compensation had drifted ten to fifteen percent below market.

We changed the practices. Rotation across surfaces every eighteen to twenty four months. Weekly one on ones with career topics. Annual compensation against market. The next year had one departure. The work to retain was less than the work to replace.

For more on the related work, see engineering retention the patterns that work and the engineering compensation philosophy that scales.

Common mistakes companies make

  1. Treating each departure as a unique event.
  2. No exit interviews or exit interviews that get nothing useful.
  3. Counter offers as the retention strategy.
  4. Compensation below market.
  5. No career conversations.
  6. Managers who do not advocate.
  7. No rotation across surfaces. Engineers get bored.
  8. No skip level conversations.

A 90 day plan to improve retention

  1. Weeks one and two. Conduct exit interviews with recent departures. Identify themes.
  2. Weeks three to six. Conduct stay interviews with current engineers. Identify at risk.
  3. Weeks seven to nine. Address the surfaced issues. Comp. Manager. Work.
  4. Weeks ten to twelve. Establish the ongoing practices. One on ones. Career conversations. Reviews.

For more on the related work, read engineering retention the patterns that work and the engineering sabbatical a underrated retention tool. On the broader culture side, the engineering culture document that engineers actually read is the natural next read.

FAQ

Frequently asked

Author

Why this is the work I do

The work in this article is not theoretical for me. It is what I shipped last quarter, last month, and this week. Yashveer Singh, founder of Yashveer Labs. I do not write about things I have not done. I do not pretend to expertise I do not have. If the topic here is the topic you are dealing with, I am the person who has dealt with it. Multiple times. Recently.

Related reading