Burnout is real, common, and expensive. People who burn out leave companies, miss work, do worse work before they leave. The cost to teams is large; the cost to individuals is larger.
This page is about recognizing burnout early and preventing it structurally — not about how to recover after it happens.
Burnout is not just "tired." The clinical definition (Maslach):
Burnout is chronic, not acute. It builds over months. By the time it's visible, prevention is too late.
Watch for:
These are individually noise; together over time, they're signal.
Burnout is rarely "personal weakness." It's usually structural:
Working consistently over capacity. Not for a sprint but as the steady state.
Constantly trying to figure out what's wanted. Drains energy without producing visible progress.
No control over what to work on, how to work on it. Especially harmful for engineers.
Bad management, conflict, hostile environments. Wears people down.
Repetitive, manual operational work. Necessary but unrewarding. See ToilReductionStrategies.
Work that doesn't match the engineer's strengths, interests, or values.
Always-on culture; expected to be available; no clear off-time.
What actually prevents burnout:
Estimate honestly. Push back on unrealistic deadlines. Hero work for short crunch periods is fine; "always crunch" is the path to burnout.
Most engineering work is done well in 30-40 focused hours per week. More than that produces diminishing returns and accumulates fatigue.
The myth: more hours = more output. The reality: tired engineers ship more bugs.
Engineers who don't take vacation burn out. Make taking time off visibly OK; cover for each other.
People do better when they own their work. Constant reassignment, micromanagement, or "everyone owns everything" produces frustration.
Automate operational work. Distribute on-call rotations. Reduce the unrewarding repetitive parts. See ToilReductionStrategies.
Engineers who feel stuck burn out faster. Visible career progression — promotions, scope expansion, new challenges — keeps energy.
Remote and even in-office, the connections matter. Isolated engineers burn out faster.
Set expectations: work happens during work hours. Slack outside hours is OK to ignore. Email at 11pm doesn't expect a midnight response.
Once it's visible, recovery is harder. Some patterns:
Real time off. Not "work from home with reduced hours" — actually away from work.
Take work off their plate. Doesn't mean firing them; means letting them work on less for a while.
If their role is the problem, fix the role. Reassignment, different team, different responsibilities.
Burnout often involves management failure. Address it; don't just blame the individual.
If the company won't change and the person is burning out, sometimes leaving is right. As manager, your goal is the person's wellbeing, not their retention at any cost.
Sustained overwork as culture. Predictable burnout in 1-2 years.
The reliable engineer gets all the hard problems. They burn out; the team loses its strongest member.
Glorifying the engineer who works weekends. Sets expectations for everyone; produces resentment and burnout.
If every quarter is a crisis, the team isn't operating sustainably. Crises happen; constant crisis is structural.
"They couldn't handle the workload" — when the workload was genuinely unsustainable. Easier than fixing the structure.