AI Engineer

Give Your On-Call Its Own AI Teammate - Swaapnika Motapothula, Chinmay Gandhi & Vlad Tsvang, Meta

Published 2026-11-10 · Duration 15:41

Summary

The talk introduces a novel AI teammate designed for on-call incident response, addressing the operational bottleneck that has emerged as AI accelerates code writing. Instead of relying on siloed automation (e.g., separate bots for alerts, tickets, or deploys), the system proposes a single, context-aware agent that connects all signals—alerts, tickets, incident history, and code changes. This teammate provides a human with a hypothesis, supporting evidence, and a proposed action, shifting the engineer's role from deep investigation to critical decision-making while ensuring all critical changes pass through normal human review and Continuous Integration (CI).

Download summary

Key takeaways

  1. The Operational Bottleneck

    The challenge has shifted from writing code to operating it in production. On-call duty is the primary operational load, requiring a system that can synthesize information from multiple sources (alerts, tickets, history) simultaneously.

  2. Integrated AI Teammate

    The proposed solution is one AI teammate per rotation that acts as a single loop across all signals, maintaining shared context and identity across shifts, unlike current siloed automation tools.

  3. Autonomy Ladder 0:05

    AI autonomy is structured in levels: Level 1 (Investigation only), Level 2 (Drafts fixes for human approval), and Level 3 (Clears lower criticality work autonomously). Autonomy must be earned by demonstrating that mistakes are cheap to detect and catch.

  4. Human-in-the-Loop Safety 0:13

    Critical production decisions and code changes remain human-owned. The AI teammate provides the evidence and the draft fix, but the human must approve the action, ensuring that review remains the primary filter.

More digests on AI Agents

Technical details

  • AI Agent Architecture 6s

    The core teammate is a simple agent utilizing a model with tools in a loop, acting on an environment and reading feedback. The system integrates team-specific skills, runbooks, and knowledge bases, allowing teams to 'bring their own agent' while leveraging the core platform.

  • Shared Memory and Identity 11s

    The teammate's identity and memory belong to the *team* (the rotation), not an individual. This ensures that expertise, past decisions, and corrections flow into the shared memory, improving performance over time (e.g., Shift 30 > Shift 1).

  • Feedback Loop and Learning 12s

    The system is designed to learn continuously: any correction or failure (e.g., when a proposed fix was wrong) reopens the item and is absorbed into the team's memory, making feedback an active input to the system.

  • Automation Loops 9s

    The system includes automated loops for triage, recovery from stuck runs, and shift handoffs. It proactively monitors for stuck or failed runs and attempts to repair broken schedules before paging a human.

Mentioned resources

Channel & topics

Watch on YouTube · Back to latest

This independent, AI-assisted summary is provided for commentary and informational purposes. It may contain errors or omit important context. Please watch the original video for the creator's complete presentation. Video, thumbnail, and related copyrights belong to their respective owners.