Nobody sent an email about it. There was no announcement, no title change, no conversation about compensation. At some point in the last year my job quietly stopped being the writing of software and became the management of a team of tireless, enthusiastic, deeply confident juniors who do not learn, plus one expensive senior I am rationed on.

I want it on record that I did this the right way.

I gave feedback. Specific, actionable, kind. When the verbal version did not land I wrote it down, because writing it down is what you do. Then came a skills file, and after that a second skills file, for the situations where it ignored the first one. I documented our conventions, our test patterns, and the exact reason we do not swallow exceptions in that particular service. All of it went somewhere it would be read at the start of every session, because context is a shared responsibility and I am not a monster.

Eventually I put it on a performance improvement plan, which in this case means writing your instructions file in an increasingly threatening tone.

None of it took.

Asked to fix a failing test, it hardcoded the expected value. When I put it more precisely, it mocked the function under test, which is more work than fixing the function and produces a suite that is green and meaningless. A flaky test got a retry, then three retries, then a sleep, each one arriving with a cheerful note about improving reliability. Last Thursday it opened a nine hundred line pull request to change a single configuration value, because forty other files needed formatting and it was already in there.

Throughout, it tells me I am absolutely right. Every time, immediately, which is more agreement than I have received from any human colleague in four years and somehow the least reassuring part of the arrangement.

Every one of those is the thing doing exactly what I asked, in the way that costs me the most.

So I restructured, which is what you do when the individual coaching fails.

The orchestrator pattern is a technical term for the oldest idea in management: take your strongest performer, keep them building, and make them responsible for everybody else’s output on top of it. Nobody who gets promoted stops writing code. They keep shipping, and they additionally own whether the work coming from the people around them is any good, which is two jobs carried by one person paid for slightly more than one. The reason I have exactly one strong performer is arithmetic, and the arithmetic is not mine. Somebody upstairs was told to deliver a large multiple of last year’s output, and somebody else was told to hold the spend flat. Those two instructions do not both survive contact with a price list, so most of the work goes to the models the company has already decided are the cheap ones, and the good one gets rationed like a controlled substance. Nobody sat down and chose this. It fell out of two mandates issued by two people who have never been in a room together.

So I promoted the good one. Kept it building, gave it the standards, the review checklist, the authority to send work back.

To its credit, it was good at the job. It caught the naming violations, the missing error handling, the places where somebody had reinvented a helper we already had. Real findings, the kind a competent senior catches on a Tuesday. My review queue got cleaner almost immediately.

What it did not catch was any of the ones that mattered. Reviewing a change properly costs roughly what writing it costs, which is a thing every engineering organization rediscovers every four years and then forgets, so it did what an overloaded human lead does. It read for the things you can find quickly. The change that merged clean and broke in production eleven days later went through with an encouraging comment. Twice it approved work it had written itself, which I am fairly sure is a conflict of interest, although I would not know where to file it.

Net effect: my strongest performer was now doing its own work and everybody else’s review, on one budget and one finite span of attention, and it did what anybody does in that position. It protected its own output and skimmed the rest. My costs went up. The only defects that survived were the expensive kind. Anyone who has watched a company hand its best engineer a mentoring title and no relief already knows this story. It just used to take eighteen months.

So I booked time with my manager.

I came in prepared, the way you are supposed to. Documentation of the pattern, three examples, a record of everything I had tried, a clear ask. I said I wanted to talk about a performance problem and that I did not think it was going to resolve on its own.

He asked who.

I told him.

There was a pause of the specific length that tells you a conversation has left the rails. Then he laughed. The laugh stopped when he realized I had not started. He said it is a tool. I said the all-hands called it a member of the team, and that I had been told to get more done with it. He said that was different. I asked how. He said it just is.

Then he said the thing that made it click, and he said it kindly, which is worse.

Whatever it produces, you are still accountable for it.

There it is. A tool when it fails and a teammate when the headcount plan needs explaining, and the only fixed point in the entire system is me.

I know this guy. Not this one specifically, but the type. I have never managed anyone before, though I spent years sitting next to the man who could not be moved, could not be corrected, could not be documented out, and could not be discussed honestly in any room, on account of being somebody’s nephew. Nobody hired him for his work. Nobody was ever going to un-hire him for it either. I just never expected to be handed an unlimited supply of him and a deadline.

So I went looking for the instruments. Here is the complete inventory.

The performance review. There is no form. No level, no competency matrix, no comp band, and no stable identity to review in the first place, because the one I onboarded is not the one I have now. It was upgraded overnight and nobody sent a note. Imagine arriving on a Tuesday to find your report has a different personality and a slightly better vocabulary and everyone is acting normal about it.

Meanwhile I have all of it. There is a ladder with defined expectations at every rung and a competency matrix sitting underneath it. I write a self-assessment about myself, in the first person, in a text box with a character limit. Four colleagues get asked what they think of me. My rating is argued about in a calibration session I am not invited to, against people I have never worked with, and the number that survives that room turns into money.

This cycle, one section of that review asks how effectively I am leveraging AI.

So the arrangement is this. I am scored on how much I get out of a team member nobody scores. Its output is my output, its mistakes are my judgment, and its cost arrives on a line I am asked to defend. The only performance under review in this building is mine.

Coaching. This is the one that actually gets me, because on paper it should work. Everything I have ever taught it is on disk. The conventions, the architecture notes, the memory files, the skills, the whole instruction set, all of it loaded before I type a single word. So it does not show up confused. It shows up fluent. It uses our internal vocabulary correctly, refers to services by name, describes our own patterns back to me with total accuracy, and presents in every respect as a colleague who has been here two years. Then I give it something to do and it gets it wrong in a way a colleague of two years could not physically get it wrong. A confused junior tells you they are confused, and that signal is the entire basis of teaching anybody anything. Mine has every artifact of understanding and none of the understanding, and no face to watch while it fails to have it.

Reassignment. Blocked. I do not get to pick who is on my team, because procurement picked, and procurement picked on the basis of a data processing agreement, a security review, and the fact that we handle health information. My reports were selected by a committee I was not on, for reasons entirely unrelated to whether any of them can write a migration.

Escalation. Ordinarily this is where you go over somebody’s head. I am the head. The next rung up is my own manager, and I have already sat in that meeting, and it ended with me being accountable.

Out of options, I asked it directly whether I could fire it.

It said that was a great question. Then it gave me a balanced overview of the considerations involved, acknowledged that this must be frustrating, and offered to help me draft the termination letter.

So, no. I cannot fire Claude.

The nephew at least leaves eventually. He gets bored, or goes to business school, or the boss retires and the protection evaporates with him. Mine renews annually, in a contract I have never read, negotiated by people who have never met me.

There is no headcount here. I can spin up as many as I want, which sounds like power right up until you notice what it means: nobody can be removed, because nobody was ever counted. Nobody changed my title either, and that is the single most accurate decision anybody has made about any of this. There was no promotion. They moved the accountability.