Tech burnout: the complete guide to recognising it, recovering from it, and deciding what's next

Burnout is one of those words that has been used so loosely for so long that it has almost stopped meaning anything. It gets applied to a bad week, a demanding sprint, a boss you dislike. So when it actually happens to you — the real thing, the version that doesn't lift on a Saturday and doesn't lift after a holiday either — you often don't recognise it, because the word has been worn smooth by overuse.

This guide is about the real thing, specifically as it happens to people who work in tech. It draws on everything we've published about burnout — the recognition, the biology, the recovery, the relationships it damages, and the decision it eventually forces — and organises it into the sequence most people actually move through. You don't need to read it all today. Find the part that matches where you are, start there, and follow the links deeper.

Part 1: Is this actually burnout?

Almost everyone spends longer here than they need to, because the early symptoms are easy to explain away. The exhaustion gets attributed to a rough quarter. The irritability to a difficult colleague. The Sunday-evening dread to being insufficiently grateful for a job most people would want. Each individual explanation is plausible, which is exactly what makes the pattern so easy to miss.

The most reliable place to start is the ten signs you're burnt out — not the internet-quiz version, but the ones that actually distinguish burnout from ordinary tiredness. Then pay attention to the physical signals, because your body tends to admit there's a problem months before your mind will. Disrupted sleep, a stomach that has opinions about Monday, infections that linger, a resting heart rate that has quietly drifted upward: these arrive early and are almost always misfiled as unrelated.

Two distinctions matter enormously at this stage, and getting them wrong sends people down years of unproductive paths.

The first is burnout versus depression. They share symptoms — exhaustion, flatness, loss of interest — but they have different causes and different treatments, and the difference is not academic. Burnout is context-bound: it lifts, at least partially, when you're genuinely away from the context that caused it. Depression travels with you. If your flatness follows you into a holiday, a weekend with people you love, or a hobby you used to enjoy, that is worth taking to a professional rather than to a productivity system.

The second is that quiet quitting is not laziness. The disengagement that gets moralised about in management blogs is, far more often, a nervous system doing exactly what it's supposed to do: withdrawing effort from a situation that has stopped being survivable at full output. Reading your own disengagement as a character flaw is one of the most common and most costly mistakes people make here.

If you recognise yourself in someone who spent years concluding they were simply lazy, read the account of running on empty for three years. It's the single most common story we hear, and the recognition itself tends to be the thing that finally shifts something.

Part 2: Why tech does this so efficiently

Burnout is not unique to tech, but tech has an unusually complete set of the conditions that produce it, which is why it shows up here at such scale.

The mechanism is worth understanding, because it reframes the problem from a personal failing to a structural one. Chronic stress has measurable long-term effects — on cardiovascular health, immune function, sleep architecture, and memory — and those effects don't politely pause while you finish one more quarter. The stress response is designed for short bursts followed by recovery. Tech work frequently supplies the bursts and systematically removes the recovery: always-on communication, on-call rotations, quarterly cycles that never actually end, and a culture that treats availability as commitment.

Then there's the accounting nobody does. The real cost of staying in a job that's burning you out works through what the situation is actually costing you — not just in health, but in earning potential, relationships, and the compounding opportunity cost of years spent depleted. People stay because leaving looks expensive. The comparison is usually being made against the wrong baseline.

Some environments compress all of this dramatically. Three years at a startup that broke me is a first-hand account of what happens when equity, mission language, and a small team combine into something that makes ordinary boundaries feel like betrayal.

And there's a newer pressure that didn't exist five years ago. AI doing work that used to be yours adds a layer of existential uncertainty on top of the ordinary exhaustion — a low background hum of "is this even worth recovering for?" that makes everything else harder to face. If that's part of what you're carrying, it's worth naming rather than treating as unrelated.

Part 3: What to do in the next seven days

If you're deep in it right now, long-term strategy is not what you need. You need to stop the bleeding, and you need steps small enough to actually take while exhausted.

Start with the seven-day reset for burnt-out engineers. It is deliberately not a productivity system — no optimisation, no habit stacking, no 5am routine. It's the minimum sequence for getting a nervous system out of emergency mode, designed to be doable by someone who has nothing left.

In parallel, there are two conversations worth considering. The first is with your manager: how to say you're struggling without tanking your career covers what to disclose, what to leave out, and how to frame it as a capacity problem rather than a confession. It is possible to have this conversation badly, and the article is mostly about avoiding the specific ways it goes wrong.

The second is the one you have with yourself about limits. Setting boundaries when your company culture punishes it is the honest version — not "just log off at five," but what to do when the culture genuinely does penalise unavailability, and how to pick boundaries that survive contact with a team that doesn't respect them.

And if you've already privately decided you're leaving but can't go yet, managing stress at work when you've already decided to leave addresses that specific and strange interval — the months where you're still showing up for something you've mentally exited.

Part 4: Why rest alone didn't fix it

This is the part that blindsides people. You take the holiday. You take the leave. You come back, and within about ten days you're exactly where you were — and now you have the additional worry that if rest didn't work, maybe you're broken.

You're not. Why taking time off didn't fix my burnout — and what did is the most-read article we've published on this, because it names the mechanism plainly: rest treats depletion, but burnout is usually caused by conditions. Remove yourself from the conditions temporarily and you get temporary relief. Return to unchanged conditions and you get an unchanged outcome. Time off is necessary and it is not sufficient, and knowing that in advance saves people from concluding the problem is them.

What does work is less dramatic and slower. What actually helped me recover — and what was just noise separates the interventions that moved the needle from the large category of things that felt productive and changed nothing.

For many people the missing piece is professional support, and finding the right kind matters more than people expect. How to find a therapist who actually understands tech work stress covers why a generalist can struggle with this — the specifics of on-call, of equity vesting as a golden handcuff, of imposter syndrome in a field that rewrites itself every eighteen months — and how to screen for someone who won't need it all explained from scratch.

Recovery also isn't linear, and it doesn't require you to be idle. How to start a side project when you're still recovering is about the delicate business of re-engaging with creative work without recreating the exact conditions that broke you — which is a real risk, because the same drive that produced the burnout is very good at repurposing itself.

Part 5: The parts that spill over

Burnout does not stay politely inside working hours, and the collateral damage is often what finally forces the issue.

The most common casualty is your relationships. How burnout affects your relationships — and what to do about it covers the specific pattern: the person who is depleted all day has nothing left for the people at home, those people feel the withdrawal as rejection, and the resulting friction becomes another stressor feeding the original problem. It's a loop, and it usually needs to be named out loud before it can be interrupted.

There's also the anticipatory version of the damage — the anxiety about what happens if you do step away. The anxiety nobody warns you about when you finally have free time is written for after the exit, but it's worth reading before, because knowing that relief is often not the first thing to arrive removes a lot of unnecessary alarm when it doesn't.

And if you're wondering whether any of this is even real or whether you're simply not tough enough: ninety days of writing about burnout, and what the responses taught us is the closest thing we have to an aggregate answer. The patterns in what people write in are remarkably consistent, and the most consistent one is that nearly everybody believes they're the only one.

Part 6: Do you actually need to leave?

Eventually burnout forces a question, and it's important to ask the right one. "Am I burnt out?" and "do I want to leave tech?" are separate questions, and collapsing them into one leads to bad decisions in both directions — people who quit an industry when they needed to quit a manager, and people who endure a decade because they correctly sensed that leaving wasn't the answer.

Work through the five questions to ask before any big career decision before committing to anything. Consider the intermediate moves first, because they're reversible and surprisingly effective: deliberately downshifting to a less demanding role solves it for some people entirely. And read the story of someone who went back twice — not as a cautionary tale, but because it complicates the narrative usefully. Leaving isn't always permanent and isn't always right the first time, and knowing that takes some of the pressure off the decision.

If you're returning rather than leaving, what nobody tells you about returning to work after burnout leave covers the re-entry — which is harder than most people expect, and which almost nobody prepares for.

And if you work through all of this and conclude that the answer really is to go: that's a different and much longer project, and it has its own map. How to leave tech: the complete guide covers the six stages from first doubt through the money, the preparation, and the part after.

Where to start today

Pick the one that matches where you actually are, not where you'd prefer to be.

Not sure this is burnout: take the self-assessment, then read the ten signs. Sure it is, and running on empty: start the seven-day reset tonight — sleep first, everything else after. Rested and still exhausted: read why time off didn't fix it, because the answer isn't more rest. Flatness that follows you everywhere: read burnout or depression and then talk to someone qualified. Damaging things you care about: start with relationships. Certain you need out: begin with the five questions, not the resignation letter.

The single most useful thing you can do at any stage is stop treating this as a personal failing to be pushed through. Burnout responds to changed conditions, not to greater effort — and greater effort is the one thing you've already tried.