AI and work
AI can make more jobs than it destroys
By Oussama Labrahmi 路 路 6 min read

Geoffrey Hinton won a Nobel Prize in 2024 and is known as one of the "godfathers of AI". In 2016, he said we should stop training radiologists, because within five years AI would read medical images better than any doctor.
We're almost in 2027, and AI has become very good at reading scans. In a Swedish trial of more than 80,000 women, AI-supported mammogram screening found cancers at a similar rate to two human readers, with 44% less reading work.
Radiologists did not disappear. They're still being trained, and in the US the shortage is projected to last until 2055.
So why? If AI does so much of the reading, why do we still need radiologists, and why do we need more of them? The answer I keep coming back to is Jevons Paradox.
What is Jevons Paradox?
In 1865, an English economist called William Stanley Jevons wrote a book about coal. Engineers had made steam engines much better, and the new engines used far less coal to do the same work. You would expect the country to burn less coal.
It was the opposite. Coal use went up, a lot. The engine was now cheap to run, so everyone wanted one: more factories, more trains, more ships. Each engine used less coal, but there were so many more engines that the total went up.
Before
High cost, limited adoption
After
Lower cost, much wider adoption
Back to radiology. As reading a scan gets faster and cheaper, doctors can ask for more scans. Hospitals can screen people who are not sick yet. Scans nobody would pay for before start to make sense. More scans means more results to check, more reports to sign, and more patients who need a real doctor to talk to. The machine is fast, but the work grows even faster.
AI isn't the only cause. People live longer, and imaging is used for more conditions than ever. But cheaper reading pushes in the same direction.
What other fields does this apply to?
Many. I'll use the one I know: software development.
I've built software for clients for six years, mostly on the frontend. Five years ago, a small app or website cost real money and took weeks. Only companies with serious budgets could pull it off. A small hotel in Morocco, a local shop, a gym, a co-working space: they ran on WhatsApp and paper. Nobody built software for them, because it was too expensive.
Now AI writes a lot of the code. I use it every day. An app that took me weeks to build by hand now takes a weekend. The cost of building software is going down fast.
So what happens? Not less software. More software. The hotel wants a WhatsApp booking agent (I built one). The shop wants its own online store. The gym wants a dashboard. These were too small to be worth it.
Big companies work the same way. They all have a long list of projects they want but never start: internal tools, features for a small market, rebuilding a legacy system. Most of these die on the list because they cost more than they bring back. When AI makes them cheaper to build, many start to make sense. The company says yes to more projects, and those projects need experienced developers.
That's the good part of the story. Now the part that's hard to explain.
So why are people still getting laid off?
Because the jobs being cut and the jobs being added are not the same jobs.
50K+
Tech job cuts announced in Q1 2026
Challenger, Gray & Christmas+30%
Software engineering openings, reported increase
TrueUp, via Business Insider-20%
Jobs for developers aged 22 to 25, against the late 2022 peak
Stanford study, ADP data
In the first three months of 2026, tech companies announced 52,050 job cuts. In about the same period, one tracker showed software engineering openings up about 30%, at a three-year high. Both are true at the same time. Other data is less rosy: Indeed shows postings up about 15% since early 2025, and still about 27% below 2020.
The growth is in senior engineers and AI work. On Indeed, senior roles were 71% of the rise in US software postings from May 2025 to May 2026, while entry-level postings across all jobs fell 7.5%.
A Stanford study found that software developers aged 22 to 25 had about 20% fewer jobs in July 2025 than at the peak in late 2022. Older workers were mostly fine. The study's August 2026 update says the gap has widened, mainly because companies hire fewer young people, not because they fire more of them.
It makes sense when you think about it. The simple tasks juniors used to do are the same tasks AI does best. Companies are also moving money: less for salaries, more for AI tools and servers. So they cut in one place and hire in another.
And be careful with the word "AI" in layoff news. Companies choose the reason they give, and "AI" sounds better than "we hired too many people in 2021". Challenger counted AI as the stated reason for about 24% of announced US job cuts through July 2026, and 40% in May alone. Those numbers count what companies said, which may not be what happened.
So what does this mean for us?
Hinton was right about the skill. AI can read scans, and it can write code. I think he was wrong about what happens next. He has said himself that he spoke too broadly in 2016. When something gets cheap, people don't do the same work with fewer people. They ask for more.
I'm not going to lie and say I'm fully relaxed. I'm a developer, and I use these tools every day, so I see how fast they are getting better. And I know the market is hard right now, especially for people who are just starting. That is real, and Jevons Paradox does not fix it for them this year.
But I also see the other side. Every month, I see more things that someone wants to build than people who can build them. The job is changing. Typing code by hand is becoming the small part. Knowing what to build, and checking that the machine did it right, is becoming the big part.
Radiologists did not lose the game. They moved from finding the problem to deciding what to do about it. I think developers are doing the same thing right now, and the future is for the ones who adapt.
Questions
What is Jevons Paradox?
Jevons Paradox is when making something cheaper or more efficient raises its total use instead of lowering it. William Stanley Jevons described it in 1865, after better steam engines led Britain to burn more coal.
Did AI replace radiologists?
No. AI reads some scans very well, but the US still has too few radiologists. Scan volumes keep growing, and someone still has to check results, sign reports and talk to patients.
Will AI replace software developers?
Not the whole job, in my view. AI writes more of the code, and cheaper code means more projects. The work moves toward deciding what to build and checking that it's right.
Why are there tech layoffs if software job openings are up?
They are different jobs. Openings are growing for senior engineers and AI work, while entry-level postings fall. Companies are also moving money from salaries to AI tools and servers, so they cut and hire together.
Are junior developers hit hardest by AI?
So far, yes. A Stanford study found developers aged 22 to 25 had about 20% fewer jobs in July 2025 than at their late 2022 peak, while older workers held up.
Sources
- Hinton acknowledges mistake in predicting AI replacement of radiologists, AuntMinnie
- AI-supported mammography screening in the MASAI trial, The Lancet Oncology, via PubMed
- Current radiologist shortage projected to persist to 2055, HealthDay
- AI was supposed to replace radiologists, but now they are in more demand than ever, WPVI
- Jevons paradox, Wikipedia
- March 2026 job cuts report, Challenger, Gray & Christmas
- July 2026 job cuts report, Challenger, Gray & Christmas
- AI remains top reason for US job cuts in May, Fox Business
- AI isn't killing software jobs: TrueUp openings data, Business Insider
- AI and job postings: from destruction to creation?, Indeed Hiring Lab
- The labor market is tilting toward seniority, Indeed Hiring Lab
- Canaries in the Coal Mine? Six facts about the recent employment effects of AI, Stanford Digital Economy Lab
- Yes, AI is affecting employment. Here's the data, ADP Research
Last checked .
