Site Reliability Engineer, Infrastructure Platforms — AMER (Intermediate to Senior Staff)

An overview of this role

Site Reliability Engineers keep GitLab's user-facing services and production systems running reliably at scale. They combine software engineering with operational excellence, applying sound engineering principles, automation, and continuous improvement to build, operate, and evolve our production infrastructure.

This is a single application for Site Reliability Engineering opportunities across Infrastructure Platforms. Rather than asking you to choose the right team or level upfront, we evaluate your skills holistically and match you to the opportunity that best aligns with your experience and our hiring needs. We hire Site Reliability Engineers from Intermediate through Senior Staff across multiple Infrastructure Platforms teams.

How our SRE hiring works

• Recruiter Screen: A conversation about your background, what you're looking for, and the level and teams that fit.
• Core Technical: The shared assessment every SRE candidate takes, covering system architecture and incident review.
• Hiring Manager Interview: A conversation about ownership, judgment, execution, collaboration, and growth.
• Peer Technical: Team-specific depth, run by SREs from the team you're most likely to join.
• Skip-Level Interview: A conversation with a senior leader on values alignment and cross-team collaboration.

Levels calibrated during interviews:

• Intermediate: Independently deliver meaningful reliability improvements within a defined area.
• Senior: Own complex reliability work end to end and raise team effectiveness.
• Staff: Shape reliability across multiple teams, solving systemic problems.
• Senior Staff: Set technical direction across a broader Infrastructure area and influence organizational reliability strategy.

What you'll do

• Keep user-facing services and production systems reliable, scalable, and efficient.
• Build automation and tooling that reduces toil and replaces manual work with repeatable, infrastructure-as-code-driven workflows.
• Operate and troubleshoot production systems on Kubernetes, including deployments, rollouts, and scaling.
• Write and maintain infrastructure as code, and ship changes safely through CI/CD and GitOps.
• Participate in on-call, triage alerts, follow and improve runbooks, and escalate appropriately.
• Contribute to the observability stack, using metrics, logs, and SLOs to detect symptoms early rather than just outages.
• Take part in incident response and post-incident reviews, turning learnings into changes in automation and process.
• Document runbooks, architecture decisions, and reviews so findings become repeatable practices.

What you'll bring

• Experience keeping production systems reliable, combining an operations mindset with real software engineering practice.
• Experience building net-new infrastructure tooling and automation (e.g., Terraform modules, Kubernetes operators/controllers, or custom production automation).
• The ability to read, debug, and reason about code. Most teams work in Go; some work in Ruby.
• Experience with infrastructure as code, and with Kubernetes and its ecosystem, at a depth appropriate to your level.
• Hands-on experience with at least one major cloud provider (GCP or AWS).
• Familiarity with observability practices, including metrics, logging, alerting, and SLOs or SLIs.
• Comfort participating in on-call and incident response, with a structured approach to troubleshooting under pressure.
• Strong written communication and the ability to operate as a manager-of-one in an async, distributed environment.
• A track record of using automation, and increasingly AI, to reduce toil.