Burnout is one of the most serious threats to engineering team health and retention. It builds slowly, is often invisible until it is severe, and can drive your best engineers to leave. As an engineering manager, you are uniquely positioned to spot the early signs and create conditions that prevent burnout from taking hold.
Recognising the Signs of Burnout
Burnout manifests differently in different people, but there are common patterns to watch for. The most reliable signal is a change in behaviour. An engineer who was previously engaged and enthusiastic becomes withdrawn and cynical. Someone who used to take pride in their work starts delivering the bare minimum. A reliable team member begins missing meetings or coming in late.
Other signs include increased irritability during code reviews or team discussions, withdrawal from social interactions, declining code quality despite the engineer's known capabilities, and an inability to focus on tasks that previously came easily. Physical symptoms like frequent illness, visible exhaustion, and complaints about sleep problems are also indicators.
It is important to distinguish burnout from temporary stress. Everyone has tough weeks. Burnout is characterised by its persistence — the exhaustion does not improve with a weekend off, the cynicism deepens over time, and the engineer's sense of professional efficacy continues to decline. If you have noticed these patterns for more than two to three weeks, it is time to act.
- Watch for sustained changes in engagement, enthusiasm, and work quality
- Note withdrawal from team interactions and social activities
- Look for increased cynicism, irritability, or negativity
- Distinguish between temporary stress (resolves with rest) and burnout (persists and deepens)
- Pay particular attention to your highest performers — they are often most susceptible
Having the Conversation About Burnout
Approaching an engineer about potential burnout requires sensitivity. Many engineers feel that admitting to burnout is a sign of weakness or that it will negatively affect their career. Create a safe space for the conversation by being direct but non-judgmental.
Start by sharing your observations without making assumptions: 'I have noticed you seem less engaged in sprint planning lately, and your energy in one-on-ones feels different from a few months ago. I want to check in and see how you are doing.' This opens the door without forcing a diagnosis.
Listen more than you talk. If the engineer confirms they are struggling, your role is to understand what is driving it and to offer support — not to fix the problem in a single conversation. Common drivers include sustained overwork, lack of autonomy, unclear impact, repetitive or unchallenging work, and personal life stressors that compound professional pressure.
Immediate Interventions for Burnout
Once burnout is identified, take immediate action to reduce the load. This might mean reassigning on-call duties, removing the engineer from a high-pressure project, cancelling non-essential meetings, or simply giving them explicit permission to work at a reduced pace for a defined period.
Encourage time off. Many burned-out engineers are reluctant to take holiday because they feel they cannot afford to fall further behind. As their manager, you need to make it clear that time away is not just permitted but expected. Offer to help them plan their absence so their work is covered — removing the guilt barrier is as important as removing the workload.
If the burnout is driven by a specific project or working relationship, address that directly. Move the engineer to different work, change the team composition, or escalate the dysfunctional dynamic that is causing the problem. Surface-level interventions like 'take a mental health day' are insufficient when the root cause is structural.
Creating Sustainable Working Conditions
Prevention is far more effective than intervention. Build sustainability into how your team operates. Start with realistic workload expectations — if your team is consistently working evenings and weekends to meet commitments, you are overcommitting, not under-resourcing.
Protect focus time. Context-switching is one of the most exhausting aspects of engineering work. Establish meeting-free blocks, limit the number of projects an engineer works on simultaneously, and be ruthless about cancelling meetings that do not need to happen.
Create variety in the work. Engineers who spend months on the same type of task — bug fixes, incident response, or maintenance work — are at high risk of burnout. Rotate responsibilities, offer opportunities for creative or exploratory work, and ensure that every engineer gets to work on something they find genuinely interesting at least some of the time.
Long-Term Burnout Prevention Strategies
Build a team culture where discussing workload and energy levels is normalised. Include questions about sustainability in your one-on-ones: 'On a scale of one to five, how sustainable does your current workload feel?' Track the answers over time — a declining trend is an early warning system.
Model the behaviour you want to see. If you send emails at midnight and work through holidays, your team will feel pressure to do the same regardless of what you say. Take your own time off, set boundaries around your working hours, and be visible about doing so.
Advocate for systemic changes at the organisational level. If burnout is widespread across your team or your organisation, the problem is structural — it cannot be solved through individual interventions alone. Push for realistic planning, appropriate staffing levels, and a culture that values sustainable pace over heroic effort.
Key Takeaways
- Watch for sustained behavioural changes, especially in your highest performers
- Create a safe, non-judgmental space for burnout conversations and listen more than you talk
- Take immediate action to reduce load — reassign work, encourage time off, address structural causes
- Build sustainability into team operations through realistic workloads, protected focus time, and work variety
- Model healthy boundaries yourself and advocate for systemic changes at the organisational level
Frequently Asked Questions
- Is burnout the manager's fault?
- Burnout is rarely caused by a single factor, and it is not productive to assign blame. However, as a manager, you have more influence over your team's working conditions than anyone else. You set workload expectations, protect focus time, manage stakeholder demands, and shape team culture. When burnout occurs, your responsibility is to address both the immediate situation and the systemic conditions that allowed it to develop — not to blame yourself, but to take ownership of creating a better environment going forward.
- What if the engineer refuses to acknowledge they are burned out?
- Respect their perspective, but do not stop observing. Share your concerns once clearly, explain that you are there to support them whenever they are ready, and continue monitoring their performance and wellbeing. Sometimes people need time to recognise and accept what is happening. In the meantime, you can still take indirect action — reducing their workload, protecting their focus time, or shifting them to more engaging work — without requiring them to label their experience as burnout.
- How do I prevent burnout across a whole team, not just individuals?
- Focus on the systemic factors: workload planning, on-call burden, meeting load, and the ratio of interesting-to-tedious work. Conduct regular team health checks using a framework like the Spotify Squad Health Check to identify areas of concern before they become crises. Ensure that on-call, maintenance, and other high-burden responsibilities rotate fairly. And be honest with your own management about your team's capacity — protecting your team from overcommitment is one of your most important jobs.
Explore Team Health Tools
Use our interactive tools to assess team health, track workload sustainability, and identify burnout risks before they become critical.
Learn More