Head of AI Native Operations

Role overview A globally distributed, open-source-first software company is building an AI-native internal operating system where agents carry a meaningful share of operational work. The Head of AI Operations will own the maturity model, written standards, and operating cadence that make that shift stick, leading two senior individual contributors (one platform engineer, one enablement lead) and applying a single design rule: every recurring meeting must justify why an automated report cannot replace it.

Responsibilities

- Own the maturity model end to end: the rubric, scoring method, evidence standard, and appeals path, so every team gets a published assessment and a written plan to its next level. - Run assessments and land them as commitments, working directly with department heads and tying outcomes to named owners and dates. - Own the standards layer: how work is tracked, how proposals reach resolution, how teams migrate to shared tooling, and how stale documentation is retired, with standards that are followed without being chased. - Run the operating cadence, including automated weekly reporting, a recurring blockers-and-decisions forum, a monthly leadership review, and a quarterly board format, and actively delete meetings a report could replace. - Manage rollouts through private assessments first, then a pre-committed public transparency date that does not move. - Wire standards into onboarding so each new cohort arrives pre-trained rather than inheriting local habits. - Hire, grow, and direct two senior individual contributors, and become the reviewer of what they build rather than the executor.

Requirements

- Experience running operating cadence and program discipline at a remote, async company crossing roughly 200 to 800 people. - Hands-on experience personally building agentic AI workflows that others depended on, with the ability to review workflow definitions, data models, and pull requests for quality. - Track record of taking a standard from zero to company-wide without direct authority over adopters, with a clear mechanism that made it stick. - Exceptional written communication, with documents functioning as the primary enforcement mechanism in a remote, async environment. - Comfort being graded publicly by the same system you build alongside every other team. - Native fluency with Git, Markdown, and pull requests, whether from an engineering or technical operations background.

Nice to have

- Prior ownership of a maturity model or capability assessment across teams you did not directly manage, with published results and organizational reallocations driven from them. - Direct experience permanently eliminating a recurring meeting by replacing it with an automated system. - A deep software engineering background.

Benefits and work setup

- Fully remote, async-first with global hiring and a co-working allowance usable anywhere. - Equity ownership for every team member and a personal tech allowance. - Health coverage for employees and partial coverage for dependents, regardless of location. - Annual company off-sites, flexible scheduling, and an annual professional development allowance.