Here's a number that should make every engineering leader uncomfortable: 21% of companies have already stopped hiring entry-level workers. Nearly half (47%) say they will by 2027. One in three expects to have eliminated entry-level roles by the end of this year.
This isn't a headline from a dystopian think-piece. It's from a ResumeTemplates.com survey of nearly 1,000 U.S. business leaders, published earlier this year.
And most of the CTOs I talk to aren't losing sleep over it — because they're the ones making the call.
That's the problem.
The Math That Feels Good Right Now
Here's the logic: AI handles the tasks juniors used to do. Why pay for three entry-level engineers when a senior engineer with an AI coding assistant does the same work? You cut training overhead, reduce management burden, tighten headcount.
The numbers look great in Q2.
Sixty-six percent of public-company CEOs, in a survey cited by Fortune this year, plan to freeze or cut hiring through the rest of 2026. They're not wrong about the short-term economics.
But they're running a calculation that only works for the next 18 months — and breaks everything after that.
What You're Actually Doing
When you stop hiring junior talent, you don't just eliminate cost. You eliminate a pipeline.
Nobody is born senior. Your current senior engineers became senior because someone hired them when they were junior. Someone gave them the tickets, the code reviews, the mentorship, the chance to ship something and break something and fix it. They got expensive because they got good — and they got good because they had years of experience learning on real problems inside real organizations.
Stop hiring at the bottom, and in five years you have a team of people who are 58 instead of 48, or burned out instead of hungry, and nobody coming up behind them who knows your systems, your culture, or your domain.
The talent pipeline is not self-replenishing. You either invest in it deliberately, or you find yourself buying expensive senior talent from competitors who did.
The IBM Counterpoint
IBM is tripling its entry-level hiring this year. While everyone else is cutting junior headcount, IBM is running the opposite play — deliberately.
IBM CHRO Nickle LaMoreaux has been blunt about the logic:
"We are tripling our entry-level hiring, and yes, that is for software developers and all these jobs we're being told AI can do."
— Nickle LaMoreaux, Chief Human Resources Officer, IBM, in Fortune
Her thesis: AI doesn't eliminate the need for junior talent. It changes what junior talent does. Instead of writing boilerplate CRUD endpoints, they're reviewing AI-generated code, validating outputs, catching hallucinations, and building the institutional judgment that no model can replicate.
The junior engineer isn't gone. The junior engineer's job description changed.
What This Means for You
If you're a CTO or VP of Engineering reading this, you probably aren't thinking about your talent pipeline five years out. You're thinking about your headcount budget for the next quarter, your deployment velocity this sprint, and whether your AI tooling is actually paying off.
That's understandable. It's also exactly why this problem compounds quietly until it's expensive to fix.
So start with what not to do. Don't confuse "AI handles this task" with "we don't need people who learn this skill." The tasks AI automates — the boilerplate a tool like GitHub Copilot now drafts in seconds — are often the same ones that build foundational judgment in early-career engineers. Remove the task, and you remove the learning. You don't get the senior engineers of 2031 without the juniors of 2026.
Then redefine the entry-level role before you kill it. IBM's move works because they redefined what junior engineers do, not just how many they hire. AI validation, output review, edge-case testing, documentation, and prompt engineering are all legitimate entry-level functions. Write the job description before you write off the category.
And the companies hiring at the bottom right now are building a moat. Go back to that ResumeTemplates.com number: a fifth of companies have already stopped. Five years from now, the organizations with institutional AI fluency embedded at every level — the kind that shows up in code-review comments, not in a vendor's onboarding deck — are going to have an enormous advantage over the ones that didn't. That fluency doesn't come from hiring contractors. It comes from people who grew up inside your org learning alongside your systems.
The short-term math on eliminating junior hiring looks clean. The long-term math doesn't.
You're not just cutting headcount. You're cutting your future.
VC5 Consulting helps engineering leaders build technical teams that can actually execute — today and three years from now. If your talent strategy needs a second opinion, let's talk.