Senior Site Reliability Engineer, Environment Automation

An overview of this role

As a Site Reliability Engineer (SRE) at GitLab, you’ll help keep all user-facing services and production systems reliable, scalable, and efficient. Our SREs combine a pragmatic operations mindset with strong software engineering practices to drive automation, reduce toil, and improve resilience across our platform.

In the Environment Automation specialization, your focus is on operating and automating hundreds of GitLab environments—from initial provisioning to day-to-day maintenance tasks. 

Unlike other SRE roles, this position centers on automating the lifecycle of many tenant environments, ensuring they remain secure, consistent, and reliable at scale.

• Some examples of the projects you could work on:
• Designing infrastructure automation that provisions and operates GitLab environments using Terraform, Ansible, and Kubernetes
• Creating and maintaining deployment packages for GitLab, such as Helm Charts and omnibus-gitlab
• Building and operating Dedicated GitLab instances integrated with cloud-native services (e.g., GCP, AWS)
• Developing tools to orchestrate infrastructure-as-code workflows across multiple tenants
• Deploying and managing microservices on Kubernetes clusters at scale
• Enhancing GitLab’s observability stack (e.g., Prometheus, ELK) to support proactive monitoring and incident response
• Integrating with and operating infrastructure in cloud provider ecosystems (e.g., IAM, networking, storage)
• Championing and implementing cloud security best practices across automated infrastructure

What You'll Do

• Build & Scale Multi-Tenant Infrastructure: Design and implement automation that provisions and manages hundreds of isolated GitLab environments using Terraform, Ansible, and Kubernetes. Manage complex state strategies and workspace configurations to support scale and maintainability.
• Debug & Resolve Production Issues: Troubleshoot issues across Kubernetes clusters, cloud services, and GitLab apps—identifying root causes of failed deployments, crash loops, and scheduling conflicts to ensure service continuity.
• Automate Operations at Scale: Replace manual workflows with infrastructure-as-code solutions, including automated version upgrades, configuration rollouts, and provisioning pipelines that operate reliably across all tenants.
• Monitor & Predict Capacity: Build observability systems that detect bottlenecks, predict usage trends, and optimize resource consumption using tools like Prometheus, ELK, and Grafana.
• Res