Claude Code vs. Your ML Career: A 2026 Reality Check
Juniors down 20%. Seniors up 12%. Here's what's really happening — and what to do about it depending on where you are.
I’ve been getting a lot of DMs lately, and they’re almost all some version of the same question: “Man, are all the jobs going to be gone? What does the future actually look like for someone like me?”
Sometimes it’s from a junior who gets ghosted after four rounds. Sometimes it’s from a friend from my Meta days who just got told their team is “not backfilling.” Sometimes it’s a student wondering if the whole field is collapsing before they even get their degrees.
And honestly, I get it. The takes out there are both scary and uninformed. They range from “AI will replace all engineers in 12 months” on one side. “AI just fails on simple tasks like counting r’s in strawberry,” on the other. After 15 months of watching this play out at Roku, interviewing candidates, and using these tools every single day, I would say that both are wrong. Here’s what I actually think is going on:
IMO, the 2026 ML job market is not dying. It has split into two. People in the first half are in real trouble. The other half may have the best market ML engineers have ever had. The whole game right now is figuring out which half you’re in, and making the moves that land you on the right side of that split.
A while back, I wrote Why LLMs Won’t Replace Programmers, and followed it up with a 2025 careers guide. Both still hold up — go read them if you haven’t. This post is about the stuff that’s changed around over the last 15 months, and what I’d actually do about it if I were you right now. Let’s get into it.
What I’m Actually Seeing
Let me paint you the picture I’ve been watching play out.
A Stanford study by Brynjolfsson and team using real ADP payroll data found something jarring: devs aged 22–25 are down about 20% in employment since late 2022. Devs aged 30+ in the same kinds of roles? Up 6–12% over the same window.
Can’t really say for sure, but at least this is my lived experience. I am getting more calls than usual, as you can see below. Most of these came in the last 2 weeks:
Pair that with what CEOs have been saying on earnings calls, which I don’t think people have fully absorbed yet:
Honestly, it’s pretty much in your face once you gather the courage to see it. The agents have gotten really good at the exact things juniors spent their first three years doing — boilerplate services, implementing someone else’s paper, fine-tuning on clean data, plumbing around a senior’s design.
So companies have just stopped hiring juniors and using agents to give seniors the kind of leverage they used to get from a small team. I see it happening across the orgs and folks I talk to.
That said, the productivity claims flying around from CEOs and vendors are wildly overstated in my opinion. I mean, some days Claude Code seems to double my output. Other days, I have to spend like 45 minutes fighting it when it goes into a dark corner and takes an unexpected turn while coding, which I could’ve done in 5 minutes.
I have seen enough folks fudging benchmarks and lying on LinkedIn threads to trust them. And honestly, you will really need to work with these tools for at least a good few weeks to know the actual picture, their capabilities, and the impact they could bring.
What Agents Took. What They Can’t Touch.
So, with that out of the way, the simplest way I’ve found to think about your career in 2026 is this → some skills just got way cheaper because agents got really good at them. Others got way more valuable because agents still can’t do them — and somebody has to, and that somebody needs to be you.
Look at what you actually worked on last week. Which column does most of it belong in?
