EmergingTool-using agents and workflow orchestrationPart of The agent workforce

Agent Workflow Architect

Also called Agentic Workflow Architect

An Agent Workflow Architect decides which tasks go to agents, which stay with people, and where approvals sit. It matters because agents that act without clear limits create risk, rework and decisions nobody owns.

What they do

They map a real business process and break it into steps. For each step they decide who or what does it: an agent, a person, or both. They define the tools each agent may call and the permissions behind them. They design handoffs and approval points, including what a reviewer sees and what happens if they say no. They write this up as a workflow specification. They test it in a sandbox with awkward cases, then watch how it behaves once real work flows through. Much of the job is finding where the process breaks and fixing the design.

What a strong hire delivers

In the first months, a strong hire turns one messy process into a written workflow specification that engineers, operations and risk can all read. They get it running with explicit tool permissions and clear approval points. They set up a rollout evaluation that shows completion rates, how exceptions are handled, and who made each decision. The team can then say what the agents may do and why.

How you can tell they are good

Ask them to walk through a workflow they designed. Look for clear reasons why each step went to an agent or a person. Ask what went wrong in testing and what they changed. Strong people talk about failure paths, permission limits and reviewer fatigue before you prompt them. Be wary of anyone who only describes the happy path or treats approvals as a box to tick.

Why it is hard to fill

Few people carry this title today. The work is usually hidden inside application engineering, automation or integration jobs, so job titles tell you little. The skills are mixed: systems design, security thinking, evaluation and an understanding of how people actually work. Most candidates are strong in one or two. Our view is that you should hire for the judgement about limits and handoffs, then check the technical depth.

Where to find them

Look at application engineers who have built tool-calling features, workflow automation specialists, and systems integrators who have handled approvals and audit trails. Some come from platform or internal tooling teams. Others sit in solutions engineering at companies that sell agent products to enterprises. Operations-minded engineers who have redesigned a process end to end are often a good fit, even without agent experience.

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 Workflow Architect

  1. Describe a workflow you split between people and automated steps. How did you decide where each task went?

    A strong answer names criteria such as risk, reversibility, ambiguity and volume. They explain trade-offs and what they changed after testing. Worry if the split was based only on what was technically easy to automate.

  2. How do you decide what permissions an agent gets for each tool?

    Look for least privilege, scoped credentials, read versus write separation and logging. They should mention reviewing permissions as the workflow changes. Worry if they give agents broad access for convenience.

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

Job description you can post

We are building agents that take real actions inside our product and operations. We need someone to design how work moves between people and agents, with clear limits, approvals and accountability. You will own the workflow specification and prove it works in rollout.

What you will do

  • Break business processes into steps and decide which go to agents, which to people, and which to both
  • Define tool access and permissions for each agent
  • Design handoffs and human approval points, including what reviewers see
  • Write workflow specifications that engineering, operations and risk can use
  • Build sandbox tests covering exceptions and failure cases
  • Run rollout evaluations on completion, exception handling and decision ownership

What you will bring

  • Shipped workflows or automations that combine software and human steps
  • Hands-on experience with agent frameworks or workflow engines
  • Experience integrating tools and protocols into agent systems
  • Working knowledge of security practice for permissions and access
  • Experience evaluating system behaviour end to end
  • Clear written communication of complex processes

Nice to have

  • Experience with MCP or similar tool protocols
  • Background in systems integration or internal tooling
  • Experience designing audit trails for regulated work

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
  • Tool and protocol integrationAdvancedConnect models to external data and capabilities
  • Security engineeringWorkingProtect systems, identities and sensitive assets
  • Model evaluationWorkingMeasure capability and failure modes credibly

Other roles in tool-using agents and workflow orchestration

Hiring nowAI Agent EngineerAn AI Agent Engineer builds software agents that take real actions through tools they are explicitly permitted to use. They turn model capability…Hiring nowAgent Tool Integration EngineerAn Agent Tool Integration Engineer connects AI agents to outside systems through tightly scoped interfaces. They make sure agents act only where…EmergingComputer-Use Agent EngineerA Computer-Use Agent Engineer builds agents that operate real application interfaces, clicking, typing and reading screens, within firm limits. They…EmergingAgent Memory and Personalisation EngineerBuilds the memory, user models and personalisation layers that let an agent remember people across sessions and act on it. It matters because an…EmergingAI Agent ManagerAn AI Agent Manager assigns work to AI agents, reviews what they produce, handles the exceptions and tunes the workflow. They make agents dependable…

Related roles in other families

EmergingMulti-Agent Systems ResearcherMulti-agent coordination and economicsA Multi-Agent Systems Researcher studies how several AI agents behave when they work together, and builds methods and benchmarks to make that…EmergingAgent Coordination EngineerMulti-agent coordination and economicsAn Agent Coordination Engineer builds the layer that lets several AI agents hand work to each other, share state and settle conflicts. It matters…EmergingMulti-Agent Evaluation ScientistMulti-agent coordination and economicsA Multi-Agent Evaluation Scientist measures how groups of AI agents behave together and designs tests that expose collusion, cascades and…EmergingAgent Market Mechanism ResearcherMulti-agent coordination and economicsThis person designs and tests the rules that govern how AI agents trade, bid and share resources in bounded simulated markets. It matters because…

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.

← Tool-using agents and workflow orchestrationAll new job families

Start a search

Hiring an Agent Workflow Architect?

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.