Career Standby: When the Future Stops Feeling Solid

The workday is over. Slack is closed. You are halfway through making dinner when you open LinkedIn on your phone, almost without deciding to.

There is another layoff announcement. A post about an AI agent completing a week of engineering work in an afternoon. Someone explaining why the skill you spent years developing is no longer enough. You save a job listing you probably will not apply to, then make a mental note to revisit your CV this weekend.

Nothing has happened. You still have a job. Monday's work is waiting.

And yet some part of you is already preparing for its absence.

Lately, I have noticed a different kind of exhaustion in tech. It is not exactly burnout, although it can eventually become that. It is not career grief, because nothing has ended yet. It is the strain of remaining professionally ready for disruption even while your ordinary working life continues.

I have started thinking of this as Career Standby.

Career Standby is what happens when preparedness stops being an occasional action and becomes a background condition. You are still building, collaborating, and trying to care about the work in front of you. But somewhere behind all of that, another process keeps running: what if this does not last?

The five-year question under AI uncertainty

Career conversations used to contain a familiar question: where do you see yourself in five years?

The question was never easy, and the answer was rarely accurate. Still, it assumed something useful: that the future was solid enough to imagine. You could picture a direction. A deeper technical path. A move into leadership. A different company, perhaps, or a product of your own. The point was not prediction. It was orientation.

For many engineers, AI has made that question feel different.

Now the first thought is not always where do I want to grow? It is: which parts of my work will still be valued by then? Will the role still exist in a recognizable form? Will using AI well be enough, or will the bar move again before you have properly adjusted to this version of it? Should you go deeper into engineering, move closer to product, learn a new domain, or quietly begin preparing for another profession altogether?

Nobody has a clean answer. That matters.

The uncertainty is not imaginary. In the first quarter of 2026, Gallup reported that 31% of U.S. technology workers thought it was likely their job would be eliminated within five years because of automation or AI. Dice's 2026 Tech Sentiment Report found a similarly uneasy picture: many tech professionals expected to change employers, while far fewer felt confident they would find something better.

Statistics do not tell you what will happen to your career. They do help explain why an ordinary Tuesday evening can feel strangely provisional.

The second invisible job of Career Standby

Career Standby creates a second job underneath the one you are already doing.

The first job is visible. It has tickets, meetings, pull requests, deadlines, and the occasional production issue that arrives at exactly the wrong moment.

The second job happens in fragments. Fifteen minutes reading job descriptions before bed. A saved article about an unfamiliar tool. A half-finished course opened after a tiring day because resting feels slightly irresponsible. A quiet calculation of how many months your savings might cover. A side project chosen less from curiosity than from the hope that it will make your profile look current if the market turns against you.

None of these actions is unreasonable on its own. Updating a CV is sensible. Learning is part of a long career in software. Keeping some awareness of the market can be healthy.

But there is a difference between preparing once and rehearsing loss every day.

That difference is easy to miss because Career Standby often looks responsible from the outside. You are not collapsing. You are planning. You are staying informed. Perhaps you are even shipping consistently at work while quietly building an escape route at night.

The cost appears elsewhere: in the evening that never quite feels like an evening, in the weekend that becomes a small professional insurance policy, in the inability to enjoy a calm period because calm starts to resemble the moment before bad news.

When learning becomes career insurance

Software has always required learning. That is part of its appeal. There is pleasure in encountering an unfamiliar idea, following it until something clicks, and realizing that your mental map of the craft has grown a little wider.

Career Standby changes the emotional texture of that learning.

You are no longer reading because something sparked your curiosity. Or not only because of that. You are reading because you saw another post suggesting that engineers who do not master a particular tool immediately will become irrelevant. You open the tutorial with a tired urgency. The question underneath is no longer what could this help me build? It is what happens if I do not keep up?

That shift matters. Curiosity tends to widen your attention; fear narrows it until every new thing starts looking like evidence that you are late.

I wrote about reinvention fatigue as the cost of repeatedly becoming legible again when the field moves. Career Standby sits slightly earlier in the sequence. It is the anticipatory phase: the feeling that you must keep repositioning before you even know what changed, because waiting for clarity might mean waiting too long.

AI intensifies this because the visible pace is relentless. Models improve. Product launches arrive. Confident predictions spread faster than evidence. If you already carry the comparison trap, the feed becomes more than a source of professional information. It becomes a weather system. Every announcement changes the forecast.

And you start dressing for a storm that may or may not arrive.

The Plan B running in the background

There is nothing wrong with having a Plan B.

A long career can include detours, role changes, periods of uncertainty, and chapters you could not have designed from the beginning. Practical preparation can be an act of care — for yourself, for the people who depend on you, for the future version of you who may need options.

But a Plan B can also become a low, continuous hum beneath Plan A.

Maybe you wonder whether you should move into management before the market decides pure engineering is less valuable. Maybe you consider consulting, teaching, or a completely different field. Maybe the thought is vaguer: I should probably have something else. Not because you want to leave. Because staying without an escape route has started to feel naive.

The mind is good at running these simulations. It can produce a surprising number of alternate lives while you are trying to finish one ordinary day.

There is a point where contingency planning stops creating safety and starts making the present harder to inhabit. You become partially absent from work you still care about, and partially absent from the rest of your life too. You are always preparing to evacuate a future that has not actually happened.

This is one of the more difficult parts to name honestly. The industry does not need to make an explicit threat for the threat to become ambient. Sometimes the combination of headlines, layoffs, product demos, and confident predictions is enough. The uncertainty enters the room and stays there, even on quiet days.

Preparedness ≠ permanent vigilance

Job insecurity is not a personal weakness. The World Health Organization includes it among the working conditions that pose a risk to mental health, alongside excessive workloads, low control, and unclear roles.

That framing matters because it moves the conversation away from self-criticism. If you feel unsettled by a labor market that is visibly changing, the answer is not to become better at pretending certainty. There is no honest way to guarantee that your current role, your current stack, or even the current shape of software engineering will remain untouched.

But uncertainty does not deserve unrestricted access to your attention.

Preparedness has edges. It might mean updating your CV, setting aside a financial cushion where possible, keeping contact with people you trust, or choosing one area of learning that feels durable enough to deepen. These are actions. They can be completed, revisited at a reasonable rhythm, then put down for a while.

Permanent vigilance has no edges. It turns every evening into a referendum on whether you did enough to remain employable. There is always another tool to test, another thread to read, another possible future to insure yourself against.

The goal is not to stop paying attention. It is to notice when attention has become a form of unpaid on-call.

A smaller place to stand

When the future feels unstable, the instinct is to build a perfect plan. A complete map through a landscape that keeps changing. That is understandable. It is also impossible.

I do not have a neat answer for this one. I am not sure anyone does.

The more useful move may be smaller: separate what deserves a concrete response from what is merely asking you to worry.

Some questions help with that separation:

• What has materially changed in my work, not just in my feed?

• Which part of my craft still feels worth deepening even if the tools keep moving?

• What is one preparation task that would genuinely help — and when will it be done for now?

This is close to the distinction between controlling inputs and trying to control outcomes. You cannot produce certainty through enough late-night research. You can decide what kind of engineer you want to be while the uncertainty remains: curious without becoming frantic, prepared without living in rehearsal, adaptable without treating your present self as already obsolete.

There may still be a CV update this weekend. There may still be a course worth taking, a conversation worth having, or a Plan B that deserves some real thought.

Let those be tasks. Not an atmosphere.

Final thoughts

The future of software engineering will change. Some roles will shift. Some skills will become less central, while others will matter in ways we cannot fully see yet. Pretending otherwise would not make anyone calmer for long.

But a career is lived in the present tense.

It is lived in the feature you are trying to understand, the colleague you are helping, the problem that still catches your curiosity, the dinner getting cold while you scroll through another prediction about a future nobody can describe with confidence.

Prepare where preparation is useful. Take uncertainty seriously. Then, when you have done what today reasonably asks of you, close the tab.

You do not need to solve your entire professional future every evening after work.