Engineer Burnout: Are the Numbers Real?

Engineer Burnout is Becoming more Common — Here's How to Recognise it Early and Stop it

Recent surveys of engineering populations make uncomfortable reading.

Around 65% of engineers report having had a burnout event in the previous twelve months. For senior engineers, tech leads and engineering managers, the number climbs to around 85%.

It's worth reading those numbers again. Burnout in engineering isn't an unfortunate edge case anymore. It's almost the norm. If you're an engineer with a pulse and a calendar, the statistical baseline says you've either just had a burnout episode, are in the middle of one, or are heading towards one.

This is not a piece designed to scare you. It's a piece designed to make the early signs legible — because almost everybody who burns out tells me, afterwards, that they could see the signs months in advance and didn't act on them. By the time the wall arrives, the cost has compounded.

Why Engineering is structurally bad for burnout

Engineering combines several features that, taken individually, would each be a known burnout risk factor. Together, they're a near-perfect storm.

The work is cognitively expensive. Real engineering work — designing systems, debugging thorny problems, holding multiple abstractions in your head at once — is among the most metabolically expensive activities the human brain does. You can't sustain it for ten hours a day, five days a week, for years, without a price.

The deadlines never stop. Sprints, releases, papers, project gates, customer commitments. There's always another finish line, and the organisation rarely creates real recovery time between them. Your nervous system never gets the signal that it's safe to come down.

The work is identity-loaded. Engineers and scientists tend to be people for whom the work is part of who they are. That makes it harder to take a step back when you need to, because doing so feels like stepping back from yourself.

You love it. This is the cruellest one. The burnout that hits hardest in technical careers isn't the burnout of people who hated their jobs all along. It's the burnout of people who genuinely love the work, who find it fulfilling, who light up when they're solving an interesting problem — and who keep over-extending because the joy is real. The love disguises the cost. Until it doesn't.

You're surrounded by other people doing the same thing. Whatever you're doing, somebody else on your team is doing more of it. The local culture quietly normalises a workload that, viewed from the outside, would be alarming.

Why "I love my work, so this can't be burnout" can be dangerous

The version of burnout most people picture — the dramatic crash, the breakdown, the dropping out — is the late-stage version. The version most engineers experience for years before it gets that far is much quieter.

It's a slow, accumulating loss of love for something you used to love. The mornings get a little harder. The afternoons get a little flatter. The thing that used to give you energy still gives you energy on a good day, but the good days come less often. Sleep gets a little worse. Sundays get a little heavier.

If you said this out loud to most engineers, they'd hear "burnout" and think "no, I'm not at that stage". That's the trap. The crash is the late stage. By then, the recovery costs are large. The work to do is upstream of it, when the symptoms are still ambiguous and the costs of action are still small.

Early warning signs that are almost always missed

There are signs my coaching clients tell me, in retrospect, that they were already showing six to twelve months before they thought of themselves as burning out.

You wake up at 3am thinking about work. Not occasionally. Regularly. Specific worries about specific meetings, deadlines or conversations. Your sleep is being colonised.

You feel a low-grade resentment that wasn't there before. Towards stakeholders. Towards your manager. Towards the customer. Towards people who interrupt you. You used to think of these things as part of the job; now they feel like an injustice.

Your energy curve has flattened. You don't have peaks anymore. Things that used to give you a real lift — solving a problem, getting good feedback, finishing something — register as okay rather than great.

You've started cutting things you used to enjoy outside work. Exercise. Hobbies. Friends. Reading anything that isn't work-related. The cuts feel temporary. They've been temporary for two years.

You're working harder for diminishing returns. It takes you longer to do the same quality of work than it used to. You compensate by adding hours rather than by stopping to ask why.

Small things have started feeling huge. A code review comment. A diary clash. A passive-aggressive email. The intensity of your reaction is out of proportion to the trigger.

You feel undervalued — and you're privately fairly sure that's accurate. A persistent sense that you're being asked to do more in return for less. Promotions that didn't come. Recognition that didn't arrive. Pay that hasn't kept up.

If three or more of these are resonating with you, you're not "just busy". You're showing the early pattern. The right response now is much smaller and much cheaper than the right response in twelve months' time.

What actually works (and what doesn't)

The popular literature on burnout will tell you to take a holiday, do mindfulness, set better boundaries, exercise more, sleep more, drink less. None of this is wrong. All of it can help, but sometimes easier said than done.

The reason it doesn't work, at least on its own, for most people in technical careers is that it treats burnout as a personal failure of self-care. The truth is more uncomfortable. Burnout is what happens when a person is being asked, over a sustained period, to do more than the system around them is set up to make sustainable. You can't self-care your way out of a structurally unsustainable workload.

Real recovery — and real prevention — usually involves work at three levels.

Level one: physiological reset. You can't think clearly about anything else until your nervous system has had enough recovery time to come back online. Sleep, daylight, movement, time off the screen. Boring, foundational, non-negotiable.

Level two: structural change. Some honest reckoning with the job as it actually is. What's the realistic workload? What's the part of it you can negotiate, push back on, or decline? Where are the leaks — the meetings that don't need you, the work that's been allowed to expand to fill the time, the part of the job that's not actually your job? Many engineers, on examination, find a surprising amount of the load is recoverable here.

Level three: identity and pattern work. This is the level that rarely gets reached, and it's where coaching usually pays for itself. Engineers who burn out repeatedly often do so because of a pattern they're not aware they're running — the perfectionism, the inability to delegate, the equation of self-worth with productivity, the need to be the one who can be relied on. Until that pattern is updated, the structural changes don't hold; the person finds a new way to fill the recovered time with the same old behaviour.

NLP-informed coaching is well suited to this kind of pattern work, because it operates at the level the pattern itself is operating on. The point isn't to analyse the pattern from above. It's to give the underlying system a different way of running.

What to do this week if any of this rings true

Two suggestions, depending on where you are.

If you recognise the early signs and the cost is still manageable: take it seriously now. Block recovery time in your diary like you'd block a release. Have one honest conversation with your manager about workload. Drop one thing this week that doesn't have to be done. Notice whether you feel any resistance in yourself to doing those things — and treat that resistance as data about how much the pattern has already taken hold.

If you recognise multiple signs above and you've been quietly minimising them for months: don't try to think your way through this on your own. The thing about burnout is that the version of you that needs to think about it is the version that's already been compromised by it. A second perspective from someone who works with engineers in this exact place is genuinely useful, not least because it shortens the path back.

That's the work I do. If you'd like to talk through what's going on in your situation, a free 30-minute Discovery Call is the right place to start. We'd spend half an hour mapping what's actually happening, and at the end of it I'd tell you honestly whether coaching is the right next step for you. If it isn't, I'll usually be able to suggest something that is.

Don't wait for the crash. The cost of acting now is small; the cost of acting later is the one nobody wants to pay.

---

Related reading: [From Engineer to Manager: The Five Mindset Shifts That Actually Make the Promotion Stick](/blog/engineer-to-manager) and [How to Know When It's Time to Leave Engineering](/blog/when-to-leave-engineering).

---

### About the author

Patrick Collins is a coach for engineers, scientists and technical professionals. He's a Fellow of the Institution of Mechanical Engineers and Chartered Engineer with a PhD in Astrophysics, 30+ years in engineering and high-tech industry, experience as a Technical Director through a successful SME exit, and is an NLP practitioner and Hypnotherapist. He works with clients worldwide.