Research into how job descriptions and engineering roles are evolving to match the new reality of AI agent-driven software delivery. Compiled to support the Nexus EM alignment discussion around the Feature Architect / lead dev role.
Fusion Risk Management posted an AI Agentic Delivery Engineer role (also called "Harness Engineer") at $150K-$165K. The role description:
- Directs AI coding agents to deliver production-ready software
- Translates feature requirements into agent-ready specifications
- Requires 5+ years of SWE experience plus deep understanding of LLMs and coding agent behaviors
- Experience in enterprise B2B SaaS environments with product and engineering teams
This is one of the first concrete postings that combines delivery accountability with agent orchestration — exactly the hybrid role we're describing for feature teams.
Deloitte's analysis coins the term AO-DLC (Agent Orchestrated Development Life Cycle) and frames the shift as:
"Instead of writing every line of code, engineers set objectives, guide specialized agents, review outputs and maintain architectural integrity. Humans own architecture, validation, and accountability."
Key findings:
- Accountability migrates upward, not away — engineers retain ownership of outcomes but delegate execution
- This is an operating model transformation, not a tooling upgrade
- Without proper oversight structures, organizations face "architectural drift across many agent-made decisions"
- ROI depends on governance and workforce maturity
A Staff Engineer's perspective on why the same skills used to lead junior engineers are exactly what's needed to lead AI agents:
"AI does not remove the need for engineering judgment. It increases the value of it."
The accountability model has three pillars:
- Quality gatekeeping — distinguishing "impressive-looking code from useful, maintainable software"
- Ambiguity resolution — agents given vague instructions will assume and build on assumptions, burning tokens and producing poor results
- Judgment over output — the engineer remains accountable for architecture, testing, security, performance, and maintainability
"The skills I built to enable humans turned out to be the exact skills needed to lead AI agents."
Addy Osmani describes the progression:
- Engineer initiates with a high-level goal
- Planning agents create subtasks
- Coding agents implement asynchronously
- Testing/review agents catch problems
- Human steps in to approve plans and give final deployment approval
"Organizations that have invested in this orchestration layer thoughtfully are shipping features in days that used to take weeks."
The 2026 Agentic Coding Trends Report found that on Claude Code, 79% of interactions are full automation vs 21% augmentation. The role shift is already happening in practice — engineers are spending the majority of their time directing and reviewing, not writing.
Cloudflare deployed coordinated AI review agents — up to seven specialized reviewers (security, performance, code quality, documentation, release management, compliance) managed by a coordinator agent. In 30 days:
- 131,246 review runs across 48,095 merge requests in 5,169 repositories
- Each MR reviewed an average of 2.7 times
- Median review time: 3 minutes 39 seconds
An academic paper on accountable agents in software engineering found:
"When a system fails in production at 2am, someone needs to own the problem completely: diagnose it, fix it, communicate with stakeholders during the outage, ship the fix, and lead the post-mortem. AI tools can assist with parts of this, but the accountability, the judgment under pressure, and the sustained focus on resolution belong to a person."
Current ToS frameworks consistently shift responsibility for correctness, safety, and legal compliance onto users — meaning the delivery engineer must own this explicitly.
One CTO cataloged 35+ AI engineering titles in a single week and concluded most describe roughly the same 3 jobs. The ones closest to our "delivery engineer" concept:
| Title | Focus |
|---|---|
| AI Agentic Delivery Engineer | Feature delivery via agent orchestration |
| Agent Tech Lead | Slicing features into agent tasks, steering agents, verification workflows |
| Context Engineer | Designing the context plane (CLAUDE.md, rules, RAG) that makes agents effective |
| AI Operations Manager | Hybrid technical + operational oversight at scale |
A concrete Agent Tech Lead job description on GitHub captures the convergence: orchestrating multiple coding agents on parallel worktrees, slicing features into agent-ready tasks, establishing verification workflows, handling corner cases when agents get stuck.
The Feature Architect / lead dev in the proposed model is essentially becoming this role:
graph TB
subgraph role["The Delivery Engineer (Feature Architect)"]
A["Directs AI agents to implement features"]
B["Owns delivery accountability end-to-end"]
C["Writes SDPs and makes architectural decisions"]
D["Reviews and validates agent-generated code"]
E["Translates requirements into agent-ready specs"]
F["Coordinates with PM and Architect Buddy"]
end
role --> old
role --> em
subgraph old["What They DON'T Do Anymore"]
G["Write all the code themselves"]
H["Wait for sequential refinement gates"]
I["Depend on EM for project management"]
J["Hand off UI/testing to other teams"]
end
subgraph em["What the EM Does Instead"]
K["Coaches delivery engineers in this new model"]
L["Cross-feature coordination and dependency tracking"]
M["Staffing proposals and capacity management"]
N["Escalation triage and component ownership"]
end
| Thread Point | Industry Evidence |
|---|---|
| Matt: "Only 1 person writes code with an LLM at a time" | Anthropic data: 79% of Claude Code interactions are full automation by a single engineer. The unit of production is one person + agents. |
| Robin: "Lead devs go heads-down and don't track delivery" | The Fusion Risk Mgmt posting and Agent Tech Lead JD both explicitly include delivery tracking as a core responsibility — this is a skill gap to address, not a reason to keep the old model. |
| Aaron: "Features need to be smaller — 6 weeks or less" | Osmani: "Organizations shipping features in days that used to take weeks." Smaller features + agent-accelerated delivery = this timeline is realistic. |
| Robin: "Are we sure keeping EM out of features is right?" | Deloitte: accountability migrates upward to governance/coaching layer. EM becomes the talent transformation and orchestration oversight role, not the feature PM. |
| Naveen: "Can less experienced engineers keep up?" | The Emad Mokhtar piece argues these are Staff-level skills. Junior engineers need coaching into this model — which is exactly the EM's job. |
| Matt: "Conway's law — are we doing teams this way because it works?" | The CTO title analysis found most orgs are still mapping old roles onto new work. The ones succeeding are the ones redesigning the role from scratch. |
- AI Agentic Delivery Engineer — Fusion Risk Management
- Agentic AI in Software Engineering — Deloitte
- Stop Just Writing Code, Start Leading Agents — Emad Mokhtar
- The Future of Agentic Coding — Addy Osmani / O'Reilly
- Agent Tech Lead Job Description — GitHub
- Accountable Agents in Software Engineering — ArXiv
- AI Job Titles in 2026 — Ivan Turkovic
- 2026 Agentic Coding Trends Report — Anthropic
- Orchestrating AI Code Review at Scale — Cloudflare
- From Context Engineers to Chief AI Officers — ODSC