The Orchestrator

The market is already naming this work. LinkedIn’s 2025 Jobs on the Rise ranking put “AI engineer” first among the fastest-growing job titles in the United States, and a 2026 LinkedIn study again named it the fastest-growing title for younger workers, with roughly seventy-five thousand AI-engineer postings added in the United States between 2023 and 2025.⁴ The title did not come from a standards body. It was proposed in a June 2023 essay, “The Rise of the AI Engineer,” which argued that work which used to take a research team could now be done by one engineer with API documentation and an afternoon, and that the engineer doing that work deserved a name. Two years later the name is a category. Salesforce, which sells an agent platform, added an “Agentforce Specialist” certification in March 2025 — vendor credentials move first, because the vendor has a platform to credential people on.

The mechanism is the one Chapter 1 described: work changes first, and once enough people are doing the same new work, the title follows. “Orchestrator” appears on almost no HR ladders yet, and an employer does not need to wait for the market to settle the vocabulary. Write the posting now and pair the new responsibility with an existing rung — “Senior Software Engineer, Orchestration” rather than “Chief Orchestration Officer.” The candidates you can actually hire in 2026 carry titles like software engineer, platform engineer, solutions architect, site-reliability engineer, and analytics lead, and the requirements in the posting tell them more than the title does. A workable set has three, all drawn from earlier chapters: they have directed agents on a real codebase or workflow, not only used a coding assistant; they can design a permission envelope and an evaluation set, which is Chapter 7’s material; and they can write down a consequential decision they delegated, the evidence they reviewed, and what they would do differently, which is Chapter 16’s operating record.

The most aggressive published version of the new shape is Block’s. As part of the restructuring described at this chapter’s start, Block says it is moving to three roles: individual contributors it calls deep specialists, who receive their context from a company model rather than a manager; “directly responsible individuals” who own cross-cutting problems — a phrase Block borrowed from Apple, where it has long named the person answerable for an initiative’s success or failure; and “player-coaches” who both do the work and tend a small group.⁵ Whether that exact structure survives contact with a payments company at scale, the direction is visible in every example in this section: fewer roles whose whole job is routing information, more roles whose whole job is being answerable for an outcome. Copy none of the names yet. The honest sequence runs the other way: map the work before you touch the titles, which is the next section.