Agents and embodied systems

Tool-using agents and workflow orchestration

This family covers building bounded agents that act through explicit tool permissions. AI companies need it because an agent that can only do what it is allowed to do, and shows its work, is one a customer will actually trust.

Teams have moved from demos to agents that touch real systems, and that raises the stakes. Someone has to decide what an agent may do, how its actions are seen, and what happens when a step fails. The tricky part is the profile. Strong hires usually come from application engineering, workflow automation or systems integration, not research. Titles vary widely, and some roles are still forming. Look for people who think about failure first.

Hiring now 2Emerging 4

Roles in this family

6 roles

Where the people come from

Application engineering, workflow automation or systems integration

Not to be confused with. Core reasoning methods and open-ended future autonomy are separate categories.

Core skills

  • Security engineering
  • Model evaluation
  • Agent orchestration
  • Tool and protocol integration

Where it is used

  • Enterprise software and developer tools
  • Consulting and business services
  • Customer service and contact centres

Routes in and out

People move in from

More in Agents and embodied systems

← All new job families

Start a search

Hiring in tool-using agents and workflow orchestration?

Tell us the work you need done. We find the people already doing it, whatever their job title says.