When people talk about AI and jobs, the conversation often jumps straight to replacement. I think that misses the more useful question: which parts of a job are changing, and what should we do about it now?
In this episode, I look at work as a collection of tasks. Some routine tasks will be automated. Others will become faster with AI. Work that needs judgement, accountability, trust, or a real understanding of people will still need people.
The World Economic Forum expects substantial job creation and displacement by 2030. Forecasts will change, but the direction is already visible: data literacy and AI skills are growing in value, while analytical thinking, resilience, and collaboration remain important.
That does not mean everyone needs to become an AI engineer. It means more people will need to understand where AI is reliable, where it is weak, and when to challenge its output.
I would focus on three habits:
That approach connects with how I think about wearing different hats in software development: keep one area of depth, then add the breadth that helps you own the outcome.
Job titles are difficult to predict, but these responsibilities are becoming real:
| Responsibility | What it means in practice |
|---|---|
| AI integration | Connect models to useful data, tools, and business processes. |
| AI evaluation | Test quality, cost, safety, and reliability before and after release. |
| AI assurance | Check whether outputs meet legal, security, and organisational standards. |
| Human escalation | Take over when an automated process reaches uncertainty or risk. |
| Data stewardship | Keep training and retrieval data useful, current, and properly governed. |
| Workflow design | Decide which steps belong to people, software, or a combination of both. |
My main conclusion is simple: do not prepare for one imagined future job. Build enough technical understanding to work with AI, then deepen the judgement and domain knowledge that make your work difficult to automate.
Legal Stuff
