Forward Deployed Engineer (SDEV)

Join PagerDuty as a Forward Deployed Engineer (SRE Agent) and work directly with our largest customer accounts. You will connect the SRE Agent to their production environments, guide their teams in incident management, and contribute code back to the core SRE Agent product. This role requires a strong background in software engineering, hands-on experience with LLM/agentic systems, and customer-facing skills. Benefits include paid volunteer time, health insurance, generous paid time off, and flexible workplace options.

• Embed and drive SRE Agent adoption by working onsite and in regular contact with strategic customer teams to deploy the SRE Agent and configure tools.
• Build and contribute core agent capabilities by scoping, designing, and building reusable agent tools, connectors, and skills on the agent’s extensibility surfaces.
• Run pilots and unblock customer adoption by standing up new agentic capabilities with strategic accounts, gathering evaluation data, and identifying technical blockers.

• Customer-facing skills. You can run a technical design session with a customer’s engineers and present the business case to their leadership
• Comfortable with ambiguity. You can start from a vague problem statement in an unfamiliar environment and get to working software without much direction. Former founders and founding engineers tend to do well in this role
• Willingness to travel 25–50% during active customer engagements
• 8+ years of experience building and shipping production software across team boundaries (assessed against PagerDuty Staff Engineer / SDE V expectations)
• 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)
• Hands-on experience with LLM and agent systems in production, including agent development, tool-use frameworks (MCP or equivalent), evaluation pipelines, and guardrail design
• A record of shipping software that got adopted, and the judgment to recognize which customer requests generalize and when the right answer is not to build
• Practical operational knowledge of incident management and observability concepts (on-call, postmortems, SLOs/SLIs, alerting)
• Background as a founder or founding engineer accustomed to navigating high ambiguity and driving unscripted problem-solving
• Customer-facing technical consulting, forward-deployed engineering, or solutions architecture experience on top of a core software engineering background
• Experience with policy-as-code, fine-grained permissioning, or safety guardrail patterns for agent-driven automation
• Production experience with PagerDuty or competing digital operations and incident management platforms
• Active open-source contributions to the AI agent or Model Context Protocol (MCP) ecosystem