Will AI replace my job?

Your title is only a container. Two people called project manager, accountant or software developer may spend their weeks on very different work.

One may prepare repeatable documents. Another may resolve exceptions, negotiate priorities and carry responsibility for decisions.

Those tasks do not have the same relationship with current AI tools.

This is the most useful pattern in the Reddit discussion that prompted this guide.

People answering the same question described both rapid automation and little immediate change. Their experiences were not necessarily contradictory.

The work inside their roles differed, as did the authority, systems, regulation and customer contact around it.

Official occupational data also describes jobs through tasks, skills, activities and work context.

O*NET is useful for creating a starting list, but your own task mix must correct it. The title should help you begin the review; it should never decide the result.

One “AI risk” number hides three different questions. Exposure asks whether current tools can address part of the task. Human resilience asks where a person remains important.

AI leverage asks where a tool may improve the work while a person keeps control.

Imagine a financial analyst who drafts a recurring commentary, investigates unusual movements and presents a recommendation to a risk committee.

Drafting may have high exposure. Investigating inconsistent data may retain substantial human judgement.

Preparing alternative explanations may offer high leverage if the analyst verifies every claim. Calling the whole role “replaceable” loses those distinctions.

This is also why exposure is not job-loss probability.

Adoption cost, demand, liability, data access, regulation, workflow design and management choices all affect what happens next.

Research from the ILO describes job transformation as a more likely broad effect than full automation, while warning that exposure is uneven.

A short task audit gives you evidence you can act on today. You do not need a perfect occupational forecast, a résumé upload or a list of every duty you have ever performed.

Use a normal week as the reference period. Include recurring work, exception handling, meetings, decisions and follow-up.

Avoid vague items such as “manage projects.” Write observable tasks such as “reconcile delivery changes with the client and update the launch plan.”

The goal is not to prove that you are safe.

It is to identify where work may compress, where your contribution is durable, and where a tool could help without quietly transferring risk to you.

The clearest warning signs appear in your workflow and organisation.

A polished demo may show technical capability, but it does not show whether the tool can use your data, survive exceptions, meet policy or carry responsibility.

Pay attention when entry-level tasks disappear, a team stops replacing leavers, output expectations rise without new headcount, or a previously specialist task becomes self-service.

These changes may matter before a role is formally redesigned.

Also watch for positive signals.

New review duties, customer explanation, workflow ownership, quality assurance and governance can become more valuable as production becomes easier.

Your response should strengthen the work that others need to trust, not merely the work a tool can generate.

A useful manager conversation is about planned workflow change, not a request for certainty.

Your manager may not know the long-term future of the occupation, but they may know which tools are being tested, which costs are under pressure and which outcomes still need accountable owners.

Bring your task list.

Ask which work the team wants to reduce, where quality currently fails, which customer or regulatory constraints cannot move, and what evidence would support a broader role.

This makes the conversation operational rather than anxious.

If the organisation expects you to train or supervise a system, ask how the new responsibility will be recognised. Verification is work.

So are escalation design, documentation and monitoring. Do not let those duties become invisible simply because the first draft is faster.

Do not make an expensive career move from one alarming headline.

Start exploring when several signals align: most of your frequent tasks are compressing, your organisation offers little path into higher-judgement work, demand is weakening, and you can name an adjacent role that uses strengths you already have.

Exploration is not resignation. Speak with people doing the adjacent work, complete a small project, compare required credentials and test whether you enjoy the real tasks.

A reversible test produces better information than months of abstract research.

If redundancy, immigration status, regulated practice or major financial commitments are involved, add qualified human advice.

A task assessment can clarify questions and options. It cannot determine the legal, financial or personal consequences of a move.