Introduction

This book is about a job title that has not settled yet, which is exactly why it is worth examining before it does. All over the industry, people are already directing models, agents, tools, codebases, and human specialists toward outcomes they are personally on the hook for, and they are doing it under whatever title they happened to be hired under — developer, architect, product engineer, technical lead, founder, researcher. The titles have not caught up, because titles never do. But the work has become recognizable enough that I can describe it to someone who is doing it and watch them nod before I finish. This book calls that work orchestration, and it calls the person responsible for it an orchestrator.