"I feel like a middleman in my own work."
That sentence has come up more than any other in the conversations The Clearing has had with engineers over the past two years. Not "I am scared AI will replace me." Not "I am not good enough." This: something you built is happening through you rather than by you.
It is a specific feeling. You have the title. You review the PRs. You ship to production. But the authorship — the quiet sense that "this thing is mine because I made it" — has gone quiet.
If you have felt this, you are not alone. And you are not broken. This is a new kind of occupational friction affecting engineers across every level and stack. It is called the middleman problem, and understanding it is the first step to fixing it.
What the Middleman Problem Actually Is
The middleman problem is the gap between being the person who produces code and being the person who understands it. It does not happen when you are slacking off. It happens when you are working hard — shipping features, closing tickets, shipping more — but doing it through AI tools you have become dependent on in ways you cannot fully see.
Here is what it looks like in practice. You open a new task. You open AI. You prompt. AI generates. You review. You tweak. You merge. You move on. The feature ships. The feature is yours. And yet — if someone asked you to rebuild that feature from scratch, or explain every decision that went into it, or debug it at 2am when it is broken in production — you would have to go back to the AI to remember what it did.
The work happened to you. You facilitated it. You did not author it.
The gap between shipping and owning is not a character flaw. It is the predictable result of using tools designed to make building easier while removing the friction that used to be the training.
That friction — the stuck moments, the hard problems, the real struggle — was the training. It built your skills. It built your confidence. AI removes that friction. That is the point. But it also removes the training ground. And most engineers have not noticed the exchange rate.
Not Imposter Syndrome — Something Different
People often confuse the middleman problem with imposter syndrome. They look similar from the outside. Someone who feels like a middleman in their own work might sound like someone with imposter syndrome — "I do not actually know what I am doing." But the cause is different, and the fix is different.
Imposter Syndrome
A confidence problem. You feel like a fraud despite evidence of competence. You downplay your achievements. You fear being "found out."
The Middleman Problem
An ownership problem. You did the work and earned the title, but the work happened to you rather than through you. Your confidence is well-founded — the gap is real.
Imposter syndrome says: "I am not as good as people think." The middleman problem says: "I am not as connected to this work as I used to be, and I can feel it." Both are uncomfortable. Only one has a structural fix available.
Why It Gets Worse Before It Gets Better
Here is the dangerous part: the middleman problem compounds. The longer you use AI tools without maintaining your own practice, the larger the gap grows — even as your output increases. Your velocity goes up. Your ownership shrinks.
This shows up in ways that are easy to rationalize away:
- You cannot explain the last three features you shipped in enough detail to debug them alone
- When asked how something works, your instinct is to show the prompt, not the solution
- You have stopped starting side projects because AI makes it "easy" — and they never feel like yours
- You feel productive all day but empty at the end of it
- Your colleagues ask how something works and you have to check the AI output to answer
- When AI is unavailable for even an hour, you feel genuinely stuck
The compounding effect: Each day you use AI to close the gap between confusion and code, you also widen the gap between your skills and your output. Velocity compounds in the direction of the tool. Ownership compounds in the direction of loss. At some point, you look around and realize you can ship anything but own nothing.
Who Feels This Most
The middleman problem does not hit everyone equally. Three groups feel it most acutely:
Senior engineers who built their identity on craft
If you spent a decade building real competence — if you know what it feels like to be genuinely stuck and genuinely capable — the middleman problem is disorienting in a specific way. You are not doubting your competence. You are mourning the relationship with it. The work used to flow through you. Now it flows around you. You still have the skills. But the path between the skills and the shipping has been replaced by a prompt.
Junior engineers building careers on AI-assisted foundations
Junior engineers who started their careers with AI tools available face a different version of the same problem. They never had the period of genuine struggle that would have built their foundation. They have output without the reps. Their career is built on a building they have not actually seen constructed from the inside. When the gaps show up — and they will — it often happens at the worst possible moment: a performance review, a critical incident, a promotion that requires real competence they have not developed.
Engineers in mandatory-AI environments
Engineers whose companies have made AI tools mandatory face the middleman problem structurally. There is no opt-out available. You either use the tools or you cannot keep up with the velocity expectations. The problem is not individual — it is systemic. And the solution cannot be purely personal.
How to Reclaim Ownership
The middleman problem is structural, so the fix needs to be structural too. Here are the practices that have helped engineers rebuild ownership over time:
- One no-AI session per week
Block 90 minutes on a regular day and build something small without any AI assistance. Not a work task — something you care about. The point is not to prove you can do it; the point is to remember what it feels like to work through a problem yourself.
- The Explanation Requirement
Before you ship anything AI helped build, pause and explain it out loud to no one. Why that approach? What are the tradeoffs? What would you have done differently? The gaps in your understanding show up immediately when you try to explain them. If you cannot explain it, you do not own it yet.
- The AI Gap Log
Keep a running document of moments when you reached for AI and could not have done it yourself. Not to judge yourself — to see patterns. Over time, this log shows you where your ownership has contracted and where it might be worth rebuilding.
- Quarterly calibration
Once a quarter, ask yourself: "If all AI tools disappeared tomorrow, how much of my current work could I still do?" Write the answer down. Track it over time. If it is dropping, that is a signal — not a failure, a signal.
- Teach without AI
Find one thing you understand deeply — something AI could explain but you could explain from memory — and teach it to someone else. In person, a meeting, a pairing session. The act of teaching without AI as a safety net reveals what you actually own.
None of these practices reject AI. They require you to stay honest about where you actually are — and to deliberately maintain the parts of your craft that AI cannot replace.
The Question Worth Asking
The middleman problem is not going away. AI tools are going to keep getting better at generating code. The velocity gap between using AI and not using AI is going to keep growing. And the ownership gap is going to keep growing with it — unless you actively work against it.
The most useful question is not "should I use AI?" It is: "What do I want to still be able to do myself in two years?"
Answer that question deliberately. Then work backward from there. That is how you stay the author of your own work — even as the tools around you keep changing.
If This Is Getting Severe
If the middleman problem has progressed to the point where you are questioning your entire career, feeling persistently hopeless, or experiencing physical symptoms like disrupted sleep and anxiety, this page alone is not enough.