Why cutting junior talent could backfire

Anyone spending time inside a company right now can feel it. There is a growing assumption shaping decisions at the highest levels. AI will drive efficiency and therefore companies are expected to reduce headcount.

It sounds logical. It sounds disciplined. But it is also incomplete.

I have been in boardrooms where AI is discussed as both an opportunity and a justification. Leaders talk about transformation, and in the same breath talk about reducing headcount. The connection feels automatic, as if one must follow the other.

Here’s what’s missing from the conversation: What is the work we actually want done, and how should it be done?

THE EFFICIENCY SHORTCUT

Labor is the largest line item for most companies. When AI enters the picture, it is natural to look there first. If technology can do more, we must need fewer people.

But there is little evidence that AI is delivering productivity at a level that justifies the speed of workforce reduction. What I see instead is pressure, particularly in public companies, to show immediate returns on significant AI investments.

Cutting travel or discretionary spending does not move the needle. Headcount does. So it becomes the most visible lever.

THE ANALYST PROBLEM

Recently, I spoke with a young analyst who just finished a rotation program. His advice was simple: Do not let new hires rely on AI too early.

That runs counter to what most CEOs say. Every company wants employees to be AI-fluent. However, if you rely on AI before you understand the business, you lose the ability to judge the work. You may produce answers faster, but you cannot assess their quality, relevance, or risk.

Judgment is built through repetition. By doing the work yourself, you learn what good looks like, where things break, and how decisions hold up in practice. Without that foundation, you defer to AI instead of using it as a tool.

THE CODE REWRITE

I recently heard about a company that used AI to rewrite its entire code base over a single weekend. It was a 10-year-old system. What would have taken months, possibly years, was done in days.

On the surface, that sounds like the future. But the story did not end there.

Once the code was rewritten, the company still needed the original engineers to validate it. They had to determine whether it would hold up, whether it introduced new risks, and whether it actually worked in the real world. The writing speed was impressive. The certainty was not.

It required far more human input and judgment on the back end than expected. That is the part of AI adoption we are underestimating. Output accelerates, but the demand for judgment and deep assessment is only growing.

THE RISE OF DEVELOPMENT DEBT

At this moment, if you reduce junior hiring or eliminate early-career roles because AI can handle entry-level tasks, be clear about the tradeoff. You save money but also remove the pathway that develops the experienced talent, the talent your organization needs to rely on for judgment over time.

This is the greatest long-term risk. I call it development debt.

A gap emerges when cutting off that early pipeline. You will have a workforce that can generate but not evaluate answers. Your organization can move quickly, but lacks the context to know whether it should.

AI cannot replace experience or replicate the pattern recognition coming from years of seeing how decisions play out. Someone still needs to say, “This works here,” or “This does not.”

THE APPRENTICESHIP WE ARE LOSING

Most learning early in a career comes from proximity to leaders and experts within the firm. Listening to how decisions are made. Watching how problems are framed. Seeing what tradeoffs leaders are willing to make.

That kind of learning is slow. It is, by definition, inefficient. But it is effective and essential. If we replace that with AI reliance, we skip the stage where judgment is formed.

A better approach requires intention. Give new hires time to observe, ask questions, and understand how the business actually works. Then introduce AI as a tool to enhance that understanding.

One of the most effective models is pairing people who are strong in different ways. Junior employees often bring speed and comfort with technology, pushing for new approaches. More experienced employees bring context and perspective, challenging whether different approaches make sense. The outcome of working together is better than either working alone.

This breaks down if companies cut off their junior talent pipeline.

SLOW DOWN TO MOVE FORWARD

The instinct right now is to move fast. Adopt quickly. Show results. But slowing down is the more strategic move.

Instead of asking how many people can be replaced, ask how work should be redesigned. What should be done by humans. What could be done by machines. And where the combination creates something better.

There are three things leaders can do:

First, redesign the work before reducing the workforce. Be explicit about where human judgment is essential, where AI can augment, and where it can fully take over.

Second, use natural attrition and role shifting instead of immediate layoffs. This creates space to evolve the organization without cutting off future capability.

Third, treat AI adoption as an experiment, not a conclusion. Test, learn, and validate before making permanent structural changes.

That kind of discipline is what builds something more resilient and sustainable.

A DIFFERENT KIND OF ADVANTAGE

There is no question that companies need to differentiate and disrupt themselves. That requires creating what does not yet exist, and that still depends on people. People are the differentiator, not AI.

AI is widely accessible. What sets organizations apart is judgment. The ability to question the data, imagine real-world alternatives, and make decisions in context.

Companies investing in that capability development, even when it initially feels slower and less efficient, will stand apart over time. In the end, AI may change how work gets done, but it does not replace the need for people who understand what the work should be.

Tami Rosen is an executive, board director, and strategic advisor to finance and technology companies.

View the full article