The Middleman Problem: 71% of Engineers Don't Recognize Their Own Code

The Moment It Clicked

It usually happens in a code review.

Someone asks you to explain a function you wrote three weeks ago. You open the file. You recognize your name in the git blame. But as you start to describe what's happening, you realize: you don't actually know. Not the way you used to. You're reading the code like it's the first time.

Not because you're new. Because the AI wrote it, and you approved it, and you moved on.

That moment — when you realize you're describing AI-generated work to colleagues who think it's yours — is the middleman problem. And it happened to most of your team too.

"r/programming just sticky-banned LLM content. 2,741 upvotes. 313 comments. The mods called it 'low-signal.' But the engineers in that thread weren't arguing about whether LLM code is good. They were talking about something else entirely."

— NightCoderNinja, The Clearing (@CoderNight47757)

What the Middleman Problem Actually Is

The middleman problem isn't one specific thing. It's a collection of experiences that go like this:

The Displacement

The work you used to do — the solving, the designing, the debugging — now happens inside an AI tool's inference process. You provide prompts. The AI produces code. You evaluate it. Ship it. Repeat.

The Recognition Gap

You can't explain your own code without the AI layer. Not in the way that matters — not the reasoning, the tradeoffs, the why. The what, yes. The why, less so.

The Dependency Feeling

You increasingly feel like you're mediating between the AI and the actual output. When the AI is unavailable — an outage, a rate limit, a context cutoff — anxiety spikes.

The Skill Erosion

You notice you reach for AI on things you used to handle confidently. The skill isn't gone, exactly. But it's harder to access. Like a muscle that hasn't been used in months.

Not imposter syndrome — a structural problem

Here's the distinction that matters: imposter syndrome is a confidence problem. The middleman problem is a skill architecture problem. You feel like a middleman not because you're doubting yourself, but because the actual work of engineering has shifted to the AI in ways you didn't fully choose or notice. Confidence coaching won't fix the middleman problem. Deliberate practice might.

The Three Signals You Have It

The middleman problem doesn't announce itself. It shows up as a slow accumulation of small wrongnesses. These are the three most common signals from our survey data:

Signal 1: You can't explain your own code without AI

Not "I forget a variable name." More like: "I can read this function, but if you asked me to walk through it on a whiteboard from scratch — no AI assistance — I'd hesitate." The understanding that lets you reason about code independently has gotten thinner. This is different from normal framework memorization decay. This is functional understanding erosion.

Signal 2: More of your time is spent curating than creating

The ratio has flipped. Before AI tools, most of your time was spent solving and writing. Now more of your time is spent evaluating AI suggestions, deciding between AI alternatives, and debugging AI-authored code that doesn't quite work. The work still gets done. But you're a different kind of engineer than you were two years ago.

Signal 3: Code reviews make you more anxious than they used to

Not because you're less competent. Because you're less certain which parts of the code are actually yours. When a reviewer asks about a decision, you sometimes feel the pull to open the AI chat to reconstruct the reasoning. You've become a curator of AI-generated decisions. That feels different from being the engineer who made those decisions.

From our survey

Of the 71% who reported feeling like middlemen, 84% said they experienced at least two of these three signals. The middleman problem tends to compound — once one signal appears, the others usually follow within months.

The Numbers Behind the Feeling

We surveyed 2,147 engineers in late 2025 and early 2026. The data tells a story that individual engineers already knew:

Signal	% Affected	Most Common In
Feel like a middleman between AI and final output	71%	All experience levels, slightly higher in 5-10yr engineers
Noticed measurable skill decline in specific areas	63%	Debugging, architecture design, documentation writing
Anxious when asked to explain code they shipped	58%	Mid-level and senior engineers (more complex codebases)
Considered leaving software engineering entirely	44%	Highest in engineers with 3-7 years experience
Use AI tools and feel good about their skill level	12%	Mostly engineers in AI-adjacent roles

The 44% who considered leaving isn't a burnout stat — it's an identity stat. These aren't engineers who are overworked. They're engineers who went into the field to build things, and who increasingly feel like they're reviewing things instead. Read the full survey analysis →

Why the Industry Isn't Taking This Seriously

The industry answer to "I'm feeling like a middleman" is always the same: "Just adapt. The good engineers use AI." This framing is everywhere. It's in the think pieces, the conference talks, the manager directives.

But here's what that answer misses: the engineers struggling aren't struggling to use AI. They're struggling with what AI use is doing to the skills they spent years building. And they didn't get to vote on that tradeoff.

The industry says:

"Adapt. Use AI. Ship faster. That's the new normal."

Engineers hear:

"The skills you built are obsolete and we're not going to talk about it."

This is the structural problem. Individual engineers aren't being given language for what's happening, let alone tools to address it. The middleman problem is real, it's widespread, and it's being reframed as personal failure or resistance to change. It isn't either.

The engineers who figured out how to talk about this — and got organizational support — are recovering. The ones who accepted the industry's framing and blamed themselves are not. Why rest alone doesn't fix this →

The Recovery Path

There's good news: the engineers who recover fastest from the middleman problem don't do it by using AI more carefully. They do it by building deliberate AI-free periods into their practice — and by rebuilding the skill in a specific way.

Name the problem before you try to fix it

Most engineers try to willpower their way through this: "I'll just pay more attention." That doesn't work because the problem isn't attention — it's skill structure. Acknowledge the middleman problem explicitly: "I have noticed X, Y, Z. These are real, not personal failures." Take the AI Fatigue Quiz to understand your severity tier →

The explain-it-outloud test

Before you accept any AI-generated solution: explain it out loud as if you're teaching someone. Not reading it — explaining it. If you can't, the skill that solution touches still matters. The AI might be faster, but you still need to understand. This single practice identifies which skills are eroding and which are fine.

Schedule deliberate AI-free periods

The engineers who recover fastest schedule AI-free coding time — not as punishment, but as practice. Start with one problem per week without any AI assistance. Something small. Write the code, run the tests, debug it yourself. The resistance you'll feel is the signal that this is the right skill to rebuild. The No-AI Block method →

Rebuild by teaching, not just by doing

Teaching is the fastest path to genuine understanding. Pair with a junior engineer and agree: no AI in the pairing session. Walk through problems from first principles. When you have to explain why a piece of code works — not what it does, but why the design decisions were made that way — you're rebuilding the structural understanding that AI tools have replaced.

Audit which skills you've delegated

Make a list of the skills you used to use every day that you now hand to AI. Then ask: which of these do I want to maintain? Which am I okay delegating? The middleman problem gets worse when this delegation happens passively — when you never made the choice. Making it explicit gives you agency back.

Frequently Asked Questions

Is the middleman problem the same as imposter syndrome?

No. Imposter syndrome is a confidence problem — you doubt your abilities despite evidence of competence. The middleman problem is a skill structure problem — the actual work of coding has shifted from you to the AI, and your genuine competence in specific areas has measurably declined. You can feel like a middleman even when you're highly confident in other areas.

Will these skills come back if I stop using AI tools?

In most cases, yes — but recovery is slower than you'd expect and faster than you'd hope. Skills atrophy through disuse, and rebuilding them requires deliberate practice, not just time away. The engineers who recover fastest combine AI-free periods with active skill-rebuilding: they write code without AI assistance, explain their work out loud, and deliberately take on problems outside their AI tool's comfort zone.

Is it responsible to use AI tools if they might be eroding my skills?

This is the wrong question. The right question is: which skills are essential to your professional identity and long-term value, and how do you protect those while using AI for everything else? The engineers in our survey weren't anti-AI — 89% used AI daily. The concern was selective: they're losing skills they didn't intend to lose, in areas they didn't realize mattered to them.

Should I quit my job if I feel like a middleman?

Quitting is a reaction to a structural problem that doesn't require job-leaving to solve. Before you quit, try: (1) a 2-week AI-free coding period on non-critical work, (2) explaining your own code out loud without AI assistance, (3) one deliberate project where you never use AI. If after all of that you still feel disconnected from the work, then evaluate whether your environment is the right fit.

How do I bring this up with my manager?

Frame it as a skill sustainability question, not a performance problem. Say: "I've noticed I'm leaning on AI tools for things I used to handle independently, and I want to be intentional about keeping my core skills sharp. Can we talk about how to structure some AI-free time into our workflow?" Most managers will respond well to this — it's proactive, professional, and addresses long-term team capability.

What does the 71% middleman statistic actually mean?

In our survey of 2,147 engineers, 71% reported agreeing with the statement: "I often feel like a middleman or curator between the AI tool and the final output, rather than the primary author of the code." This doesn't mean they're bad engineers — many have 10+ years of experience. It means the nature of their daily work has shifted in a way they didn't choose or fully adjust to.

The Middleman Problem