Site Reliability Engineer, Infrastructure Platforms — UK (Intermediate to Senior Staff)

Because this is a single application for SRE roles across Infrastructure Platforms, our process is built to evaluate you once and match you well, rather than interviewing separately for every team.

Recruiter Screen: A conversation about your background, what you're looking for, and the level and teams that fit, so we can point your process in the right direction.

Core Technical: The shared assessment every SRE candidate takes, regardless of eventual team. A low-stress, collaborative discussion covering system architecture and incident review.

Hiring Manager Interview: A conversation about ownership, judgment, execution, collaboration, and growth, the non-technical signals that make an SRE effective at GitLab.

Peer Technical: Team-specific depth, run by SREs from the team you're most likely to join, focused on the problems that team actually works on.

Skip-Level Interview: A conversation with a senior leader on values alignment, and how you'll work across teams.

After your interviews, we consider your performance alongside our current hiring needs to confirm the level and team where you'll do your best work. Interview results are a major factor, and final placement also reflects our active hiring priorities at the time.

Intermediate: You independently deliver meaningful reliability improvements within a defined area.

Senior: You own complex reliability work end to end and raise the effectiveness of your team.

Staff: You shape reliability across multiple teams, solving systemic problems and creating approaches others can reuse.

Senior Staff: You set technical direction across a broader Infrastructure area and influence reliability strategy at organizational scale.

Keep user-facing services and production systems reliable, scalable, and efficient

Build automation and tooling that reduces toil and replaces manual work with repeatable, infrastructure-as-code-driven workflows

Operate and troubleshoot production systems on Kubernetes, including deployments, rollouts, and scaling

Write and maintain infrastructure as code, and ship changes safely through CI/CD and GitOps

Participate in on-call, triage alerts, follow and improve runbooks, and escalate appropriately

Contribute to the observability stack, using metrics, logs, and SLOs to detect symptoms early rather than just outages

Take part in incident response and post-incident reviews, turning learnings into changes in automation and process

Document runbooks, architecture decisions, and reviews so your findings become repeatable practices

Experience keeping production systems reliable, combining an operations mindset with real software engineering practice

Experience building net-new infrastructure tooling and automation, not just configuring existing tools. For example, Terraform modules, Kubernetes operators or controllers, or production automation and services written from scratch

The ability to read, debug, and reason about code. Most of our teams work in Go; some work in Ruby. You can discuss a piece of code's behavior, performance, and failure modes

Experience with infrastructure as code, and with Kubernetes and its ecosystem, at a depth appropriate to your level

Hands-on experience with at least one major cloud provider (GCP or AWS)

Familiarity with observability practices, including metrics, logging, alerting, and SLOs or SLIs, and using data to inform operational decisions

Comfort participating in on-call and incident response, with a structured approach to troubleshooting under pressure

Strong written communication and the ability to operate as a manager-of-one in an async, distributed environment

A track record of using automation, and increasingly AI, to reduce toil and improve how you and your team work

Alignment with GitLab's values and a commitment to working in accordance with them

Infrastructure Platforms is responsible for the availability, reliability, performance, and scalability of GitLab’s user-facing services, most notably GitLab.com . The organization spans teams across Production Engineering , GitLab Dedicated , GitLab Delivery , and Developer Experience , covering everything from the production fleet and networking platform to observability, incident response, deployment infrastructure, tenant scale, and our single-tenant Dedicated offering. We are a globally distributed, remote-first organization that works asynchronously, favors automation over toil, and uses monitoring, metrics, and clear ownership to continuously improve the reliability of GitLab at scale. For more on how we work, see the Infrastructure Handbook Page .

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 .