GitLab
Publicado originalmente en greenhouse · Aplica desde el sitio de la empresa para mejor experiencia.
<div class="content-intro"><p>GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster.</p> <p>The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. <a href="https://www.youtube.com/watch?v=OuZIb5zszQI">Co-create the future with us</a> as we build technology that transforms how the world develops software.</p> <p>*<em>Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license. Claim based on GitLab data. Fortune 100 refers to the top 20% ranked companies in the 2025 Fortune 500 list, published in June 2025. Fortune and Fortune Media IP Limited are not affiliated with, and do not endorse products or services of GitLab.</em></p></div><p><strong>An overview of this role</strong></p> <p>Site Reliability Engineers keep GitLab's user-facing services and production systems running reliably at scale. They combine software engineering with operational excellence, applying sound engineering principles, automation, and continuous improvement to build, operate, and evolve our production infrastructure.</p> <p>This is a single application for Site Reliability Engineering opportunities across our Infrastructure Platforms department. Rather than asking you to choose the right team or level upfront, we evaluate your skills holistically and match you to the opportunity that best aligns with your experience and our hiring needs. We hire Site Reliability Engineers from Intermediate through Senior Staff across multiple Infrastructure Platforms teams.</p> <p>We don't expect every candidate to have experience with every technology in our environment. We're looking for engineers with strong technical fundamentals, a growth mindset, and the ability to learn quickly. We'll support you in becoming successful with GitLab's tools, systems, and ways of working.</p> <p><strong>How our SRE hiring works</strong></p> <p>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.</p> <ul> <li><strong>Recruiter Screen:</strong> 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.</li> <li><strong>Core Technical: </strong>The shared assessment every SRE candidate takes, regardless of eventual team. A low-stress, collaborative discussion covering source code, system architecture, and incident review.</li> <li><strong>Peer Technical: </strong>Team-specific depth, run by SREs from the team you're most likely to join, focused on the problems that team actually works on.</li> <li><strong>Hiring Manager Interview: </strong>A conversation about ownership, judgment, execution, collaboration, and growth, the non-technical signals that make an SRE effective at GitLab.</li> <li><strong>Skip-Level Interview: </strong>A conversation with a senior leader on values alignment, and how you'll work across teams.</li> </ul> <p>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.</p> <p><strong>What level am I?</strong></p> <p>We calibrate your level during the process, but here is roughly what each looks like so you know where you might land.</p> <p><strong>Intermediate</strong></p> <ul> <li>You make meaningful contributions to reliability, automation, and operational efficiency, working independently within a scoped area</li> <li>You diagnose issues on your own, understand system dependencies, and can explain the tradeoffs you made</li> <li>You prioritize well, break work into manageable steps, and use automation to reduce toil</li> <li>You document your work clearly and keep yourself moving without needing check-ins</li> </ul> <p><strong>Senior</strong></p> <ul> <li>You drive reliability improvements across multiple projects or services and prioritize them based on real system needs</li> <li>You lead investigations, anticipate cascading failures, and coordinate incident response</li> <li>You own delivery end to end, unblock others, and improve the patterns your team works by</li> <li>You communicate complex ideas clearly, influence how work gets done, and enable coordination across teams</li> </ul> <p><strong>Staff</strong></p> <ul> <li>You shape reliability strategy across teams and services and define patterns that others reuse</li> <li>You introduce prevention strategies, identify systemic weaknesses, and influence incident response practices beyond your immediate area</li> <li>You design execution and automation approaches that work at organizational scale</li> <li>You connect reliability work to platform and business needs</li> </ul> <p><strong>Senior Staff</strong></p> <ul> <li>You set technical direction for reliability across a sub-department, not just a team</li> <li>You drive the hardest, most ambiguous systems problems and establish standards and guardrails that multiple teams adopt</li> <li>You mentor Staff and Senior engineers</li> <li>You align reliability strategy with long-range platform direction and represent Infrastructure's interests across the wider Engineering organization</li> </ul> <p><strong>What you'll do</strong></p> <ul> <li>Keep user-facing services and production systems reliable, scalable, and efficient</li> <li>Build automation and tooling that reduces toil and replaces manual work with repeatable, infrastructure-as-code-driven workflows</li> <li>Operate and troubleshoot production systems on Kubernetes, including deployments, rollouts, and scaling</li> <li>Write and maintain infrastructure as code, and ship changes safely through CI/CD and GitOps</li> <li>Participate in on-call, triage alerts, follow and improve runbooks, and escalate appropriately</li> <li>Contribute to the observability stack, using metrics, logs, and SLOs to detect symptoms early rather than just outages</li> <li>Take part in incident response and post-incident reviews, turning learnings into changes in automation and process</li> <li>Document runbooks, architecture decisions, and reviews so your findings become repeatable practices</li> </ul> <p><strong>What you'll bring</strong></p> <ul> <li>Experience keeping production systems reliable, combining an operations mindset with real software engineering practice</li> <li>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</li> <li>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</li> <li>Experience with infrastructure as code, and with Kubernetes and its ecosystem, at a depth appropriate to your level</li> <li>Hands-on experience with at least one major cloud provider (GCP or AWS)</li> <li>Familiarity with observability practices, including metrics, logging, alerting, and SLOs or SLIs, a