Staff Site Reliability Engineer, Environment Automation at GitLab

Staff site reliability engineer for environment automation at GitLab Bengaluru, building automation that provisions hundreds of isolated environments.

This full-time Bengaluru role was posted on 18 September 2026. The listing describes building and scaling multi-tenant infrastructure: designing and implementing automation that provisions and manages hundreds of isolated environments, and troubleshooting issues across Kubernetes clusters, cloud services and GitLab applications. Requirements include proven ability to operate and troubleshoot production workloads across multiple tenants, and strong hands-on Terraform experience including workspace strategies and state management.

About GitLab

GitLab builds a DevSecOps platform that covers source code management, CI/CD, security scanning and planning in a single application. Its listings state that more than 50 million registered users and more than half of the Fortune 100 use the platform.

GitLab operates as an all-remote company with team members in many countries, including India. Its public handbook and listing pages describe an asynchronous, documentation-heavy way of working, and its listings note that team members are expected to use AI tooling in daily workflows. Learn more on GitLab's website.

The role in plain terms

Environment automation at this scale - hundreds of isolated environments - is infrastructure-as-product work: the environments serve GitLab's own development and Dedicated customers, so provisioning reliability is on the critical path. The Terraform requirement is specified down to workspace strategies and state management, which signals the loop will test real IaC depth, not surface familiarity. Staff level means you set the automation architecture, not just write modules.

The team and the work

Per the listing, the work spans Kubernetes, cloud services and the GitLab application stack itself, so troubleshooting crosses infrastructure and application boundaries.

What the employer asks for

These requirements are quoted from the employer's listing, kept in their exact words so eligibility details are not distorted:

Production-Scale Experience: Proven ability to operate and troubleshoot production workloads across multiple tenants or environments. Deep understanding of how distributed systems fail at scale and...
Terraform & IaC Mastery: Strong hands-on experience with Terraform, including workspace strategies, state management, and automation patterns that scale. Comfortable solving state isolation issues and...
Kubernetes in Production: Skilled at diagnosing deployment failures, interpreting pod logs, and debugging scheduling issues and rollback scenarios in live environments. Understands how pods, ReplicaSets,...
Programming & Code Analysis: Ability to read and debug code in Go and/or Ruby. Familiar with identifying performance issues, scalability concerns, and contributing to infrastructure...
Large Scale Operations Background: Experience supporting infrastructure for many customers or environments simultaneously. Comfortable managing isolation, scaling, monitoring, and incident response across diverse workloads.
Architecture & Incident Response: Able to reason through complex systems and operational challenges. Brings on-call experience and can lead technical discussions and incident resolution efforts...
Customer-Focused Collaboration: Proven ability to work across teams and with internal or external customers to solve technical problems while maintaining service commitments and clear communication.
GitLab Platform Proficiency: Comfortable using GitLab as a daily tool for infrastructure automation, collaboration, and operational workflows.

Who this role suits

Staff SREs with multi-tenant production experience and deep Terraform mastery. Not for SREs whose IaC experience is secondary, or platform engineers without multi-tenant scale exposure.

Practical notes

For environment-automation roles, expect IaC design questions (state layout, workspace strategy, drift) plus a multi-tenant incident scenario. Scale numbers from your own environment work make answers concrete.

Working at GitLab

Roles at GitLab span the product itself (backend in Ruby and Go, frontend, security, infrastructure) plus internal systems teams that build the company's own tooling and automations.

How to apply

Apply directly on the employer's site: Staff Site Reliability Engineer, Environment Automation at GitLab. We found this listing on the Greenhouse public job board (job-boards.greenhouse.io), where it was posted on 18 Sep 2026 and was still open when we checked on 30 Oct 2026. Before applying, re-read the employer's own description in full, since eligibility details, deadlines and process steps can change at any time and the employer's page is always the final word. Tailor your resume to the specific requirements above rather than sending a generic one: mirror the skills and tools the listing names where you genuinely have them. A short, specific note on why this team and this problem interest you goes further than a long generic cover letter. Never pay a fee to apply or interview; genuine employers, including this one, do not charge candidates.

Related openings on GetFirstJob

If this role is not the right fit, these current openings are in a similar area:

We write and maintain this page from the employer's public listing and link straight to their application page. We do not act as a recruiter, and applying is always free. If the link above stops working, the role has likely been filled.

This is our short summary of the employer's listing. The full description, eligibility and deadline are on the employer's page.