How to leave tech: the complete guide, from first doubt to life after

Nobody leaves tech in one move. From the outside it looks like a single decision, but everyone who has done it describes the same thing: a long sequence of stages, each with its own questions, fears, and mistakes waiting for the unprepared. This guide maps the whole sequence — find your stage, start there, and follow the links deeper.

Nobody leaves tech in one move. From the outside it looks like a single decision — one day you're a software engineer, the next you're not — but everyone who has actually done it describes the same thing: a long sequence of smaller stages, each with its own questions, its own fears, and its own mistakes waiting for the unprepared. The first doubt. The quiet research. The spreadsheet. The conversations. The exit. And then the part nobody plans for: what happens after.

This guide maps the whole sequence. It draws on everything we've published — dozens of first-person accounts and practical deep-dives — and organises it into the six stages almost everyone moves through. You are probably in one of them right now. You don't need to read all of this today. Find your stage, start there, and follow the links into the articles that go deeper on whatever you're facing.

Stage 1: Admitting something is wrong

Most people spend a surprisingly long time here — months, often years — explaining away what their body and mood are telling them. The tiredness gets attributed to a rough quarter. The irritability to a difficult colleague. The Sunday-evening dread to being insufficiently grateful for a good job. If you're in this stage, the most useful thing you can do is get honest about what's actually happening before you make any decisions at all.

Start with the ten signs of burnout — not the internet-quiz version, but the ones that distinguish burnout from ordinary tiredness. Pay attention to the physical signals too, because your body usually admits there's a problem long before your mind does, and chronic stress has real long-term costs that don't wait politely while you finish one more project. If you recognise yourself in the person who kept concluding they were just lazy, read the account of running on empty for three years — it's the single most common story we hear.

Two things matter at this stage. First: burnout is not the same as wanting to leave tech, and treating them as the same question leads to bad decisions in both directions. Some people need recovery, not resignation. Others discover that time off doesn't fix it because the problem is structural, not personal. Second: you don't have to decide anything yet. Naming the problem accurately is the whole job of stage one.

"Burnout is not the same as wanting to leave tech. Some people need recovery, not resignation. Others discover time off doesn't fix it because the problem is structural. Naming the problem accurately is the whole job of stage one."

Stage 2: Deciding whether to actually leave

This is the stage where the question shifts from "what's wrong with me?" to "do I actually want out?" — and it deserves more rigour than most people give it. The pull of a big decision can make leaving feel like the answer to everything, which is exactly why it's worth slowing down here.

Work through the five questions to ask before any big career decision. Be honest about whether you're successful but numb — a specific and confusing condition that doesn't respond to the usual advice — or whether you've hit the point described in knowing when enough is enough. And before you commit to the exit, consider the intermediate moves: setting real boundaries, telling your manager you're struggling, or even deliberately downshifting to a less demanding role. For some people these moves solve it. For others, trying them is what finally confirms that the problem isn't fixable from inside — and that confirmation is valuable in itself.

It's worth reading the story of someone who went back twice at this stage, precisely because it complicates the narrative. Leaving isn't always permanent, it isn't always right the first time, and knowing that in advance takes some of the pressure off the decision.

Stage 3: The money

Money is where most escape plans quietly die — not because the numbers don't work, but because they were never actually calculated. Vague financial dread will keep you stuck indefinitely; a real number, even a large one, is something you can work toward.

The sequence is straightforward. First, work out how much runway you actually need — the honest version, based on what you really spend. Then go deeper with a real budget before quitting and, if you're the type who wants a single target to aim at, calculate your freedom number. While you're still earning, build the six-month emergency fund — a tech salary is the best runway-building tool you will ever have, and it stops the moment you leave.

Two more pieces round this stage out. The financial fears that keep people stuck deserve direct examination, because most of them shrink dramatically when written down. And if your exit might be involuntary or negotiable, learn how to negotiate a severance package — an underused option that funds a surprising number of successful transitions. For the longer view, what financial independence actually means for tech workers and what it looks like on a reduced income reframe the whole question away from "can I afford one year off" toward "what life am I actually funding?"

The financial checklist, in order

  • Know your real monthly number. Three months of actual bank statements, irregular expenses included, plus 10% for what you missed.
  • Set your runway target. Months without income × real monthly number, plus a two-to-three-month buffer and health coverage if relevant.
  • Build it while employed. A named transition account, funded monthly. Your current salary is the plan's engine — use it deliberately.
  • Check the severance option. If a reorganisation is in the air, a negotiated exit can fund six months of your transition.
  • Stress-test the plan. What happens if the transition takes twice as long? If the answer is "catastrophe," extend the runway before you leave.

Stage 4: Preparing while you're still employed

The gap between deciding to leave and actually leaving is typically six months to two years, and how you use it determines almost everything about how the transition goes. The full playbook is in how to prepare for leaving tech while you're still showing up every day — it covers the financial groundwork, the professional positioning, and the narrative you'll need when people start asking questions.

The hard part of this stage is psychological: you're performing a role you've mentally left. Managing stress when you've already decided to leave addresses that specific limbo. So does the question of who to tell and when — what to tell your family is its own delicate problem, especially when the job you're leaving is one they're proud of. And if your next chapter involves independent work, this is exactly when to find your first freelance client while still employed — nothing de-risks a leap like a client who predates it.

Stage 5: Figuring out what comes next

"Anything but this" is not a destination. The people whose transitions work tend to leave toward something, even if it's only a rough direction. Start with the ten careers tech professionals actually transition into — real paths with real evidence, not listicle filler. If you genuinely don't know what you want, that's its own problem with its own method: how to figure out what you actually want when you've spent a decade optimising for the next rung of someone else's ladder. A newer option worth knowing: using AI tools to test a career path before you commit lets you prototype a direction in evenings and weekends instead of betting the runway on a guess.

Then read the stories — not for inspiration, but for calibration. The senior engineer who became a ceramics teacher (including the finances nobody mentions). The engineer who left $180k to write, one year in. The PM who went independent, first ninety days. One year after leaving Google, the honest update. The burnout that pushed one developer to freelance — and if that's your path, the guide to setting rates when you're terrified of charging. For the widest view, twelve honest stories of life beyond tech in one place. What these accounts share is not triumph — it's texture. The transitions that work are slower, messier, and more financially deliberate than the versions that go viral.

"'Anything but this' is not a destination. The people whose transitions work tend to leave toward something — even if it's only a rough direction. The stories worth reading aren't the triumphant ones; they're the ones with texture."

Stage 6: After you leave

Here is the stage nobody plans for, because from inside a burnout it's unimaginable that leaving could be anything other than pure relief. Then you leave, and within weeks you meet the things the planning spreadsheet didn't cover: the anxiety that arrives when you finally have free time, the strange grief of no longer being "the smart one in the room", the discovery that your job title was carrying more of your identity than you knew.

The identity work is real work. How to rebuild your sense of self when your job title was your whole identity is the practical guide; what leaving tech actually did to my sense of self, two years later is the honest long-range report. If you worry about your skills decaying, what happens to your tech skills when you step away will probably reassure you — and the skills AI can't replace makes the case that what you keep is more durable than what you lose. And if you eventually go back — to a job, to the industry, on your own terms — that isn't failure. Returning to work after burnout and the going-back-twice story both treat return as a legitimate move in a longer game, which is exactly what it is.

Where to start today

If you take one action after reading this, make it stage-appropriate. Exhausted but haven't named it yet: read the burnout signs and take an honest inventory. Deciding: work the five questions. Committed but stuck on money: open your bank statements and calculate your runway this week — the number is less frightening than the fog. Preparing: the while-you're-still-employed playbook is your map. Already out and finding it stranger than expected: you're not doing it wrong — this is normal, and it passes.

Leaving tech is not one decision. It's a sequence of small, reversible, mostly unglamorous moves — and every one of them is easier with a map. This is the map. Come back to it as you move through the stages.

L
Life Beyond Tech
This guide is built from everything we've published — dozens of first-person accounts and practical deep-dives on leaving tech. It's updated as new articles are added, so it's worth bookmarking and coming back to.

One honest letter, every Sunday.

Join 1,200+ tech workers getting real talk about burnout, career pivots, and what comes next. No hustle culture. No spam.