This is a build-it-and-run-it role. You'll provision cells, route traffic to them, deploy them safely, and keep them reliable in production. You'll also help move customer organizations onto Cells, one of GitLab's most important scaling initiatives.
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.
Take part in on-call or operational support where your team’s ownership model requires it.
What you'll bring
Professional experience running production infrastructure at scale on AWS, GCP, or both, including Kubernetes, along with 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: you 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.
Experience with Cloudflare, Spanner, Argo CD, TypeScript, or operating GitLab at scale is a plus, not a requirement.
About the team
Every team in our organization owns its services end to end, from design through on-call.We own the control plane that tracks cells and decides where each request belongs, and keep the fleet in step with GitLab's release cadence.We work closely with delivery, database, migration, and product teams across GitLab. Feature teams own how their services behave on the platform; we own the underlying infrastructure.We're an all-remote, asynchronous team. We make decisions in GitLab issues, use directly responsible individuals (DRIs) to own technical direction, demo our work weekly, and use AI-assisted workflows every day.
How GitLab Supports Full-Time Employees
Benefits to support your health, finances, and well-being
Flexible Paid Time Off
Team Member Resource Groups
Equity Compensation & Employee Stock Purchase Plan
Growth and Development Fund
Parental Leave
Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application.
Country Hiring Guidelines: GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process.
Privacy Policy: Please review our Recruitment Privacy Policy. Your privacy is important to us.
GitLab is proud to be an equal opportunity workplace and is an affirmative action employer. GitLab’s policies and practices relating to recruitment, employment, career development and advancement, promotion, and retirement are based solely on merit, regardless of race, color, religion, ancestry, sex (including pregnancy, lactation, sexual orientation, gender identity, or gender expression), national origin, age, citizenship, marital status, mental or physical disability, genetic information (including family medical history), discharge status from the military, protected veteran status (which includes disabled veterans, recently separated veterans, active duty wartime or campaign badge veterans, and Armed Forces service medal veterans), or any other basis protected by law. GitLab will not tolerate discrimination or harassment based on any of these characteristics. See also GitLab’s EEO Policy and EEO is the Law. If you have a disability or special need that requires accommodation, please let us know during the recruiting process.
