Every few weeks another headline claims AI has wiped out most entry-level programming jobs. Two-thirds gone. Junior developers obsolete. The end of the career ladder.
Most of it is nonsense — inflated numbers and vibes dressed up as analysis. But underneath the noise there is a real signal, and it's more useful (and more actionable) than the doom-posting. I went looking for the data that actually holds up. Here's what it says, and what I think you should do about it.
Skip the job-posting counts — they're misleading, because a "junior" role advertised and then filled by a senior still shows up as a posting. The more reliable measurement comes from payroll data: who's actually employed and getting paid.
In 2025, Stanford's Digital Economy Lab analyzed exactly that, and found something striking. Employment for software developers aged 22–25 fell by nearly 20% from its late-2022 peak. That's real, and it's significant.
But the number that matters most isn't that one. It's the comparison sitting right next to it: over the same period, in the same highly AI-exposed roles, developers aged 30 and older didn't decline at all. Their employment grew.
Junior developers down. Experienced developers up. In the same jobs, at the same time.
Read carefully, because this is where most takes get it wrong in both directions.
It does not mean "AI is killing software engineering." Experienced engineers are doing fine — better than fine. And it doesn't even cleanly mean "AI killed junior jobs," because there are confounds tangled in there: the industry over-hired during the pandemic boom and spent the next few years correcting, and interest rates reshaped hiring too. Anyone selling you a clean "AI did it" story is overselling.
But it does point at something specific and hard to argue with: the pressure is concentrated at the entry point, not across the field. The thing under threat isn't "being a developer." It's "being a junior developer" — the rung where the work is most well-defined, most low-context, and most similar to what AI now does cheaply.
Meanwhile something like 84% of developers now report using AI tools (per the 2025 Stack Overflow survey). The tool that made the bottom rung more crowded is now in nearly everyone's hands. The junior's traditional value — being the fast hands for the well-scoped, low-context task — is exactly what got commoditized.
If the exposed position is "junior" and the protected position is "experienced," then the single most valuable thing you can do for your career right now is stop being interchangeable with what AI does well, as fast as you reasonably can. Not by working longer hours. Not by memorizing more syntax — the machine has all the syntax. By becoming the thing the machine isn't: someone with judgment, context, and the trust of the people around them. Someone who understands why the code exists, can tell when a plausible-looking answer is wrong, and can be relied on when the problem isn't well-defined.
That, not coincidentally, is roughly the definition of a mid-level developer. Which means the move that protects you in the AI era and the move that advances your career are the same move: get off the bottom rung, deliberately and quickly.
A few things that genuinely move you from "interchangeable" toward "trusted," starting now:
None of that is a trick, and none of it is fast in the "one weekend" sense. But it's the difference between a developer the market is unsure about and one it's actively protecting.
The bottom rung is more exposed than it's ever been. Let that be the reason you stop standing on it.
I wrote a short book on exactly this — the concrete habits that get a developer from junior to mid, fast, in the AI era. It's called Getting from Junior to Mid, Fast. But honestly, the four bullets above are a real start on their own — no purchase required.
What's your read on the data? Are you seeing this play out on your own team? I'd genuinely like to hear it in the comments.