EmergingMulti-agent coordination and economicsPart of The agent workforce

Agent Coordination Engineer

Also called Agent Orchestration Engineer

An Agent Coordination Engineer builds the layer that lets several AI agents hand work to each other, share state and settle conflicts. It matters because multi-agent products fail at the seams, not inside any one agent.

What they do

They design and build the routing, messaging and conflict resolution that sit between agents. Day to day, that means deciding which agent gets a task, how handoffs are passed on, and what happens when two agents want the same resource or hold different views of the world. They write coordination protocols, run multi-agent simulators, read traces to find where a handoff went wrong, and add fault and contention tests. Much of the job is making failure boring and recoverable.

What a strong hire delivers

In the first months, a strong hire gives the team a working coordination layer with clear handoff rules and a test suite that injects faults and contention. Handoffs become correct and traceable. Agents recover from inconsistent state instead of looping or stalling. The team also gains shared language and tooling for debugging multi-agent behaviour.

How you can tell they are good

Ask them to walk through a coordination failure they diagnosed from traces. Good candidates name the cause precisely, such as a race, a stale view of state or an unclear owner, and show how they tested the fix. They reason about protocol trade-offs, and they can explain how they would measure correct handoffs and recovery.

Why it is hard to fill

The work is real but rarely has its own title. It sits inside platform, agents or research engineering roles, so job titles are a poor filter. The skills straddle distributed systems, game theory and model evaluation, and few people hold all three. Most good candidates grew into it from one side and taught themselves the rest.

Where to find them

Look first at distributed systems engineers who have moved into agent products, and at reinforcement learning researchers who worked on multi-agent settings. Agent evaluation specialists and people with a game theory or mechanism design background also fit. They sit in AI product start-ups, agent framework teams, infrastructure groups and research labs.

Indicative pay

Not enough published evidence yet to give a fair range for this role, which is common for work this new. We benchmark it for you as part of a search.

Interview questions for an Agent Coordination Engineer

  1. Tell us about a multi-agent or distributed system that failed at a handoff. How did you find the cause?

    A strong answer describes the trace evidence, the specific fault (race, stale state, unclear ownership) and how they confirmed it. Worry if they blame the model vaguely or cannot say how they reproduced the failure.

  2. How would you decide between a central router and agents negotiating peer to peer?

    Look for trade-offs: single point of failure, latency, observability, scale and how conflicts get resolved. Good candidates tie the choice to the use case. Worry about dogma or a single favoured pattern.

4 more questions, with what a strong answer covers, are in the Role Kit.

Job description you can post

We are building products where several AI agents work together, and we need someone to own how they coordinate. You will design the routing, messaging and conflict handling between agents, and make sure the whole system stays correct when individual parts fail.

What you will do

  • Design and build routing and messaging between agents
  • Implement conflict resolution for shared tasks and resources
  • Define handoff rules and coordination protocols
  • Build fault and contention tests for the coordination layer
  • Analyse traces to find and fix coordination failures
  • Run multi-agent simulations to compare protocol designs
  • Document behaviour so other teams can build on it

What you will bring

  • Demonstrated work on distributed systems or multi-agent systems
  • Clear examples of debugging failures from traces or logs
  • Experience designing or evaluating coordination protocols
  • Ability to write tests that inject faults and contention
  • Working knowledge of agent orchestration approaches
  • Sound judgement on trade-offs, explained plainly

Nice to have

  • Background in reinforcement learning or game theory
  • Experience evaluating agent behaviour
  • Familiarity with multi-agent simulators

Free to use and adapt. If it saves you time, a link back to this page is appreciated.

Skills that matter

  • Agent orchestrationAdvancedCoordinate tool-using agent execution
  • Decision theory and game theoryAdvancedAnalyse choices, incentives and strategic interactions
  • Distributed systemsWorkingDesign reliable work across networked machines
  • Model evaluationWorkingMeasure capability and failure modes credibly

Other roles in multi-agent coordination and economics

Related roles in other families

How we wrote this

Role definitions are our own editorial work, checked against occupational classifications, standards, research and employer pages. Titles vary by company, and this is a description of the work, not a job advert.

← Multi-agent coordination and economicsAll new job families

Start a search

Hiring an Agent Coordination Engineer?

Tell us the work. We find the people already doing it, whatever their job title says, and you meet them already interviewed for your role.