In early 2023, Google laid off 12,000 employees, Microsoft 10,000, and Amazon 18,000, all within a few weeks of one another. Software engineering had long been considered relatively recession-proof. That assumption unraveled in less than a single quarter.
It wasn't only the people who lost their jobs who were shaken. On Hacker News, LinkedIn, and Reddit's tech-career communities, engineers who were still employed began posting things like "I don't know where this job is even headed anymore" and "I can't predict how AI is going to change this profession." It was a moment when trust in one's career took a collective hit.
The pattern isn't confined to tech. Similar signals are showing up in product planning, content, PM, and marketing roles — anywhere AI adoption is moving fast. The work itself hasn't changed, but the conviction that it's still the right work to be doing has. How you handle that feeling determines everything that follows.
Burnout or Structural Drift?
The two states look almost identical from the outside: you don't want to work, nothing feels meaningful, and you're running on empty. But the causes are different.
Burnout is caused by overload. Restore your energy, and the same work becomes possible again. Structural drift doesn't resolve with rest. You come back from a proper break and the answer to "why am I still doing this" is no longer as clear as it used to be.
The test is simple. Recall a Monday morning after at least three full days off. If what you felt was "okay, I can get back into this," that's closer to burnout. If the same heaviness of "here we go again" was still sitting there, that's closer to structural drift.
There's a second marker of structural drift: work you're objectively good at becomes steadily harder to explain the meaning of. If you can knock out a proposal quickly and still find yourself thinking "what's the point of this," or write clean code and still think "what's even coming next" — that's not a skill problem. It's the premise of working in this field at all that's coming loose.
Burnout calls for a recovery plan. Structural drift calls for a directional decision. Confuse the two and you'll fail to solve either. Prescribing a job change for burnout is a lot like telling an exhausted person to move to a new city — the novelty lifts the mood for a while, but the actual source of the fatigue never left.
Before You Choose a Direction, Set a Timeframe
The most common mistake once you've confirmed structural drift is rushing. You pick one of job change, starting a business, or a full career switch, and paper over the discomfort with the energy of a fresh start. Six months later, in a different setting, the same heaviness comes back.
There's something to settle before you pick a direction: a realistic limit on how much longer you can tolerate this state. Set it by weighing your finances, family situation, and health together — six months, a year, two years. Only once that window is fixed do the options you can actually test within it become visible.
"Someday I'll make a change" sounds like resolve, but it has no deadline. Without a deadline, it never turns into action. Most people who've been nursing the same complaint for years are stuck exactly at this step.
Once you've set the window, start with the smallest experiment you can run inside it — a side project, regular conversations with people in other fields, or a short-term contract in an area you're curious about. Gather small data points before you make the big decision, not after.
Before You Leave the Field, Check Whether You Can Change the Role First
A large share of people going through structural drift aren't actually exhausted by the field itself — they're exhausted by the specific role they occupy within it.
It feels like IT product planning just isn't for you anymore — but it might actually be the specific position of coordinating dozens of stakeholders inside a large organization that's worn you down. You think you've lost your drive for development — but the real problem might be a specific environment where you're racing deadlines and piling up technical debt. Content planning hasn't gotten boring — a structure where one person is solely responsible for output across ten channels at once has simply become unsustainable.
There's a question that separates the two: "What if I did the exact same work at a completely different scale and structure?" At a small team instead of a large organization, freelance instead of full-time, going deep with one or two clients instead of juggling many — if that version of the work still feels doable, redesigning the role is an option worth exploring before you consider leaving the field.
Redesigning a role carries less uncertainty and takes less time than changing jobs entirely. Sometimes it's possible through an internal transfer within your current organization; sometimes it means moving to freelance or solo work. Skip this step and jump straight to leaving the field, and it's surprisingly common to land in a new field, run into the same role structure, and burn out in exactly the same way.
If You Do Choose a Full Transition: Redefine Before You Relearn
If you've decided to leave the field entirely, there's one assumption people get wrong more often than any other: that they're starting from zero in the new field.
A career, up to this point, is an accumulation of the ability to define problems, find solutions under limited resources, and stay in sync with a range of stakeholders. That ability doesn't vanish when you switch fields. The real work of a career change is figuring out which parts of your prior experience turn out to be worth more than you expected in the new one.
The problem is that it's hard to see the actual shape of what you have while you're still in the role, because you identify yourself with it. Someone who has spent ten years as an IT product planner defines their own ability inside the frame of "I am a planner." They don't separate out whether what they're actually good at is IT planning specifically, or structuring complex requirements, or turning organizational conflict into clear language. That distinction only comes into focus once you've deliberately put some distance between yourself and the role.
You don't have to quit to create that distance. Just taking on a different kind of work outside your role while staying employed, or explaining what you do to people from a completely different industry, is often enough to bring the outline into view. What's taken for granted inside an industry is frequently a rare skill outside it.
The time you spend preparing for a career change should go more into redefining your own capabilities than into learning new skills. The stronger that redefinition is, the more the move into a new field reads as a "career redeployment" rather than a "career gap" — to hiring managers, and to yourself.
The value of this sequence isn't limited to a single career change. Career instability recurs. Not confusing burnout with drift, distinguishing role from field, setting a timeframe before choosing a direction — the gap between someone who has worked through this sequence once and someone who jumped straight to action usually doesn't show itself until about six months later.
