The Apprenticeship Engine: Building Talent When AI Takes the Training Work

By Kenechukwu Ezekwem, PhD

Something is happening to the bottom rung of the career ladder, and it deserves more honesty than it usually gets. AI is taking on the routine entry-level work that once doubled as on-the-job training. The apprenticeship no longer comes bundled with the job, so leaders have to build it on purpose.

For about two years, organizations have been handing routine knowledge work to AI: first drafts, basic analysis, simple code, early research, meeting summaries and data cleanup. Each handoff looks like an efficiency gain. In the short term, it often is. But that same work was also how people learned. We rarely called it training. We called it the job.

This is the quiet talent development problem at the center of the AI transition. As routine work moves to machines, the work that helped beginners become capable is moving with it. If that learning loop is not rebuilt, the result will not only be fewer entry-level seats; it will be a thinner bench of people ready for complex work 5 or 10 years from now.

The Work We Automated Was Also the Work That Taught

Skill is built through guided struggle. Someone who can already do the work stands near someone who cannot yet do it, lets them try, corrects them and gradually steps back. People become skilled by doing the work badly, then less badly, then well.

That is not a verdict against technology. It is a warning about the learning system around it.

The early labor market signals point in the same direction, though they should be read carefully. The Stanford Digital Economy Lab found that early-career workers ages 22 to 25 in the most AI-exposed occupations experienced roughly a 13% to 16% relative decline in employment, depending on the version of the working paper cited. SignalFire’s 2025 “State of Tech Talent Report” states that new graduates accounted for just 7% of hires at major tech companies. Revelio Labs found that highly AI-exposed entry-level roles declined more than 40% between January 2023 and July 2025.

None of this proves that AI is the only cause. Interest rates, sector-specific slowdowns, overhiring during the pandemic and normal business cycles all matter. But the mechanism is real: When the machine performs the routine parts of work, the beginner may lose the repetition, feedback and judgment-building struggle those tasks used to provide.

The lesson is not that AI makes people less capable. It is that capability does not grow automatically when the tool does more of the thinking.

The Seniority Cliff

This should matter to leaders even if they are not focused on early-career hiring. If beginners do not wrestle with foundational problems, they do not build the judgment those problems once taught. Run that forward, and the risk is not merely a shortage of juniors. It is a shortage of seniors.

Imagine a hospital that adopts a surgical system so capable that residents rarely touch a patient in their first years. Throughput rises, costs fall and the quarterly numbers look good. Now run the tape forward 15 years, when today’s senior surgeons retire. Who operates?

If a problem comes, it will not be the machine’s fault. It will be ours for letting the residents stop practicing. Many organizations are now making a white-collar version of that trade without measuring the loss.

Why the Obvious Fixes Fail

The first tempting answer is to protect entry-level work by keeping routine tasks human. That is the wrong answer. Not all junior work was good training. Some of it was just busywork, and AI should remove it.

The goal is not to preserve spreadsheet grind, endless formatting or draft work that no one reads. The goal is to preserve what was hidden inside the better parts of that work: real stakes, repetition, feedback, expert modeling and gradually increasing responsibility.

Removing low-value work is progress. Removing the feedback-and-practice loop is the problem. Leaders should not protect old tasks simply because they are old. They should protect the conditions that turn effort into judgment.

The second tempting answer is to train harder: more courses, more content, more learning platforms. That answer is incomplete. Skill comes from doing real work with guidance. Content can support that process, but it cannot replace it.

Build the Apprenticeship on Purpose

As AI takes over routine work, the accidental apprenticeship goes with it. Leaders should stop waiting for learning to happen as a byproduct of the job and start engineering the conditions that produce expertise.

I call this system the Apprenticeship Engine. It is not a retreat from AI. It is a way to use AI while keeping humans inside the learning loop that builds judgment.

The principle is straightforward: Durable skill grows through real work, expert guidance, feedback and increasing autonomy. That principle is not new. What is new is the urgency. The workplace used to apply this principle accidentally because beginners had to do real work to be useful. AI is weakening that default, so the system now has to be deliberate.

The Five Design Rules

The engine is simple: Put people in real work, surround them with expert judgment and make progress visible.

Real work, not exercises. Put early-career employees on live problems with genuine stakes: a real customer issue, model, dataset, process redesign, risk question or business decision. AI should be part of the work, not banned from it. The human should use the tool while still doing the judgment-heavy tasks: framing the problem, checking assumptions, validating outputs, making tradeoffs and explaining decisions.

A clear expert in the loop. Each team needs an experienced mentor who models the work, coaches it and then gradually steps back. The effects are real, not magical; they depend on protected time, clear expectations and a manager who treats mentoring as work rather than volunteerism.

Small teams and a fixed cadence. Keep teams small enough for real observation and feedback, usually four or five people, and run cycles long enough to learn but short enough to measure, often two to four months. A cadence creates rhythm: attempt, review, correct, repeat.

A bar to clear. Define what readiness looks like before the cycle begins. Do not use seat time or course completion as proxies for capability. Make participants demonstrate the ability to do harder work with more autonomy.

Measurement an executive would respect. Track time to productivity, retention, internal mobility, promotion, quality of work and whether graduates can now do work that previously required a senior hire. The Apprenticeship Engine should be measured by capability created, not content consumed.

How to Start in One Quarter

You do not need a transformation program. You need one honest pilot.

Choose one function where leaders are tempted to reduce junior hiring because AI now handles the starter work. Put three to five early-career people on a real problem the function needs solved.

Assign one respected senior person and make mentoring count as work, not a favor squeezed in around the real job. Define the bar in advance: What should graduates of the cycle be able to do that they could not do before, and what evidence will prove it?

Then measure against your normal ramp. Did people become productive faster? Did quality, retention or engagement improve? Did the mentor spot people ready for harder work? If yes, expand. If no, you spent one cycle and learned something useful.

The organizations that do best in the next decade will not be the ones that automate the most. They will be the ones that pair what machines now do well with people deliberately taught to do what machines cannot yet own. That second half used to take care of itself. Now it has to be built.

Kenechukwu Ezekwem, PhD, is a clinical assistant professor of management and analytics at New York University’s School of Professional Studies and an American Management Association faculty member. He founded the SPS Research, Prototyping, and Production Pods, an applied AI research group where early-career analysts build publishable research and deployable prototypes in parallel. His work focuses on management analytics, workflow automation and the thoughtful use of AI to improve decision making.

Frequently Asked Questions

What is the Apprenticeship Engine?

The Apprenticeship Engine is a deliberate system for building skill through real work, expert guidance, feedback and increasing autonomy while still using AI to accelerate the work.

Why does AI create a talent development problem?

AI is taking on routine entry-level tasks that once helped beginners learn through repetition and correction. When that work disappears, so does part of the learning loop.

Should organizations protect entry-level work from AI?

The goal is to preserve the conditions that build judgment: real stakes, repetition, feedback, expert modeling and increasing responsibility.

Why is training alone not enough?

Courses and content can support development, but skill comes from doing real work with guidance. Without reinforcement, training often fails to change workplace behavior.

How can leaders start?

Leaders can start with one pilot: a function affected by AI, put three to five early-career employees on a real problem, assign a senior mentor, define a clear readiness bar and measure whether capability improves.