Why We Should Be Hiring More Junior Engineers, Not Less
AI has changed the economics of experience in software engineering
Over the last year, I’ve heard the same refrain from founders, VPs, and hiring managers over and over again:
“We can’t afford juniors right now. We need senior engineers who can move fast.”
I think that instinct is increasingly wrong.
In fact, I believe we should be hiring more junior engineers — not fewer — especially in an era where AI-native development tools have fundamentally changed how software is built and learned.
Software Engineering Is Easier to Pick Up Than Ever Before
Learning software engineering has never been more accessible.
AI tools like Claude, Cursor, and GitHub Copilot don’t just autocomplete code. They:
- Explain why a solution works
- Walk through tradeoffs between approaches
- Offer instant feedback
- Perform code reviews that, frankly, are more thorough than many human reviewers
A junior engineer today can ask “why is this bad?”, “what’s the more idiomatic approach?”, or “what edge cases am I missing?” — and get a high-quality answer immediately.
That kind of feedback loop simply didn’t exist a few years ago.
AI-Native Juniors Are Underrated
Most companies are currently optimizing for senior engineers who use AI to 10x or 100x their productivity.
That makes sense — but it’s only half the picture.
AI-native junior engineers, trained from day one with these tools, can be extraordinarily effective. They’re not unlearning old habits. They’re not resistant to AI assistance. They’re used to explaining their thinking, validating outputs, and iterating quickly.
In many cases, the gap between a junior and senior engineer has narrowed dramatically — especially for product-focused, execution-heavy work.
Juniors Need Coaching — But Less Than You Think
Yes, junior engineers still need guidance.
They benefit from learning:
- How to keep PRs small
- How not to change too many things at once
- How to reason about maintainability and long-term cost
- How to understand what the AI is generating instead of blindly accepting it
But here’s the key shift:
They need far less handholding than they did before.
AI tools handle much of the mechanical knowledge transfer that used to consume senior engineers’ time. That frees seniors up to focus on architecture, system design, and high-level decision-making — where they add the most leverage.
There’s a Massive Pool of Untapped Talent
Right now, there’s a huge glut of unemployed or underemployed computer science grads.
These are motivated, capable people who want to build, learn, and prove themselves — and many companies are simply ignoring them.
That’s a mistake.
The talent pool is larger, more AI-literate, and more eager than it’s ever been.
A Real Example: Betting on Potential Works
One of the best hires I’ve ever made was Lucy.
When I hired her, she had zero professional engineering experience. Eight months later, she’s become an indispensable part of the team — shipping real features, owning complex work, and raising the bar for everyone around her.
What made the difference wasn’t pedigree or years of experience. It was curiosity, work ethic, and a willingness to put in the hours to learn.
Those traits, combined with modern AI tooling, are incredibly powerful.
Especially for Startups: This Matters
For small startups with tight budgets, this is even more important.
Senior engineers are expensive and scarce. Junior engineers are abundant, affordable, and increasingly capable.
Hiring juniors isn’t charity. It’s not a favor.
It’s a strategic decision — one that can compound over time.
Final Thought
If your hiring strategy still assumes junior engineers are a drag on productivity, it’s probably outdated.
The tools have changed. The talent pool has changed. The economics have changed.
Don’t ignore one of the largest, most motivated pools of technical talent available today — especially when the upside has never been higher.
