Topic

Career Pivot

Real stories from engineers, PMs, and designers who made the leap — with the finances and feelings included.

19 articles

Almost nobody leaves tech in a single decisive move. The gap between privately deciding something has to change and actually going is usually measured in months or years, and most of the real work happens inside it.

These articles are about that gap: working out what you actually want after a decade of optimising for the wrong things, calculating the runway you genuinely need, negotiating your exit, and preparing while still turning up every day.

If you're at the very start of this, the complete guide to leaving tech maps the six stages and will point you at the right one to begin from.

Why I went back to a tech job after trying to leave twice

→

How I calculated my "freedom number" before leaving my tech job

→

The financial fears that keep burnt-out tech workers stuck — and how to face them

→

The 5 questions to ask yourself before making any big career decision

→

I downshifted from senior engineer to junior at a different company — no regrets

→

One year after leaving Google — the honest update

→

From PM to independent consultant — the first 90 days honestly

→

How to negotiate a severance package when you're ready to leave

→

10 Career Paths Tech Workers Can Explore Beyond Tech

→

I left a $180k engineering job to become a writer — here's year one

→

How much runway do you actually need before leaving a tech job?

→

From senior engineer to ceramics teacher — the finances nobody tells you about

→

How to prepare for leaving tech while you're still showing up every day

→

Financial independence for tech workers — what FI actually means when you're burnt out

→

What to tell your family when you're thinking about leaving a well-paid tech job

→

The tech worker's guide to knowing when enough is enough

→

How to use AI tools to test a new career path before you fully commit

→

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

→

Tech jobs that don't involve coding: a realistic list for burnt-out engineers

→