Key takeaways
- Jobs are bundles of tasks. Automation takes tasks, and the job re-forms around what is left.
- Exposure tracks how routine a task is, not how skilled the job sounds.
- The entry-level squeeze is the credible concern: AI is best at what juniors were hired to do.
- What protects a career is domain depth, owning outcomes and accountability — not any one skill.
- People who use these tools well displace people who refuse to, far more reliably than the tools displace either.
Jobs are bundles of tasks, not single things
Almost every alarming forecast about AI and employment shares one flaw: it treats a job as an indivisible unit that either survives or does not. Real jobs are bundles of tasks, and automation has historically taken tasks rather than whole occupations.
Consider what happened to accountants after spreadsheets. The tedious arithmetic disappeared almost entirely. The profession did not — it grew, and shifted towards analysis and advice. The task changed; the job re-formed around what was left.
That framing is more useful than a yes or no. Ask which tasks in your week are routine transformations of information, because those are the exposed ones, and what remains once they are gone.
How to actually audit your own role
The abstract question is unanswerable; the concrete one is not. Log your work for a week in half-day blocks and label each block by what it really consisted of — producing a routine output, deciding something, persuading someone, or handling a situation nobody had specified.
Then ask of each block whether the inputs were fully written down. Tasks where everything needed is in a document are the exposed ones. Tasks that depend on knowing who to ask, what happened last quarter, or what the client actually meant are not, because the necessary context is not available to be automated.
Most people discover their week is more mixed than they assumed, and that the exposed portion is real but smaller than the headlines imply. That is a more useful starting point than a percentage from a forecast about your job title.
What current AI is genuinely good at
Being specific about capability is more useful than speculation. Today’s systems are strong at producing plausible drafts, summarising and restructuring text, writing routine code, translating, and pattern-matching across large volumes of documents.
They are weak wherever the cost of being confidently wrong is high, where context lives in people’s heads rather than documents, where physical presence is required, and where the work is fundamentally about persuading, negotiating or holding responsibility.
Notice that this cuts across seniority rather than along it. Parts of a senior job can be highly exposed and parts of a junior job barely exposed at all, which is why occupation-level predictions are so unreliable.
- Most exposed: routine content production, first-line support, basic data entry and reconciliation, template-driven documentation
- Partly exposed: junior software work, paralegal research, entry-level analysis, first-draft design
- Least exposed: skilled trades, healthcare delivery, work requiring accountability or negotiation, roles built on relationships and trust
| Property of the task | Exposed | Protected |
|---|---|---|
| Where the context lives | In documents | In people and history |
| Cost of a confident error | Low, caught downstream | High or irreversible |
| Who is accountable | Nobody in particular | A named person |
| What good looks like | Specified in advance | Judged case by case |
| Physical presence | Not required | Required |
The entry-level squeeze is the real problem
The most credible concern is not mass unemployment. It is that AI is best at precisely the tasks juniors were historically hired to do — the first draft, the research summary, the simple ticket, the boilerplate.
That breaks the traditional apprenticeship ladder. If nobody pays a junior to do the routine work, the profession loses the mechanism by which people become senior. This is a structural problem the industry has not solved, and if you are early in your career it is worth taking seriously rather than dismissing.
The practical response is to get closer to the parts of the work that were never routine — ownership of an outcome, direct contact with users or customers, judgement under uncertainty — earlier than previous generations had to.
What actually protects a career
Not "learning to code" or any other single skill. What holds up is a combination that is hard to unbundle: domain knowledge, judgement about what is worth doing, and the ability to take responsibility for a result.
Notice that the person who uses these tools well tends to displace the person who refuses to, far more reliably than the tools displace either. That has been the pattern with every previous productivity technology, and it is the most actionable thing in this whole discussion.
There is a quieter advantage too. Being the person in a team who can tell when a generated answer is subtly wrong is increasingly valuable, and that ability comes from domain depth rather than from tooling familiarity — it cannot be acquired quickly by someone outside the field.
- Deepen domain expertise — AI is general, and generality is cheap
- Move towards owning outcomes rather than producing outputs
- Get fluent with the tools in your own field rather than avoiding them
- Build the relationships and reputation that no model has access to
- Keep a written record of what you have actually delivered
Be honest about the uncertainty
Anyone giving you a confident percentage for how many jobs will vanish by a specific year is guessing. The historical record on technology forecasts is poor in both directions: predicted catastrophes that did not arrive, and disruptions nobody saw coming.
What is reasonably well supported is narrower and more useful. Task composition within jobs is shifting quickly. Demand is rising for people who can direct these tools competently. And the transition is uneven — some people and regions absorb it far more easily than others.
That unevenness is the part most worth planning around. Aggregate outcomes being fine is little comfort if your particular role, employer or region is on the wrong side of the distribution, and that is a risk you can actually act on.
Frequently asked questions
Which jobs are safest from AI?
Roles combining physical presence, regulated accountability and human trust hold up best — skilled trades, healthcare delivery, and senior roles where someone must own the consequences of a decision. "Safe" is relative though: most jobs will change composition rather than disappear.
Should I change careers because of AI?
Rarely a good reason on its own. Switching fields resets your domain expertise, which is one of the main things that protects you. Deepening expertise in your current field while getting genuinely fluent with the tools is usually the stronger move.
Is it harder to get an entry-level job now?
In several white-collar fields, yes — the routine work juniors were hired for is exactly what these tools do well. Candidates who show ownership of a real outcome, rather than only coursework, are having noticeably more success.
How do I work out whether my own job is exposed?
Log a week in half-day blocks and ask of each whether everything needed was written down. Tasks fully specified in documents are exposed; tasks depending on people, history or unstated intent are not.
Does being senior protect me?
Not by itself. Exposure follows how routine a task is, not how senior the title is, so parts of a senior job can be highly exposed while parts of a junior job are barely affected.
Is the risk the same everywhere?
No, and the unevenness matters more than the average. Aggregate outcomes being acceptable is little comfort if your specific role, employer or region sits on the wrong side of the distribution.
Check this against your own resume
Scan your CV against a real job description, or build a parse-safe one from scratch. Your first scan costs nothing.