If AI Does the Junior Work, Who Becomes the Expert?

Imagine a company that puts AI into every workflow.

AI writes the code, drafts the contracts, analyzes the reports, and produces the first version of every strategy deck. Work that once required ten people now takes three. Costs fall. Delivery speeds up. Routine errors become less common.

On any quarterly dashboard, this looks like a successful efficiency revolution.

Then, ten years later, the senior engineers, experienced lawyers, and business leaders begin to leave.

And one question suddenly matters:

Who replaces them?

The younger employees may be excellent at working with AI. But many of them have never independently diagnosed a complex failure, built an argument from incomplete evidence, or made a consequential decision without a machine supplying the first answer.

They have seen a great deal of expert-looking work.

They may not have developed expert judgment.

AI may not simply be eliminating entry-level jobs. It may be removing the route by which people once became senior.

Entry-Level Work Was Never Low-Value Work

The traditional engineering ladder was easy to understand.

Interns wrote basic code and documentation.
Junior engineers owned small modules.
Senior engineers managed the relationships between systems.
Architects and CTOs made decisions for which no clean rulebook existed.

On the surface, this was a hierarchy of responsibility.

Underneath, it was a learning system hidden inside the production process.

Beginners started with small tasks partly because their skills were limited. But those tasks also created a low-risk environment in which they could be wrong. They wrote brittle code. They misunderstood requirements. They missed edge cases. Then someone more experienced showed them what they had failed to see.

Years later, what we call “experience” is often less about knowing more rules than sensing exceptions earlier.

The numbers look fine, but something is off.

The proposal is logically elegant, but it will fail in the real world.

The person speaking sounds persuasive, but they are avoiding the only question that matters.

Those reactions are not magic. They are the residue of thousands of predictions, mistakes, corrections, and revised predictions.

In the old system, companies had to involve beginners in order to produce the work. Training people was not merely an act of generosity. It was an unavoidable by-product of production.

AI changes that bargain.

Companies can now get the output while bypassing much of the practice. Production may need fewer beginners, but society will still need experts ten years from now.

For the first time at scale, production and development are being pulled apart.

Performance and Learning Are Now Two Different Ledgers

This is the distinction that gets lost in most arguments about AI.

Doing better with AI is not the same as learning more from AI.

Learning science has long distinguished between immediate performance and durable learning: can you still perform when the support is removed, and can you transfer what you learned to a new problem?

Sometimes AI improves both. Sometimes it improves one at the expense of the other.

In a randomized study published in PNAS, students performed much better while practicing with GPT. But when the tool was removed, the group that had received direct assistance performed worse on the exam. A more carefully designed AI tutor, which prompted students to reason instead of simply supplying answers, largely reduced that damage.

A small Anthropic coding experiment in 2026 found a similar pattern. Developers who used AI scored 17 points lower on a subsequent test of independent mastery. The problem was not that they had used AI. The problem was that some had outsourced the process of understanding along with the work.

But the opposite result also exists. A study of 5,172 customer-support agents found that generative AI increased productivity by 15 percent, with the largest gains among less experienced workers. The researchers also found signs that some of the learning persisted.

So the right conclusion is not that AI inevitably makes people less capable.

It is this:

AI can be a scaffold or a substitute. The difference is whether the learner is eventually asked to stand without it.

When AI breaks a problem into steps, supplies feedback, and challenges a person’s reasoning, it can accelerate development. When it defines the problem, performs the reasoning, and delivers the conclusion, it mostly improves current output.

Companies can see output. They can measure speed, cost, and volume.

What they cannot easily see is the future expert who was never formed.

So organizations book the efficiency as a gain and leave the missing capability off the balance sheet.

I call this judgment debt.

Like technical debt, it does not hurt immediately. It comes due when senior people leave, systems fail, conditions change, or the organization encounters an exception the model has never seen.

The Most Dangerous Worker Is Competent Only When AI Works

Automation has always contained an uncomfortable paradox.

The more a machine takes over, the less often a human practices. But when the machine fails, the human is asked to intervene at the hardest possible moment—under uncertainty, under pressure, and without the benefit of recent experience.

Commercial aviation learned this problem early. Autopilot handles most stable flight conditions, leaving pilots to take control during conflicting instrument readings, severe weather, or unexpected system failures.

Knowledge work is moving toward the same structure.

Under normal conditions, AI can produce a credible architecture, summarize hundreds of pages, or generate a clear strategic recommendation. This creates a seductive illusion: if I can review expert-looking work, I must also be able to produce it independently.

But recognizing an answer and finding the problem when no answer exists are different skills.

Judgment matters when:

the data conflicts with reality;
two persuasive recommendations point in opposite directions;
a pattern that worked for years suddenly stops working;
every available option carries a cost, and a human being must still take responsibility.

If someone has never followed the full causal chain from decision to consequence, they will not know where to distrust the machine.

The most dangerous professional in the AI era is not the person who cannot use AI.

It is the person who is competent only while AI behaves normally, then becomes responsible the moment it does not.

Judgment Is Not Pain. It Is Calibrated Experience.

There is an easy mistake to make here.

If failure produces experience, perhaps we should simply make young people suffer more. Give them harder assignments. Let them fail in the real world. Treat avoidable pain as a rite of passage.

I do not believe that.

Pain is not pedagogy.

Failure without feedback may produce fear rather than wisdom. Success attributed to the wrong cause can create something even more dangerous: confidence that has never been tested.

When Daniel Kahneman and Gary Klein examined the conditions under which expert intuition becomes reliable, they identified two essential ingredients. The environment must contain patterns that can actually be learned, and the learner must receive enough timely, accurate feedback to recognize those patterns.

In other words:

Judgment is not accumulated suffering. It is experience compressed by reliable feedback.

This is why simulation works. Pilots do not need to crash an aircraft, and doctors do not need to harm patients. A good simulator does not reproduce every sensory detail. It reproduces what matters: incomplete information, time pressure, competing objectives, consequential choices, and an honest debrief afterward.

Knowledge workers in the AI era do not need manufactured trauma.

They need real responsibility with recoverable consequences.

Let a junior person make the decision. Let the outcome matter. But contain the downside so that a client, a patient, or an entire production system does not have to pay the tuition.

We Have to Reinvent Apprenticeship

If development no longer happens automatically inside production, it must be designed, funded, and measured as a separate activity.

1. Make the Human Commit First

Before opening AI, ask the person to record an initial judgment, the evidence behind it, and what they remain uncertain about.

Then bring in the model.

The useful comparison is not “my answer versus the correct answer.” It is: What did I miss? What did the model miss? Why did I change my mind?

2. Turn AI From an Answer Machine Into an Opponent

Ask it to attack the proposal, find counterexamples, represent conflicting stakeholders, and simulate extreme conditions.

The most valuable AI is not always the most agreeable one. Sometimes it is the one that forces a person to make an intuition explicit and defend it.

3. Create Fields of Reversible Responsibility

Engineers can respond to system failures in isolated environments. Young managers can control budgets with capped downside. Lawyers can own the complete strategy of a simulated case. Product managers can test decisions on a small percentage of traffic.

The point is not to let beginners watch experts make decisions.

The point is to give beginners genuine ownership inside a safe boundary.

4. Put the Debrief Back Into the Workflow

For every important decision, record four things:

What did we know at the time?
What did we expect to happen?
Why did we choose this option?
What actually happened?

Without this discipline, an organization accumulates stories. With it, experience can become a transferable pattern of judgment.

Companies also need two ledgers instead of one:

The production ledger: How quickly and effectively can someone deliver with AI?
The learning ledger: Without AI, can they explain the reasoning, transfer the lesson, and take over when the system fails?

High output with no independent capability is not sustainable productivity.

It is judgment debt.

Do Not Train Yourself to Become an Interface

Institutions may change slowly. Individuals cannot afford to wait.

If I were entering a profession today, I would deliberately do several things that look inefficient in the short term:

think independently before asking AI;
write down a prediction before seeing the answer;
regularly complete an end-to-end task without assistance;
seek work with real but limited consequences;
keep a record of mistakes, uncertainty, and changed judgments—not just finished output.

I would also resist the idea that rapid exposure to many fields can replace depth.

Judgment is often domain-specific. Seeing a little of five industries does not automatically create transferable wisdom.

A more credible path is to build one deep anchor, then rotate through adjacent domains.

First, stay in one field long enough to follow decisions all the way to their consequences. Then move outward and discover which patterns transfer—and which similarities are merely cosmetic.

AI makes it much easier to speak about a field.

It does not make it equally easy to understand one.

Knowing the difference may become one of the most important forms of self-awareness in the next decade.

Who Pays for Growth After the Efficiency Revolution?

AI has not simply destroyed the career ladder.

It has exposed something the production process used to hide: developing judgment has always been expensive. The cost was buried inside junior work, mentorship, review, and organizational slack.

Now companies can capture the efficiency without being forced to pay the training cost.

But if every firm wants to hire only experienced people, society will eventually discover that experienced people are not a natural resource that replenishes itself.

The AI era therefore requires more than new school curricula or better personal habits. It requires a new talent system: protected time for training, shared industry simulations, promotion standards that test independent takeover ability, and institutions willing to share the cost of producing the next generation of experts.

This is not an argument for preserving inefficiency. It is not an argument for refusing AI.

We should take the productivity.

But we must also accept a responsibility that used to remain invisible:

If growth is no longer a by-product of production, we have to design it as a product of its own.

Otherwise, a decade from now, our organizations may have stronger models, fewer employees, and beautiful efficiency metrics—but too few people capable of making a judgment when the model goes silent.

At that point, we may realize that we did not train human judgment at all.

We trained human dependence.