Level 4
Orchestrating
You design the system that does the work — and the system that grows the people.
What's a level? How far you've shifted from writing code yourself to directing the AI that writes it — five bands, from hands-on-keyboard to running a fleet of agents. Most of us are mid-ladder, and climbing.
Where you are
You run fleets of agents, not single ones. Multiple agents working in parallel, in deliberate topologies: an executor here, a reviewer questioning the spec there, an advisor on standby, the whole thing coordinated by skills that carry work from first brainstorm to final merge gate. You think in terms of roles and interaction modes, not tasks. Orchestration has become a meta-skill: the discipline of arranging the work, not doing it.
What's keeping you here
At this altitude, the limit stops being your own throughput and becomes everyone else's. You can orchestrate a fleet, but the org around you still has engineers stuck below the Level 5 jump, processes built for humans-as-operators, and architecture that fights the team shape you actually need. The constraint is no longer personal capacity; it's how much of the organisation can move with you.
Why it matters now
This is where Conway's Law comes back, pointed at agents. Team Topologies argues you should deliberately shape structure to produce the architecture you want. And a fleet of agents is a team structure, with cognitive load and interaction modes of its own. The frontier is cross-model, cross-provider orchestration: Claude talking to GPT, heterogeneous agents where the question stops being "which model is best" and becomes "which model is right for this role." Designing that well is the rarest skill in the field right now.
What's different
The unit of leverage moves from "a system of agents I run" to "an organisation that can run systems of agents." Your output stops being measured in what your fleet ships and starts being measured in how many other people you've moved across the jump, and how much of the org's old human-shaped scaffolding you've torn down and rebuilt for a world where agents are the operators.
The leadership shift
Here the leadership framing is the whole job — there's almost nothing else left. You're not managing agents anymore so much as designing the conditions a whole org operates in: which team topologies produce the architecture you want, what you make safe to try, what you reward. Marquet turned the worst submarine into the best by moving authority to where the information lived, without replacing the crew. That's the move at this level, applied to an organisation of humans and agents at once: distribute ownership, design the structure, grow the leaders underneath you, and resist becoming the single point everything routes through. The cap on what you can build is now the cap on how well you grow others.
Your moves
- Treat your agent fleet as a team-design problem: name the roles, set the interaction modes, and watch the cognitive load — the topology is the architecture (Conway's Law cuts both ways).
- Run the advisor and orchestration patterns across models: route each role to the model that fits it, rather than defaulting one strong model to everything.
- Question one inherited process a week: ask whether it exists only to work around a human limitation, and if so, redesign it for agents-as-operators.
- Make growing others your real output: deliberately coach engineers across the Level 5 jump, because org-level leverage beats one more perfectly orchestrated fleet of your own.
Marquet took the worst-performing submarine in the Navy and made it the best — without replacing the crew — by refusing to give orders. Don't move information to authority. Move authority to information.
Next rung
There's no Level 9 to climb to. The next frontier isn't a higher personal level, it's leverage that lives outside you. Three directions: grow other engineers across the Level 5 jump so the capability isn't trapped in your head; question the inherited assumptions of a 40-year era built for humans-as-operators, and redesign the processes that no longer fit; and push into the cross-model orchestration frontier, where any model can talk to any model regardless of provider. The ladder stops being about you and starts being about the org you're shaping.