Platforms Engineering

<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&nbsp;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><span style="font-weight: 400;">Site Reliability Engineers (SREs) are responsible for keeping all user-facing services and other GitLab production systems running smoothly. SREs are a blend of pragmatic operators and software craftspeople that apply sound engineering principles, operational discipline, and mature automation to our environments and the GitLab codebase. We specialize in systems, whether it be networking, the Linux kernel, or some more specific interest in scaling, algorithms, or distributed systems.</span></p> <p><span style="font-weight: 400;">GitLab.com is a unique site and it brings unique challenges–it’s the biggest GitLab instance in existence. In fact, it’s one of the largest single-tenancy open-source SaaS sites on the internet. The experience of our team feeds back into other engineering groups within the company, as well as to GitLab customers running self-managed installations</span></p> <h3><strong>Responsibilities</strong></h3> <ul> <li style="font-weight: 400;"><span style="font-weight: 400;">Automating every operational task is a core requirement for this role. For example, package updates, configuration changes across all environments, creating tools for automatic provisioning of user facing services, etc.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Responding to platform emergencies, alerts, and escalations from Customer Support.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Ensure systems exist to manage software life-cycles (e.g. Operating Systems) with a minimum of manual effort.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Develop a fully automated multi-environment observability stack based on the existing SaaS system, and extend it to predict capacity needs based on the usage patterns.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Plan for new service roll-outs, expansion and capacity management of existing services, and work with users to optimise their resource consumption.</span></li> </ul> <h3><strong>As an SRE you will:</strong></h3> <ul> <li style="font-weight: 400;"><span style="font-weight: 400;">Be on a PagerDuty rotation to respond to GitLab.com availability incidents and provide support for service engineers with customer incidents.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Analyze existing, create and maintain new GitLab.com</span><a href="https://en.wikipedia.org/wiki/Service-level_objective"><span style="font-weight: 400;"> Service Level Objectives</span></a><span style="font-weight: 400;">.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Troubleshoot, evaluate and resolve operational challenges contributing to defined SLO's.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Define, improve, and engage in adapting architectural application bottlenecks as observed on GitLab.com.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Work with other engineering stakeholders on resolving larger architectural bottlenecks and participate by offering GitLab.com point of view.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Work in close collaboration with software development teams to shape the future roadmap and establish strong operational readiness across teams.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Scale systems through automation, improving change velocity and reliability.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Leverage technical skills to partner with team members and be comfortable diving into a problem as needed.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Work with counterparts in other teams of the Infrastructure department to improve infrastructure running with Chef, Terraform and Kubernetes.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Make monitoring and alerting alert on symptoms and not on outages.</span></li> <li style="font-weight: 400;"><a href="https://gitlab.com/gitlab-com/runbooks"><span style="font-weight: 400;">Document every action</span></a><span style="font-weight: 400;"> so your findings turn into repeatable actions–and then into automation.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Debug production issues across services and levels of the stack.</span></li> </ul> <h3><strong>You may be a fit to this role if you:</strong></h3> <ul> <li style="font-weight: 400;"><span style="font-weight: 400;">Are able to reason about large systems - how they work on large scale, edge cases, failure modes, behaviors.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Know your way around Linux and the Unix Shell.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Have experience in collaborating and communicating asynchronously.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Have an urge to document all the things so you don't need to learn the same thing twice.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Have an enthusiastic, go-for-it attitude. When you see something broken, you can't help but fix it.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Have a strong sense for action and know how to iterate through a problem quickly.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Share our values, and work in accordance with those values.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Have experience with Nginx, HAProxy, Docker, Kubernetes, Terraform, or similar technologies.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Are able to leverage GitLab as your day to day go-to tool.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Bonus: Strong programming skills as a (former) backend engineer - Preferably with Ruby and/or Go.</span></li> </ul> <h3><strong>Projects you could work on:</strong></h3> <ul> <li style="font-weight: 400;"><span style="font-weight: 400;">Working from the Reliability team’s</span><a href="https://gitlab.com/gitlab-com/gl-infra/infrastructure"><span style="font-weight: 400;"> issue tracker</span></a><span style="font-weight: 400;">, driving changes required to reliably support GitLab at GitLab.com size.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Work on the GitLab core projects such as,</span><a href="https://gitlab.com/gitlab-org/gitlab"> <span style="font-weight: 400;">GitLab Rails</span></a><span style="font-weight: 400;">,</span><a href="https://gitlab.com/gitlab-org/gitlab-workhorse"> <span style="font-weight: 400;">GitLab Workhorse</span></a><span style="font-weight: 400;">,</span><a href="https://gitlab.com/gitlab-org/gitaly"> <span style="font-weight: 400;">Gitaly</span></a><span style="font-weight: 400;">, etc.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Work on projects that create deployment packages of GitLab such as,</span><a href="https://gitlab.com/gitlab-org/charts/gitlab"> <span style="font-weight: 400;">GitLab Helm Chart</span></a><span style="font-weight: 400;">,</span><a href="https://gitlab.com/gitlab-org/omnibus-gitlab/"> <span style="font-weight: 400;">omnibus-gitlab</span></a><span style="font-weight: 400;">, etc.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Coding infrastructure automation with</span><a href="https://gitlab.com/gitlab-cookbooks/"><span style="font-weight: 400;"> Chef</span></a><span style="font-weight: 400;"> and Terraform.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Improving our</span><a href="https://gitlab.com/gitlab-cookbooks/gitlab-prometheus"><span style="font-weight: 400;"> Prometheus Monitoring</span></a><span style="font-weight: 400;"> or building new</span><a href="https://gitlab.com/gitlab-org/gitlab-monitor"><span style="font-weight: 400;"> Metrics</span></a></li> </ul> <h3>&nbsp;</h3> <h3><strong>Senior Site Reliability Engineer Criteria</strong></h3> <p><span style="font-weight: 400;">Technical:</span></p> <ol> <li style="font-weight: 400;"><span style="font-weight: 400;">Deep knowledge in</span><a href="https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/job-families/engineering/site-reliability-engineer/index.html.md#technical"><span style="font-weight: 400;"> 2 areas of expertise</span></a><span style="font-weight: 400;"> and general knowledge of all areas of expertise. Capable of mentoring Junior in all areas and other SRE in their area of deep knowledge.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Contributes small improvements to the GitLab codebase to resolve issues</span></li> </ol> <p><span style="font-weight: 400;">Execution:</span></p> <ol> <li style="font-weight: 400;"><span style="font-weight: 400;">Identifies significant projects that result in substantial cost savings or revenue</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Identifies changes for the product architecture from the reliability, performance and availability perspective with a data driven approach.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Proactively work on the efficiency and capacity planning to set clear requirements and reduce the system resources usage to make GitLab cheaper to run for all our customers.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Identify parts of the system that do not scale, provides immediate palliative measures and drives long term resolution of these incidents.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Identify Service Level Indicators (SLIs) that will align the team to meet the availability and latency objectives.</span></li> </ol> <p><span style="font-weight: 400;">Collaboration and Communication:</span></p> <ol> <li style="font-weight: 400;"><span style="font-weight: 400;">Know a domain really well and radiate that knowledge</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Perform and run blameless RCAs on incidents and outages aggressively looking for answers that will prevent the incident from ever happening again.</span></li> </ol> <p><span style="font-weight: 400;">Influence and Maturity:</span></p> <ol> <li style="font-weight: 400;"><span style="font-weight: 400;">Lead Production SREs and Junior Production SREs by setting the example.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Show ownership of a major part of the infrastructure.</span></li> <li style="font-weight: 400;"><span style="font-weight: 400;">Trusted to de-escalate conflicts inside the team</span></li> </ol> <h3><strong>Performance Indicators</strong></h3> <p><span style="font-weight: 400;">Site Reliability Engineers have the following job-family performance indicators:</span></p> <ul> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#gitlab-com-availability"><span style="font-weight: 400;">GitLab.com Availability</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#gitlab-com-performance"><span style="font-weight: 400;">GitLab.com Performance</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#apdex-and-error-slo-per-service"><span style="font-weight: 400;">Apdex and Error SLO per Service</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#mean-time-to-detection-mttd"><span style="font-weight: 400;">Mean Time to Detection</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#mean-time-to-resolution-mttr"><span style="font-weight: 400;">Mean Time to Resolution</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#mean-time-between-failures-mtbf"><span style="font-weight: 400;">Mean Time Between Failure</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#mean-time-to-production-mttp"><span style="font-weight: 400;">Mean Time to Production</span></a></li> <li style="font-weight: 400;"><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/#disaster-recovery-dr-time-to-recover"><span style="font-weight: 400;">Disaster Recovery Time to Recovery</span></a></li> </ul> <h3><strong>Compensation</strong></h3> <p><span style="font-weight: 400;">Please view the compensation range for this role at the bottom of the</span><a href="https://about.gitlab.com/job-families/engineering/site-reliability-engineer/"> <span style="font-weight: 400;">position description</span></a><span style="font-weight: 400;">.</span></p> <p>&nbsp;</p><div class="content-pay-transparency"><div class="pay-input"><div class="description"><p><em>The base salary range for this role’s listed level is currently for residents of the&nbsp;United States only. This range is intended to reflect the role's base salary rate in locations throughout the US.&nbsp;Grade level and salary ranges are determined through interviews and a review of education, experience, knowledge, skills, abilities of the applicant, equity with other team members, alignment with market data,&nbsp;and geographic location.&nbsp;The base salary range does not include any bonuses, equity, or benefits. See more information on our <a class="waffle-rich-text-link" href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/" data-sheets-formula-bar-text-link="https://bit.ly/GLBeneUS" data-sheets-formula-bar-text-style="font-size:12px;color:#1155cc;font-weight:normal;text-decoration:underline;font-family:''Arial'';font-style:normal;text-decoration-skip-ink:none;">benefits</a><span data-sheets-formula-bar-text-style="font-size:12px;color:#000000;font-weight:normal;text-decoration:none;font-family:'Arial';font-style:normal;text-decoration-skip-ink:none;"> and </span><a class="waffle-rich-text-link" href="https://about.gitlab.com/handbook/stock-options/" data-sheets-formula-bar-text-link="https://bit.ly/GLequity" data-sheets-formula-bar-text-style="font-size:12px;color:#1155cc;font-weight:normal;text-decoration:underline;font-family:''Arial'';font-style:normal;text-decoration-skip-ink:none;">equity</a>. Sales roles are also eligible for incentive pay targeted at up to 100% of the offered base salary.</em></p></div><div class="title">United States Salary Range</div><div class="pay-range"><span>$1</span><span class="divider">&mdash;</span><span>$1 USD</span></div></div></div><div class="content-conclusion"><h4><strong>How GitLab Supports Full-Time Employees</strong></h4> <ul> <li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/">Benefits to support your health, finances, and well-being</a></li> <li><a href="https://handbook.gitlab.com/handbook/people-group/time-off-and-absence/time-off-types/#flexible-paid-time-off-pto">Flexible Paid Time Off&nbsp;</a></li> <li><a href="https://handbook.gitlab.com/handbook/company/culture/inclusion/tmrg-tmag/">Team Member Resource Groups</a></li> <li><a href="https://handbook.gitlab.com/handbook/total-rewards/stock-options/">Equity Compensation &amp; Employee Stock Purchase Plan</a></li> <li><a href="https://handbook.gitlab.com/handbook/people-group/learning-and-development/growth-and-development/">Growth and Development Fund</a></li> <li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave">Parental Leave</a>&nbsp;</li> </ul> <p>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 <a href="https://about.gitlab.com/company/culture/inclusion/#examples-of-select-underrepresented-groups">underrepresented groups</a> 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.</p> <hr> <p><strong>Country Hiring Guidelines: </strong>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.&nbsp;&nbsp;</p> <p><strong>Privacy Policy: </strong>Please review our <a href="https://handbook.gitlab.com/handbook/hiring/candidate-faq/recruitment-privacy-policy/" target="_blank">Recruitment Privacy Policy.</a> Your privacy is important to us.</p> <p>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&nbsp;<a href="https://about.gitlab.com/handbook/people-policies/inc-usa/#equal-employment-opportunity-policy" target="_blank">GitLab’s EEO Policy</a>&nbsp;and&nbsp;<a href="https://about.gitlab.com/handbook/labor-and-employment-notices/#eeoc-us-equal-employment-opportunity-commission-notices" target="_blank">EEO is the Law</a>. If you have a disability or special need that requires&nbsp;<a href="https://about.gitlab.com/handbook/people-policies/inc-usa/#reasonable-accommodation" target="_blank">accommodation</a>, please let us know during the&nbsp;<a href="https://about.gitlab.com/handbook/hiring/interviewing/#adjustments-to-our-interview-process" target="_blank">recruiting process</a>.</p></div>