LeadDev surveyed engineering managers and their teams for their 2025 State of Engineering Management report. 22% of engineers reported critical burnout. 24% reported moderate burnout. That is 46% of engineers experiencing meaningful burnout.
Haystack Analytics puts the number higher: 83% of developers report burnout. The difference depends on methodology and definition. LeadDev measures self-reported burnout severity. Haystack measures whether developers have experienced burnout symptoms. Either way, the numbers are bad.
I have run engineering teams for 11 years. I have seen burnout from the inside — both in my own team and in client teams we joined. The cause is rarely the work itself. It is the environment the work happens in.
What Drives Burnout
Expanded responsibilities, same headcount
65% of engineers report taking on more responsibilities without additional headcount (LeadDev). The 74% talent shortage means companies cannot hire. So existing engineers absorb the work. Backend developers start doing DevOps. Frontend developers handle design. Senior engineers do project management on top of coding.
Each additional responsibility reduces focus time. Engineers who spend 4 hours per day in meetings and context-switching have 4 hours per day to code. The same amount of feature work is expected. The result is longer hours, lower quality, or both.
Technical debt
43% of developers cite technical debt as a burnout factor (Haystack). Working in a legacy codebase where every change is fragile, every deployment is risky, and every sprint starts with "first we need to fix what broke" is exhausting.
The psychological weight of technical debt is underestimated by managers who do not write code. It is not just that the work takes longer. It is that the work feels pointless — fixing the same categories of bugs, working around the same architectural limitations, knowing that the system is getting worse despite your effort.
Unrealistic deadlines
59% cite unrealistic deadlines. This connects to the headcount problem. The same amount of work, fewer people, same deadline. The math does not work. Engineers know the math does not work. Management sets the deadline anyway. Engineers either crunch to meet it (burnout) or miss it (demoralization).
Software projects overrun by 45% on average. When the baseline estimate is already aggressive and the average overrun is 45%, the resulting schedule is a burnout generator.
AI tools are not the fix
AI coding tools were supposed to help. The data says otherwise. 84% of developers use AI tools but only 29% trust the output. METR found that AI tools made experienced developers 19% slower on complex tasks. Using an untrustworthy tool that occasionally speeds you up and frequently slows you down is not a burnout fix. It is an additional cognitive load.
What Actually Reduces Burnout
Reasonable team sizing
The math: if a product needs 6 engineers to deliver on time, staffing it with 4 means burnout. The talent shortage makes hiring hard. Retained engineering teams close the gap in 2-3 weeks instead of 95 days.
Snapwire needed 30 engineers. They had 20. We provided 10. The team was no longer understaffed. The work was no longer compressed into too few people.
Technical debt allocation
15-20% of every sprint goes to reducing debt. This is not a luxury. It is burnout prevention. Engineers who see the codebase improving feel progress. Engineers who watch it decay feel hopeless.
Scope discipline
Features ship in 2-week sprints. Scope is defined per sprint, not per quarter. When the sprint is full, additional requests go to the backlog. No exceptions. This protects engineering time and gives the team a sustainable rhythm.
Stable teams
Our average client engagement is 3+ years. Engineers work on the same product, with the same teammates, for years. They are not rotated between projects every 3 months. They build domain expertise and relationships that make the work easier and more rewarding.
HeyTutor: 9 years. MyFlyRight: 10 years. Greek House: 4 years. These are not just engagement durations. They are engineering environments where people stay because the work is sustainable.
The Retention Connection
Burnout drives attrition. 24% of developers are unhappy and 92% plan to look for a new job. The replacement cost is $150K-$250K per departure. The companies that prevent burnout retain engineers. The companies that cause burnout pay to replace them.
The cheapest engineer is the one who stays. The most expensive is the one who leaves and takes 6 months of context with them. Burnout prevention is not an HR initiative. It is a financial imperative.
Last updated June 8, 2025