Pantheon
Staff Software Engineer, Platform Infrastructure
About this role
About Pantheon Pantheon brings together exceptional builders who take ownership, drive meaningful impact, and shape what’s next for the web. We power more than 300,000 websites globally for organizations including Google, Princeton, Salesloft, Clorox, and the United Nations. Every day, thousands of developers and marketers use our WebOps platform to build, iterate, and scale WordPress, Drupal, and Next.js sites that reach billions of people worldwide. As an employer, we operate with the same philosophy that drives our product: foundation and freedom. Pantheon is a vibrant, remote-forward team of experts who care deeply about their craft and results. Here, you take ownership of work that matters, contribute alongside exceptional people, and see the impact you create. The Role The Platform Infrastructure Engineering (PIE) team is the foundation that lets every engineering team at Pantheon move fast, safely. We build the patterns, templates, and tools that power a self-service developer experience - and we’re responsible for the reliability and observability standards Pantheon’s entire internal platform depends on. We’re looking for a Staff Software Engineer with a strong SRE orientation to take our platform reliability practice to the next level. Today, reliability is distributed and inconsistent across teams. This role exists to change that - establishing Site Reliability Engineering as a first-class discipline within our group and setting the patterns that 15+ engineering teams will use to ship quickly and safely for years to come. In the short term, the focus will be on building and finalizing our new internal Service Foundation platform - meeting strict compliance requirements while making it easier, more reliable, and quicker to ship. Long term, as that foundation matures, the focus shifts toward SRE best practices: formalizing SLO/SLI frameworks, incident response culture, and reliability engineering across the organization. You’ll be a technical voice not just within PIE, but across the broader Internal Platform Group - working with adjacent teams to drive alignment and raise the bar. The new platform runs on Go, GCP primitives (Cloud Run primarily, with GKE being strategically used), Terraform, and a Grafana-centered observability stack. Pantheon’s core values are Trust, Teamwork, Passion, and Customers First. Within engineering, we value collaboration, character, autonomy, and a no-blame culture. What You Will Do Establish SRE as a discipline. Define and drive adoption of SLO/SLI frameworks, reliability standards, and incident response practices across PIE and the broader Internal Platform Group. Build a quieter, more reliable internal platform. Set the observability standard. Own and evolve our observability patterns
- Prometheus metrics, OpenTelemetry tracing, and structured logging - so every team has clear, actionable signals. Observability is a first class citizen here. Build and maintain the paved path. Design and deliver the service templates, Terraform modules, and infrastructure patterns that make success easy: Go APIs, CLIs, Cloud Run services, and GKE workloads that come with reliability and observability built in from day one. Default to GCP primitives. Contribute to key strategic initiatives - migrating to GCP Secret Manager, standardizing on GitHub Actions and Cloud Build, moving to Cloud SQL - by establishing GCP-native managed services as the default for scaling. Help the organization move away from self-hosted complexity as the default, and toward primitives that reduce operational burden. Drive security and compliance. Apply security-first thinking to networking and identity
- IAP, IAM, VPC design - and support compliance posture across SOC 2, ISO 27001, PCI DSS, and other frameworks. Mentor the team. Guide engineers in designing and implementing high-impact reliability and infrastructure work, raising the technical bar across PIE and adjacent teams. Own the full lifecycle. Operate in a full DevOps model - development, testing, operations, and support for the systems you build. Participate in on-call. After an initial ramp period (typically 3-6 months), join on-call rotation and actively contribute to reducing its burden through better automation, runbooks, and reliability work. What You Need to Succeed Site Reliability Engineering principles: deep understanding of SLOs, SLIs, error budgets, toil reduction, and how to operationalize these practices in a team that hasn’t had them before. Cloud infrastructure: hands-on expertise with GCP services