Site Reliability Engineer, Cells Infrastructure

Overview

Intermediate Site Reliability Engineer on the Cells Infrastructure team in GitLab's Scale & Architecture organization, building and operating Cells, the architecture that lets GitLab.com scale horizontally.

What you'll do

• Operate Cells in production: join the on-call rotation, respond to incidents, lead post-incident reviews, and drive corrective actions to completion.
• Define and monitor service level objectives (SLOs) for routing and cell health, and build the dashboards, alerts, and runbooks behind them.
• Provision and operate cell infrastructure on Amazon Web Services (AWS) and Google Cloud Platform (GCP), including Kubernetes, networking, Identity and Access Management (IAM), PostgreSQL, Redis, and object storage.
• Develop infrastructure as code with Terraform, Helm, and GitOps tooling such as Argo CD.
• Operate and extend the global routing layer, built on Cloudflare Workers, Envoy, and a Go service backed by Cloud Spanner, and expand routing to more protocols and services.
• Improve the continuous integration and continuous delivery (CI/CD) pipelines behind ring-based deployments, covering promotion, database migrations, quality assurance validation, and rollback.
• Support organization migrations by preparing destination cells and helping with dry runs and production cutovers.
• Work with product teams to make their services cell-compatible, and write documentation so others can operate Cells with confidence.

What you'll need

• Professional experience running production infrastructure at scale on AWS, GCP, or both, including Kubernetes.
• Strong Terraform and Helm skills.
• Proficiency in Go, or strong experience in another systems language and willingness to work in Go daily.
• Solid grounding in site reliability engineering (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: how to roll changes safely across a fleet and how to roll them back.
• A strong understanding of distributed-systems fundamentals, such as 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, and stay transparent about progress and blockers.

Nice to have

• Experience with Cloudflare, Spanner, Argo CD, TypeScript, or operating GitLab at scale.

Details

• Location: Bangalore, India.
• All-remote, asynchronous team.
• Country hiring guidelines: all roles are remote, though some roles may carry specific location-based eligibility requirements.