> Markdown version of [/jobs/ext/4456358-forward-deployed-engineer-sre-agent](https://www.wearedevelopers.com/jobs/ext/4456358-forward-deployed-engineer-sre-agent). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Forward Deployed Engineer (SRE Agent

- **Company:** Pagerduty, Inc.
- **Location:** New York, NY, United States (Remote available)
- **Experience:** Expert
- **Salary:** $145,000.0 - $218,900.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Backup Devices, Continuous Integration, Software Engineering, Policy as Code, Pulumi, Evaluation Pipelines, Large Language Models, Virtual Agents, Model Context Protocol, Terraform, Pagerduty
- **Published:** October 15, 2026
- **Apply:** https://startup.jobs/forward-deployed-engineer-sdev-pagerduty-2-10499972

## About the Role

* 8+ years of experience building and shipping production software across team boundaries (assessed against PagerDuty Staff Engineer / SDE V expectations).
 * Hands-on experience with LLM and agent systems in production, including agent development, tool-use frameworks (MCP or equivalent), evaluation pipelines, and guardrail design.
 * 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.
 * 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.
 * 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).
 * Willingness to travel 25-50% during active customer engagements., * Practical operational knowledge of incident management and observability concepts (on-call, postmortems, SLOs/SLIs, alerting).
 * Customer-facing technical consulting, forward-deployed engineering, or solutions architecture experience on top of a core software engineering background.
 * Background as a founder or founding engineer accustomed to navigating high ambiguity and driving unscripted problem-solving.
 * 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.

## Description

* 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 to drive adoption and value
 * 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 the product team's repos, review process, and evaluation gates.
 * Run pilots and unblock customer adoption: Stand up new agentic capabilities with strategic accounts first, gather eval data, identify technical blockers (permissions, telemetry, missing connectors), and build production fixes directly into the product.
 * Integrate with production stacks and progressive delivery: Connect the SRE Agent to IaC (Terraform, Pulumi), GitOps (ArgoCD), CI/CD pipelines, and observability platforms, guiding customers safely from AI-assisted to autonomous operations.
 * Set technical direction and feedback insights: Define 3-6 month technical roadmaps across assigned accounts, provide architectural guidance to product managers and engineering managers, and bring customer friction and eval data back to the core team.