SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
GitLab is seeking an Intermediate Site Reliability Engineer to join the Cells Infrastructure team within the Scale & Architecture organization. Cells is GitLab's horizontal scaling architecture that splits GitLab.com into independent units, each with its own application and data stack, behind a shared routing layer.
This is a build-it-and-run-it role combining infrastructure development with production operations. You will provision cells, route traffic to them, deploy safely, and maintain reliability in production. Key responsibilities include:
- Operating Cells in production: join on-call rotation, respond to incidents, lead post-incident reviews, and drive corrective actions
- Define and monitor service level objectives (SLOs) for routing and cell health; build dashboards, alerts, and runbooks
- Provision and operate cell infrastructure on AWS and GCP, including Kubernetes, networking, IAM, PostgreSQL, Redis, and object storage
- Develop infrastructure as code using Terraform, Helm, and GitOps tooling (Argo CD)
- Operate and extend the global routing layer built on Cloudflare Workers, Envoy, and a Go service backed by Cloud Spanner
- Improve CI/CD pipelines for ring-based deployments, covering promotion, database migrations, QA validation, and rollback
- Support organization migrations by preparing destination cells and assisting with dry runs and production cutovers
- Collaborate with product teams to make services cell-compatible and write operational documentation
The team owns services end-to-end from design through on-call, works closely with delivery, database, migration, and product teams, and operates as an all-remote, asynchronous organization using GitLab issues for decisions and DRIs for technical direction.
REQUIREMENTS:
- Professional experience running production infrastructure at scale on AWS, GCP, or both, including Kubernetes, with strong Terraform and Helm skills
- Proficiency in Go, or strong experience in another systems language with willingness to work in Go daily
- Solid grounding in SRE best practices: SLOs and error budgets, blameless post-incident reviews, reducing toil through automation, capacity planning, and designing for graceful degradation
- Experience owning services in production, including on-call, incident response, and monitoring with tools such as Prometheus and Grafana
- Practical knowledge of progressive delivery: rolling changes safely across a fleet and rolling them back
- Strong understanding of distributed-systems fundamentals: request routing, proxies, consistency, and failure domains
- Experience working effectively in distributed, all-remote teams: default to asynchronous, written-first communication; document decisions in issues and merge requests; hand off work cleanly across time zones; stay transparent about progress and blockers
- Plus (not required): Experience with Cloudflare, Spanner, Argo CD, TypeScript, or operating GitLab at scale
