What if I lose my job?

01 · After hours

The question waits until the screen goes quiet

The feature is finished. The last test passes. I close a row of tabs and tell myself the day is done. Then a notification arrives: a new AI model, a new coding agent, a new demonstration of work that used to take hours collapsing into minutes.

I know how I am supposed to react. I work in technology. I should be curious. I should test the tool, study the release notes, and imagine what I can build with it. Part of me genuinely does.

Another part asks a quieter question: What if this is the thing that makes my job smaller? What if the next announcement makes it disappear?

That thought carries more than professional pride. A job pays for ordinary life. It supports plans, responsibilities, family, health, and the small sense of safety we build month by month. “Disruption” sounds exciting in a product launch. It feels different when I imagine it arriving in my inbox as a meeting invitation.

02 · Acceleration

Technology has always changed. AI changed the emotional temperature.

People in tech are used to the revolving door. A framework becomes essential, then unfashionable. A platform changes its rules. A tool we spent months mastering becomes a legacy line on a résumé. We learn the next thing because movement is part of the profession.

AI feels different because it reaches toward the work we treated as proof of our value: writing code, explaining systems, analysing data, designing interfaces, drafting strategy, and turning an unclear request into a first version. The tool does not only change the equipment. It appears to enter the workshop and reach for the craft itself.

The pace adds another layer. Before one release has settled into a real workflow, another one becomes the conversation. Social feeds compress careful engineering, marketing, fear, and spectacle into the same endless scroll. Every impressive demo seems to carry an unspoken demand: adapt immediately or fall behind.

03 · Panic loop

I can turn fear into motion and still go nowhere

Job anxiety can look productive. I can save twenty courses, open five documentation sites, subscribe to every AI newsletter, and test tools long after I have stopped absorbing anything. From the outside, it resembles ambition. Inside, it is panic wearing a work badge.

The loop is exhausting: a new tool appears, I compare myself with its best demonstration, I question my existing skills, and I rush toward the next skill before deciding whether it matters to the people I serve. The goal quietly changes from becoming useful to becoming impossible to replace.

That goal cannot be reached. No certification, framework, title, or portfolio can guarantee permanent safety. Companies change direction. Budgets tighten. Teams reorganise. Markets move. Pretending otherwise does not protect me; it only makes uncertainty feel like a personal failure.

There is another danger. If I respond by handing every difficult thought to AI, I may produce more while practising less. My output grows, but my ability to notice a weak assumption, debug a strange failure, question a requirement, or defend a decision begins to thin. I would be using the tool to escape the exact judgment that makes me valuable.

04 · Worst case

So I answer the question instead of running from it

What if I lose my job?

First, it would hurt. I would worry about money and timing. I would probably replay old decisions and wonder whether I should have learned something sooner. Losing a role can shake identity as much as income, especially in an industry that encourages us to introduce ourselves through what we build.

But losing one job would not erase every system I have understood, every difficult conversation I have handled, every client problem I have clarified, or every time I learned under pressure. A company can end a role. It cannot retroactively remove the capacity built while doing the work.

This is not a comforting promise that everything will be fine. Recovery can be slow and unfair. It is a more useful truth: the worst case is a serious event, not the end of my ability to act.

05 · Preparation

I started building a survival system, not a prediction

I cannot forecast which role will change next or how quickly. I can reduce the number of decisions I would have to make while afraid. That means treating career resilience as ordinary maintenance rather than an emergency project.

1. Keep evidence of real work. I document the problem, the constraints, my contribution, and the result. A clear case study survives longer than a list of fashionable tools.
2. Protect the fundamentals. I keep practising how systems connect, how data moves, how users behave, how failures happen, and how trade-offs are explained.
3. Learn one layer beyond my current role. I deepen an adjacent skill that creates options instead of collecting shallow familiarity with everything.
4. Maintain professional relationships. People who know how I think and follow through are more meaningful than a network assembled only when I need help.
5. Create financial breathing room when possible. Even a modest buffer can turn a sudden decision into a considered one.
6. Ship small work in public. A useful tool, explanation, or analysis keeps my learning visible and reminds me that I can still begin.

None of these steps makes a career invincible. Together, they make uncertainty less absolute. They give fear somewhere practical to go.

06 · Partnership

I use AI, but I refuse to disappear inside it

The answer is not to reject the technology. Avoiding AI would not freeze the industry at a comfortable moment. It would only leave me less able to understand the change shaping my work.

I want AI close enough to extend my range and far enough away that I can still see my own decisions. I use it to explore alternatives, remove repetition, challenge a draft, trace unfamiliar code, and accelerate the first pass. Then I inspect what it produced. I test the claim. I read the error. I ask whether the solution fits the context rather than merely looking complete.

The goal is not to compete with a machine at generating the most material. It is to become better at directing effort toward work that deserves to exist.

07 · Return

The next morning, the keyboard is still there

The announcements do not stop. Another model will arrive. Another role will be declared dead in a headline and quietly continue in a different form inside real teams. The ground will keep moving.

But the story changes when I stop asking the future for a guarantee it cannot give. I can ask smaller, harder questions. What problem am I learning to understand deeply? Where am I relying on output I cannot explain? Which relationship have I neglected? What can I finish this week that proves a useful capability?

Then I return to the keyboard. Not because I believe I am safe forever, and not because fear has vanished. I return because building is still how I meet uncertainty: one tested idea, one honest conversation, one finished piece of work at a time.

The future of technology is exciting precisely because it is not settled. That is also what makes it frightening. I am learning to hold both truths without letting either one decide who I become.