Will AI Replace My Job? Find Where It Gets Your Work Wrong
Lists of jobs AI will replace are about jobs in general. A ten-minute test shows where AI gets your own work wrong, and why that gap is your value.
On this page
Nobody told you your job changed. You just feel it. The usual answers come as lists: jobs AI will replace, a percentage of tasks "exposed", a forecast for the end of the decade. They are about jobs in general, and you don't do a job in general. The question you actually lie awake with is narrower: which parts of my work still need me? You can answer that today, in ten minutes: ask AI a real question from your work, and write down where its answer is wrong. That gap is what you're worth now, and seeing it written down is the point.
The step: two lines
Pick a question you were asked this week. Not a textbook question; a real one, with the real constraint that made it awkward. Ask your AI assistant. Read the answer slowly.
Somewhere you'll think: that's not how it actually works. Stop there and write two lines:
AI said: ...
What really happens: ...
That's the whole exercise. Do it once today.
An example
Illustrative, not from a real company:
AI said: Accrue the invoice in the period the service was received.
What really happens: We accrue it, but only after the budget owner confirms the amount by email, because the purchase order is usually out of date by the time the invoice arrives.
The AI answer isn't wrong. It is the rule. What it can't know is the part that makes the rule work in your building: who confirms, through which channel, and why.
What the gap usually contains
When I look at where systems stop and people carry on, the same few things keep turning up. I wrote them out in The Hidden Work Around Enterprise Systems, and they are the same things AI gets wrong about your job:
- The approval that lives somewhere else. The real decision happens in an email or a hallway, not in the step the documentation describes.
- The person everyone asks. If that person is you, AI is describing the process without its most important part.
- The exception that happens every week. Documentation describes the normal case. Your week is mostly the other one.
- Context from several places. You know the answer because you have seen three systems and one spreadsheet. AI saw a description of one.
None of these is a skill you'd put on a CV. All of them are the reason things work when you are in the room.
What to do with your two lines
Keep them in one file. One pair a week is enough. After a month you have three things you didn't have before:
- A map of what to hand over. Whatever AI got right is work you can stop defending and start delegating to it; two lists from one weekly task turn that into what to learn next. That frees the hour you didn't have.
- An answer for the meeting. When leadership asks what AI means for the team, five real pairs are better than any opinion.
- The first page of your plan B. Each pair is a small, concrete proof of what you know. Written up without company details, it is something a stranger can find and judge, the same way the question you answer ten times becomes a guide.
When the test misleads you
- A vague question gets a vague answer you can't fault. Ask the real question, with the real constraint, or the test tells you nothing.
- "AI was wrong" is not "I'm safe". Models get better, and the gap moves. Run the test again every few months; the movement is the information.
- The parts it got right are not an insult. They are the parts to hand over. The people who come out ahead are the ones who stop doing those by hand first.
- Don't paste what shouldn't leave the building. Use the assistant your company approves, or take names, amounts and client details out of the question.
You don't need a forecast to sleep better. You need two lines. Write them today.
Frequently asked questions
(3)
Will AI replace my job?
Nobody can answer that honestly for a whole profession, and lists that try are about jobs in general, not yours. What you can find out today is which parts of your own work AI already handles well and where it gets your work wrong. Ask it a real question from your job and write down the gap between its answer and what really happens. The parts it handles well are worth handing over. The gap is where your experience still decides the outcome.
Which parts of my job are safe from AI?
No part is safe by definition, and the line moves as models improve. Today, the parts AI gets wrong are usually the ones that live outside any document: the unwritten rule about who really approves, the exception that happens every week, context spread across several systems, and judgment about people. Test your own work every few months; the movement of the gap tells you more than any forecast.
What do I say when leadership asks what AI means for our team?
Bring evidence instead of a forecast. Run the two-line test on five real questions from your team's work and show the results: what AI got right and could take over, and what it got wrong and why. That turns a vague question into a concrete conversation about which work to hand over and which to protect.