GitLab
About this role
This is the fourth remote GitLab role today and, going by the posting's own wording, the one aimed lowest: the title says Site Reliability Engineer but the overview opens by saying they are looking for an Intermediate Site Reliability Engineer. The team builds and operates Hosted Runners for GitLab Dedicated, the managed CI/CD compute that runs customer pipelines inside single tenant AWS environments. You would own infrastructure automation across the whole lifecycle: provisioning runner fleets with Terraform, extending the Go tooling and autoscaling stack, and keeping customer CI jobs running reliably. There is real depth in the AWS surface named, including EC2, Auto Scaling Groups, VPC networking, NAT, PrivateLink, IAM and ECR, and you would define service level objectives for queue times, job success rates and fleet saturation, then build the Grafana dashboards and runbooks behind them. On call is part of it.
Who this is for
What the posting asks for. GitLab publishes no years figure, but the overview describes the target level as Intermediate, which is the clearest levelling signal across GitLab's four listings today:
- Professional experience operating production infrastructure on AWS at scale, including EC2, Auto Scaling Groups, IAM and VPC networking.
- Strong infrastructure as code experience with Terraform, including writing and refactoring modules used by other teams.
- Proficiency in Go for building and debugging infrastructure tooling, or strong experience in another systems language and willingness to work in Go daily.
- Practical knowledge of CI/CD systems and job execution: how pipelines schedule work, how ephemeral build environments are provisioned and torn down, and what makes CI workloads reliable.
- Experience with observability practice including metrics, dashboards, alerting, logging and SLO based monitoring, using tools such as Prometheus, Grafana and OpenSearch.
- Experience with on call rotations and incident management for customer facing systems.
- Strong problem solving, excellent written communication, and comfort working asynchronously across the Americas, Europe, Middle East, Africa and Asia Pacific.
Nice to have:
- Direct GitLab Runner experience.
- Familiarity with configuration management such as Ansible.
- Container tooling such as Docker.
What the work actually looks like:
- Design, build and operate AWS infrastructure for Hosted Runners across many single tenant environments, spanning EC2, Auto Scaling Groups, VPC networking, subnets, NAT, network ACLs, PrivateLink, IAM and ECR.
- Develop and maintain infrastructure as code in Terraform, contributing to common modules and deployment tooling.
- Write Go for runner tooling and autoscaling components, including instance lifecycle plugins, a zero downtime deployment CLI and reusable infrastructure toolkits.
- Build and improve the GitLab CI/CD pipelines that orchestrate blue green zero downtime deployments, automated upgrades, QA validation and performance testing.
- Define and monitor service level objectives for CI job execution, and build the dashboards, alerts and runbooks behind them.
- Participate in an on call rotation, handle incidents affecting customer CI/CD workloads, and automate recurring toil away.
- Run performance and scale testing that reflects real customer workloads, and tune autoscaling for cost and reliability.
- Write documentation and runbooks so the team can operate runner stacks consistently.
Location and working pattern: all GitLab roles are remote, with some carrying location based eligibility requirements. This listing is open to India, and the posting explicitly asks for comfort working asynchronously across many time zones.
Honest fit guidance: if you have run AWS infrastructure with Terraform and are willing to work in Go daily, this is the most approachable of GitLab's four openings today. The on call rotation is stated plainly. Do not let the SRE title put you off if your Go is not deep yet, because the posting accepts strong experience in another systems language plus willingness to work in Go.
- Professional experience operating production infrastructure on AWS at scale, including EC2, Auto Scaling Groups, IAM and VPC networking.
- Strong infrastructure as code experience with Terraform, including writing and refactoring modules used by other teams.
- Proficiency in Go for building and debugging infrastructure tooling, or strong experience in another systems language and willingness to work in Go daily.
- Practical knowledge of CI/CD systems and job execution: how pipelines schedule work, how ephemeral build environments are provisioned and torn down, and what makes CI workloads reliable.
- Experience with observability practice including metrics, dashboards, alerting, logging and SLO based monitoring, using tools such as Prometheus, Grafana and OpenSearch.
- Experience with on call rotations and incident management for customer facing systems.
- Strong problem solving, excellent written communication, and comfort working asynchronously across the Americas, Europe, Middle East, Africa and Asia Pacific.
Nice to have:
- Direct GitLab Runner experience.
- Familiarity with configuration management such as Ansible.
- Container tooling such as Docker.
What the work actually looks like:
- Design, build and operate AWS infrastructure for Hosted Runners across many single tenant environments, spanning EC2, Auto Scaling Groups, VPC networking, subnets, NAT, network ACLs, PrivateLink, IAM and ECR.
- Develop and maintain infrastructure as code in Terraform, contributing to common modules and deployment tooling.
- Write Go for runner tooling and autoscaling components, including instance lifecycle plugins, a zero downtime deployment CLI and reusable infrastructure toolkits.
- Build and improve the GitLab CI/CD pipelines that orchestrate blue green zero downtime deployments, automated upgrades, QA validation and performance testing.
- Define and monitor service level objectives for CI job execution, and build the dashboards, alerts and runbooks behind them.
- Participate in an on call rotation, handle incidents affecting customer CI/CD workloads, and automate recurring toil away.
- Run performance and scale testing that reflects real customer workloads, and tune autoscaling for cost and reliability.
- Write documentation and runbooks so the team can operate runner stacks consistently.
Location and working pattern: all GitLab roles are remote, with some carrying location based eligibility requirements. This listing is open to India, and the posting explicitly asks for comfort working asynchronously across many time zones.
Honest fit guidance: if you have run AWS infrastructure with Terraform and are willing to work in Go daily, this is the most approachable of GitLab's four openings today. The on call rotation is stated plainly. Do not let the SRE title put you off if your Go is not deep yet, because the posting accepts strong experience in another systems language plus willingness to work in Go.
Apply on company site
Opens job-boards.greenhouse.io, the employer's own application page. Applying is always free.