The Software Engineer As Agent Orchestrator Is Hired On Review, Not Typing Speed

What Does A Good Agent Orchestrator Do In The First Ten Minutes?

A candidate opens your repo, reads the ticket, and types a prompt eleven seconds later. That is the whole screen, and most teams miss it. The engineer you want spends those first minutes somewhere else: opening the two files the change will touch, checking what the existing tests actually assert, and narrowing the ticket into something an agent can be held to.

None of what follows has a checklist behind it. A working orchestrator writes the constraint into the prompt, the interface to keep, the file not to touch, the dependency budget, instead of asking for a feature and hoping. They read the diff rather than scrolling it, which is easier to see than people expect: ask one to narrate a hunk they did not write, in their own words, and a minute settles it.

Then, somewhere in a long session, they refuse something. A capable agent will propose something wrong with complete confidence: a package that does not exist, a migration that drops a column, a test quietly rewritten until it passes. Candidates who do this work daily have a reflex for it, and the reflex is boring. They go check. The shift Codacy describes is exactly this one, from typing implementation to defining intent and reviewing output, with review as the place the risk now collects; in the same account, 38 percent of developers find AI-written code harder to review than human-written code ².

The performed version sounds fluent about agents and carries no scars. Ask what the agent got wrong last week. Someone who runs one every day answers in specifics, with the commit still fresh. Someone who read about it answers in categories. Note also that this is not the job of building the agents: that belongs to the agentic AI engineer, and conflating the two is how a req ends up attracting neither.

Who Has Already Been Accountable For Code They Did Not Type?

Seniority helps here, but not the kind measured in years. Every background that produces a good orchestrator shares one habit: the person already worked with output they did not author and was held responsible for it anyway. Staff engineers who ran large code reviews qualify on that test. So do people from three or four places most reqs never think to look.

Open-source maintainers spend their weekends triaging pull requests from strangers, half of them well-meant and wrong, and they have learned to ask for a failing test before they argue about style. Incident responders and SREs distrust green dashboards on principle, which is precisely the instinct a passing test suite on agent-written code requires. Test and QA engineers spend their careers designing the trap that catches an optimistic implementer, and an agent is an extremely optimistic implementer. Contractors and consultants who inherit unfamiliar codebases every quarter get very fast at reading systems they did not build.

The market has already moved this way. US software development postings rose almost 15 percent after Claude Code's February 2025 launch while overall postings fell 7 percent, and 71 percent of the increase between May 2025 and May 2026 came from senior roles, with 37 percent from titles that mention AI ¹. BCG's 2026 survey of 11,749 workers found 47 percent already spend more time managing and directing AI than doing the work themselves ³. Directing is the job now, across more than software.

One background to treat carefully: the strong junior who has only ever worked with an agent. The prompt typed eleven seconds in usually comes from this person, who is often faster than they should be and has no model of what the code costs when it breaks at 3am. That is a training problem rather than a disqualification, and it needs someone senior reviewing their reviews for a couple of quarters.

Finding any of them does not start on a job board. People with real practice leave artifacts: merged pull requests where an agent's draft was clearly reworked, write-ups of a specific failure, talks about review tooling. Start with your own repositories and your dependencies, then work outward. GitHub is the primary source and the useful query is not stars, so read the review comments on a busy repository and find the person whose comments change the design instead of the formatting. Hacker News and Lobsters carry the honest postmortems. On Reddit, r/ExperiencedDevs runs a continuous argument about agent-written code that surfaces named people worth a cold email. The Rands Leadership Slack is full of tech leads doing this in the open, and on the conference side LeadDev and QCon program the review-and-delivery track this work lives in, where the speaker list doubles as a sourcing list.

Adjacent roles convert well. Developer experience and platform engineers already build the guardrails everyone else's agents run inside. Release engineers own the last line of defense. The forward deployed engineer bench reads unfamiliar systems under time pressure as a daily habit, which is most of the skill. Feeder companies matter less than feeder conditions: any team that shipped an internal agent platform, or that runs a monorepo with a strict review culture, has produced people who can do this.

One sourcing warning. Titles are unsettled, so a keyword search for the role name returns almost nothing useful. Search on the work instead: pull request review, code review at scale, developer productivity, internal tooling.

Close The Agent Orchestrator On Autonomy, Not Perks

What closes this candidate is scope and trust: which decisions they own, what the review bar is, and whether the team's agent policy was written by someone who still ships. What kills the offer is a rule they read as distrust, such as a mandated tool, a blanket ban on agent-written code, or a manager who counts commits as a proxy for output.

Be specific in the offer conversation about the blast radius they own without asking, because an engineer who has to escalate every schema change will not stay. Be specific about what your review standard actually is, including who is allowed to say no to a merge and on what grounds. And be specific about the tooling budget and whether their agent can reach the real codebase, since an approval queue for model access is a daily tax they will feel by week two.

Money is rarely the thing that loses this hire. The pattern that loses it is a role described as babysitting output, or a team where the agent policy exists to reassure a board rather than to help anyone write software. If the code touches lending, hiring, health or another regulated decision, say so plainly and describe how review works there; some candidates want that seriousness, and the ones who do not will screen themselves out. Where a model's own behavior is in scope rather than the code around it, that review sits with an AI model risk validator and belongs in a different req.

Set The Offer Inside Your Senior Engineer Band, Then Budget For The Tokens

Pay inside senior software engineer bands, because that is where the postings sit. No published salary series tracks this title yet. As of mid-2026, levels.fyi reports a median total compensation of $195,000 for US software engineers, with the 25th percentile at $137,000, the 75th at $280,000, the 90th at $387,000, and a San Francisco Bay Area median near $291,000 ⁴.

Read those numbers as a band rather than a target. The aggregator's sample skews toward large technology employers and self-reported packages, so a Midwest product company will land lower and a late-stage infrastructure startup higher. Because the growth in senior postings is where this demand concentrated ¹, expect the candidates you want to be holding a competing senior offer already, and expect equity refresh and level to matter more in the negotiation than base.

On location, the work argues for remote more than most engineering jobs do. Specification and review are asynchronous and text-shaped, they produce a written trail by nature, and a reviewer with three uninterrupted hours is worth more than one in an open office. The pressures that pull it on-site are real but narrow: codebases under export control or in air-gapped environments, hardware in the loop, and organizations whose security review has not yet approved sending source to a hosted model. Ask which of those applies before you write the location line, because a hybrid mandate with no reason behind it reads to this candidate as the same distrust that kills the offer.

One budgeting note worth saying out loud: agent usage is a real line item, and a team that hires the orchestrator and then rations the tokens has bought a bicycle and locked the shed.

See the benchmarks >