Forward Deployed Engineer (SDEV)

About the Role\n\nPagerDuty is seeking a Forward Deployed Engineer (SRE Agent) to join our customer-focused SRE Agent team. In this role, you will work inside PagerDuty's largest customer accounts, connecting the SRE Agent to their production environments (observability tools, infrastructure as code, GitOps tooling, and CI/CD pipelines) and guiding their teams from AI-assisted incident response to supervised and autonomous actions with safety guardrails. You will also contribute code directly back to the core SRE Agent product, building reusable tools, connectors, and skills derived from real customer needs.\n\n## Key Responsibilities\n\n- Embed and drive SRE Agent adoption: Work onsite and in regular contact with 2–4 strategic customer teams to deploy the SRE Agent, configure tools and connectors, and embed AI actions across their incident management lifecycle.\n- Build and contribute core agent capabilities: Scope, design, and build reusable agent tools, connectors, and skills on the agent's extensibility surfaces, shipping them through product repositories, reviews, and evaluation gates.\n- Run pilots and unblock customer adoption: Stand up new agentic capabilities with strategic accounts, gather evaluation data, identify technical blockers, and build production fixes directly into the product.\n- Integrate with production stacks and progressive delivery: Connect the SRE Agent to IaC (Terraform, Pulumi), GitOps (ArgoCD), CI/CD pipelines, and observability platforms.\n- Set technical direction and feedback insights: Define 3–6 month technical roadmaps across assigned accounts, provide architectural guidance to product and engineering managers, and bring customer feedback to the core team.\n\n## Basic Qualifications\n\n- 8+ years of experience building and shipping production software across team boundaries (assessed against PagerDuty Staff Engineer / SDE V expectations).\n- Hands-on experience with LLM and agent systems in production, including agent development, tool-use frameworks (MCP or equivalent), evaluation pipelines, and guardrail design.\n- Customer-facing skills: ability to run technical design sessions with engineers and present business cases to leadership.\n- Ability to navigate ambiguity and move from vague problem statements to working software.\n- A record of shipping adopted software and sound product judgment.\n- Infrastructure & Deployment expertise: Demonstrated experience with Terraform or Pulumi at scale, GitOps (ArgoCD or equivalent), CI/CD pipeline design, and progressive delivery patterns (canary, blue/green, soak periods).\n- Willingness to travel 25–50% during active customer engagements.\n\n## Preferred Qualifications\n\n- Practical operational knowledge of incident management and observability concepts (on-call, postmortems, SLOs/SLIs, alerting).\n- Customer-facing technical consulting, forward-deployed engineering, or solutions architecture experience.\n- Background as a founder or founding engineer navigating high ambiguity.\n- Experience with policy-as-code, fine-grained permissioning, or safety guardrail patterns for agent-driven automation.\n- Production experience with PagerDuty or competing digital operations and incident management platforms.\n- Active open-source contributions to the AI agent or Model Context Protocol (MCP) ecosystem.\n\n## Additional Information\n\nThis role is expected to be in the PagerDuty San Francisco office or at a client site at least 2 days a week.