The AI Operator: A New Role for Agentic Workflows

The article on HN AI Agents proposes that as AI agents and MCPs enable agent-agent coordination, companies need a new role: the AI operator. This person sits between business and engineering, analogous to the industrial engineer (during electrification) or product manager (during the internet shift).

What an AI operator does

• Spends time with CEO and department heads to identify repetitive, time-consuming, labor-intensive processes.
• Stack-ranks processes by impact on efficiency or velocity.
• Works in short sprint cycles to build or buy AI tools to automate those processes.
• Educates and supports ICs on using the tools.
• Rotates through every function at least quarterly.

Required skill stack

The strongest candidates have shipped an AI product to real users, run a business function (sales ops, customer success, product), worked at an early-stage startup, or built internal tools. The skill stack includes:

• Technical: Proficient in Python, LLM APIs, prompt engineering, agent frameworks, and workflow tools (n8n, Retool, Zapier, custom scripts). Can build internal production-quality solutions (doesn't need to scale to hundreds of users).
• Business: Understands how a function operates—its inputs, outputs, metrics, incentives.

Metrics to track

• Revenue ($) per employee
• AI usage per employee
• Tasks fully automated by AI

Why now

The author argues that AI agents and MCPs can coordinate agent-agent interactions, but organizations haven't redesigned work yet—they're just layering AI on old processes, like putting an electric motor in a steam-engine factory. The AI operator is the role to drive that redesign.

Example: a cofounder can ask Salesforce MCP connected to Claude for pipeline analysis (skipping finance, sales ops). A product person uses a Claude Code instance to analyze sales calls.

The article cites that Walmart's AI senior leader is paid 2x the CEO, signaling the value of this role.