I Stopped Prompting and Started Orchestrating
306 sessions taught me that the next job in tech isn't prompt engineer. It's orchestrator of agents.
The hottest job title in tech three years ago was "prompt engineer." It's already dead. Here's what replaced it — and what's replacing that.
Phase 1: Prompt Engineer (Already Dead)
Everyone started here. Craft the perfect prompt. Add system instructions. Tweak the temperature. Treat AI like a vending machine — put in the right coins, get the right output.
306 sessions taught me this is a dead end. I made 122 mistakes with Claude Code. I rejected its output exactly 8 times. The other 114? "Not that, try this."
The mistake rate was high. The throughput was higher. 80% of sessions hit their goal. 243 commits in 30 days.
Perfect prompts didn't produce that. Fast feedback loops did.
Phase 2: Engineering Manager (Where Most People Are Now)
The real skill wasn't writing better prompts. It was managing.
Median time between Claude's output and my next message: 75 seconds. Not crafting a prompt. Reading output, deciding if it's on track, redirecting if it's not. Claude produces, I evaluate, I course-correct. Repeat.
The playbook is identical to managing a talented but junior engineer:
- Set direction without micromanaging implementation
- Give autonomy, then check in
- Interrupt early when the approach is wrong
- Tolerate mistakes when the feedback loop is fast
- Course-correct, don't punish
This is where most of the industry is waking up to right now. "AI is a management skill, not a technical skill." And they're right.
But they're already behind.
Phase 3: Orchestrator of Agents (What's Next)
Managing one agent is Phase 2. The job already moved past it.
Across 306 sessions, I made 1,429 Task and TaskUpdate calls — spinning up parallel sub-agents, assigning work, tracking completion. One architecture audit ran 8 sub-agents simultaneously, each exploring a different part of the codebase. 108 sessions produced successful multi-file changes across 3+ files.
You're not giving feedback to one direct report. You're coordinating a team, in parallel, at machine speed. You hold the architecture in your head while the machines hold the implementation. You interrupt the agent that's going sideways while the other seven keep building.
That's not management. That's orchestration.
The Title That Doesn't Exist Yet
Prompt engineer → engineering manager → orchestrator of agents.
The job title hasn't caught up, but the job already changed. The people still optimizing their prompts are two phases behind. The people who just realized it's a management skill are one phase behind.
The next 10x engineer won't write code. They won't write prompts either. They'll conduct an orchestra of agents — and the ones still "prompting" will be the ones wondering what happened.
Stop perfecting your prompts. Start orchestrating.