The advice circulating about AI-proofing your career is mostly wrong — not because the people giving it mean badly, but because it's designed to feel actionable rather than to actually work. "Learn to code." "Master prompt engineering." "Build your personal brand." These are not useless, but they're not the moves that determine whether you stay employed and valued as AI capability expands. They're the surface.

The moves that actually matter operate at a deeper level. They change your structural position relative to AI — not your skills inventory relative to a job posting. Here are the three that consistently show up in the careers of professionals who are thriving in this transition, regardless of their field.

"The careers being protected right now are not the ones adding the most new skills. They're the ones changing their position."
01
Move Toward Accountability — Not Away From Complexity

The most common mistake professionals make when they realize their role is at risk is to try to learn new, more technical skills and hope complexity protects them. Sometimes it does. More often, the complexity is temporary — AI catches up within 18 to 36 months, and the cycle repeats.

The more durable move is toward accountability. In any workflow where AI produces outputs, someone must be responsible for those outputs. Someone must check them, validate them, sign off on them, and be professionally and personally accountable if they're wrong. That accountability function cannot be automated — it requires a person, and it requires a person with enough expertise to actually catch errors.

The practical shift: Stop optimizing for the execution of tasks and start optimizing for ownership of outcomes. Be the person who is responsible for the result — not just the person who produced one step of the process. This is a posture change as much as a skill change. But it's the posture change that determines whether AI automates around you or works under you.

This is what the books call the Oversight Class — the workers who, rather than being displaced by AI, become the accountable layer that sits above it. Their job is to direct AI tools, validate their outputs, and own the results. This class is growing, not shrinking, because every AI tool deployed in a real organization requires exactly this function.

Identify one outcome in your current role you could explicitly own — not just contribute to. Take public accountability for that outcome's quality. Document your standards for it. This is the beginning of repositioning.
02
Develop Fluency With AI Tools — Specifically to Know Their Limits

This is the version of "learn AI tools" that actually matters — and it's different from the version most people are following. Most people using AI tools are optimizing for output speed. They want to produce more, faster. That's useful but doesn't differentiate.

The professionally valuable version of AI fluency is understanding where AI tools fail. What do they get confidently wrong? What types of inputs produce unreliable outputs? When should you override the AI's recommendation versus accept it? This is the knowledge that makes you irreplaceable in an AI-assisted workflow — not because you can use the tool, but because you can evaluate whether the tool is right.

Why this matters specifically: AI tools produce confident wrong answers regularly. They hallucinate facts. They miss context. They apply the wrong framework to edge cases. In a world where AI-generated outputs are everywhere, the ability to catch these errors — quickly, reliably, and before they cause problems — is extremely valuable. It requires domain expertise that the AI doesn't have.

A doctor who knows exactly when an AI diagnostic tool's suggestion is wrong, and why, is worth far more than a doctor who either ignores AI tools entirely or accepts their outputs without evaluation. A financial analyst who can identify when an AI model is extrapolating incorrectly is worth more than one who either refuses to use the model or trusts it blindly. The evaluator is the protected position.

Pick the AI tool most relevant to your field. Use it seriously for 30 days. Document every time it's wrong, and understand why. That failure map is your professional competitive advantage.
03
Make the Strategic Move Before Pressure Forces a Desperate One

The careers that get disrupted most painfully in any technology transition are not the ones in the highest-risk roles. They're the ones in the highest-risk roles whose occupants waited too long to make a move. The move from a replaceable position to a leveraged one is straightforward when you have runway — time, options, and a deliberate strategy. It becomes nearly impossible when it's forced by a layoff, a budget cut, or a team restructure that's already happened.

Fear is data. Panic is distortion. If your honest assessment of your role puts it in moderate or elevated risk territory, that's not a reason to act desperately — it's a reason to act deliberately and soon. The window to reposition is genuinely open right now. It will get narrower as automation tooling matures and as the organizations in your industry adapt to it.

The specific shape of a strategic move varies by field, but the principle is consistent: move from executing tasks to evaluating and owning outcomes. Move from working inside a defined process to being responsible for the quality of that process. Move from general competence to specialized, contextual expertise that takes years to develop and can't be documented in a training manual.

This is not a call to change careers. In most cases, the field you're in is not the problem — your position within it is. The surgeon doesn't need a new career; the way they're positioned relative to AI surgical assistance tools determines their trajectory. The network engineer doesn't need to leave networking; whether they're doing routine configuration or designing resilient architectures determines their trajectory. The same field. Completely different exposure.

Map your current role honestly against the leveraged vs. replaceable criteria. Identify the one change in your daily work — not your job title — that moves you toward accountability and away from execution. Start making that change this month, not when you feel pressure to.

What Doesn't Work.

For completeness — the moves that feel protective but aren't:

Learning to code — useful if you're going into software development. Not a general-purpose shield. Software is already one of the most AI-affected fields; adding general coding skills doesn't significantly change your exposure in a non-technical role.

Building a personal brand — valuable for many reasons, but not career protection. A strong LinkedIn presence doesn't change whether your role is routine or judgment-dependent. It helps you find a new job. It doesn't make your current one less replaceable.

Learning AI tools as a way to produce more output faster — this is productivity, not protection. When everyone uses AI to produce more output faster, the baseline expectation rises and the headcount still shrinks. You're faster, but there's one of you where there used to be three.

Waiting to see what happens — the single most common and most costly response. The professionals who made strategic moves in 2022 and 2023 have runway. The ones who are starting in 2026 are moving faster and with less choice. The ones who wait until they're forced will be moving in crisis conditions. Every delay narrows the options.

Rising Tides — The Full Playbook

Chapters 27 through 35 cover these moves in full — how to move before pressure forces you, the specific repositioning strategy for different career situations, and what the other side of this transition looks like. $5.99 on Amazon Kindle.

Get Rising Tides on Amazon →
// Also in The Read