Every CV in my inbox is a perfect fit. All keywords match. All important tools are listed. The bullet points read like the job description, but slightly rearranged.
Three years ago, this meant something. Now it tells me almost nothing.
The real interview starts when the candidate has to speak without a script. That’s where the gap keeps showing up: young people who can produce output but can’t defend or question it, and often can’t explain how they got there.
We’re not being honest about this part.
The AI-native hiring pitch
Everybody keeps saying: junior hires are AI natives. They are faster, cheaper, and more fluent with the tools. They’ll out-execute mid-level employees still doing things the old way. Hire young, hire AI-fluent, scale your startup with half the headcount.
As a startup founder, I see the appeal. Most of us are looking for places where AI can replace manual processes and where output can grow without payroll growing with it.
The hiring decision that follows from it is where things stop looking so straightforward.
What the data says
Younger candidates are more comfortable with AI on average. That’s true. They reach for it without thinking. They save real time on tedious work.
But being comfortable with a tool is not exactly the same as being good at your work.
A 2025 Microsoft and Carnegie Mellon study surveyed 319 knowledge workers and found that the more someone trusted GenAI to handle a task, the less critical thinking they brought to it. Gerlich’s research on 666 participants showed that people aged 17 to 25 had the highest AI dependence and the lowest critical thinking scores of any age group. In engineering, a recent analysis found that junior developers accept around 89 per cent of AI-generated suggestions without seriously reviewing them.
Also Read: What to actually prioritise when your board wants AI and everything feels urgent
There’s something deeper going on underneath those numbers. In a Harvard Business Review piece from February, consulting partner David Duncan notes that generative AI was helping him much more than it was helping his junior colleagues. People with experience can tell whether AI output is good. People without it can’t.
So the question isn’t whether juniors are bad at using AI. They’re not. The question is what happened to the work that used to make them good at everything else.
Where junior judgment used to come from
The boring tasks that AI now handles, like first drafts, data cleaning, call summaries, and basic reports, weren’t just boring work. They were the apprenticeship. You learned what a good campaign brief looked like by writing fifty bad ones. You figured out which client signals mattered by sitting through the call and writing the notes yourself.
Researchers at IESE have started calling this the “skills pipeline” problem. Without the grunt work, it gets hard to imagine how anyone develops the expertise to step into senior roles. The same automation that boosts productivity this quarter can leave you without strong people to put in strategic positions three years from now.
So when I watch a junior confidently present AI-generated work, the question in my head is: where did your judgment come from? Sometimes there’s a good answer. Often there isn’t.
The other half of the gap
The flip side of the over-trusting junior is the under-adopting senior. In a startup, that one costs you just as much.
Senior people bring context, scepticism, and pattern recognition that catches AI errors. But a lot of them are slow to pick up the tools. Sometimes it’s a habit. Sometimes it’s that they’ve spent years being rewarded for doing things carefully and by hand. BCG’s 2025 AI at Work survey found that while three-quarters of leaders and managers use generative AI weekly, only 51 per cent of frontline employees do. The adoption gap runs across roles, not just generations.
A small company can’t afford either version of this. The junior who trusts AI too much and the senior who uses it too little have exactly what the other is missing.
Also Read: How AI is changing what an SME team actually looks like
Rebuilding the apprenticeship loop on purpose
If AI replaces the work that built judgment, hiring for judgment won’t be enough. You have to engineer it back in. In a startup with no patience for slow on-the-job learning, that means designing for it deliberately. Here are the four things to consider.
If AI ate the work that built judgment, hiring for judgment won’t be enough. You have to engineer it back in. Four things are worth trying.
- Score judgment, not output: Evaluate junior staff based on the questions they ask before execution, not the polish of what comes out. A junior who flags three problems with the delivery is worth more than one who turns in a clean draft on the first try. The World Economic Forum calls this the shift from execution to discernment.
- Pair juniors and seniors (both ways): Seniors review juniors for missed nuance. Juniors show seniors what the tools can already do. IDC and CIO Magazine now treat this as baseline practice, not a perk.
- Put juniors near the consequences early: Client calls from week one, not month six. As CTO Magazine put it, judgment forms through “imperfect decisions, confronting trade-offs, and experiencing feedback loops.” Without exposure, it doesn’t form at all.
- Make AI adoption a KPI for everyone: Expect seniors to use AI weekly, log where it fails them, and share those failures in team reviews. Seniors engage with the tools. Juniors see what informed scepticism actually looks like. Short internal hackathons, real workflow, mixed pairs. This makes work a “forcing function”.
What does this change about hiring?
“AI-fluent junior” as a category is incomplete. Fluency without judgment gives you confident-sounding work that can come out as faulty under review. Judgment without fluency gives you careful work that arrives a week too late.
What a small company needs is not a different kind of hire. We need a different setup for the hire. Stop looking for the candidate who already has both sets of skills – those profiles are very rare. Hire for the strength they have, and build what’s missing on the job.
The companies that work this out won’t be the ones with the most AI-fluent juniors. They’ll be the ones who still know how to grow a senior.
—
Editor’s note: e27 aims to foster thought leadership by publishing views from the community. You can also share your perspective by submitting an article, video, podcast, or infographic.
The views expressed in this article are those of the author and do not necessarily reflect the official policy or position of e27.
Join us on WhatsApp, Instagram, Facebook, X, and LinkedIn to stay connected.
The post Hiring an AI-fluent junior is easy, building one with judgment is the problem appeared first on e27.