<div class="content-intro"><p>The GitLab&nbsp;<a class="c-link" href="https://about.gitlab.com/solutions/devops-platform/" target="_blank" data-stringify-link="https://about.gitlab.com/solutions/devops-platform/" data-sk="tooltip_parent" data-remove-tab-index="true">DevSecOps platform</a>&nbsp;empowers 100,000+ organizations to deliver software faster and more efficiently. We are one of the&nbsp;<a class="c-link" href="https://about.gitlab.com/company/culture/all-remote/guide/" target="_blank" data-stringify-link="https://about.gitlab.com/company/culture/all-remote/guide/" data-sk="tooltip_parent" data-remove-tab-index="true">world’s largest all-remote companies</a>&nbsp;with 2,000+ team members and&nbsp;<a class="c-link" href="https://handbook.gitlab.com/handbook/values/" target="_blank" data-stringify-link="https://about.gitlab.com/handbook/values/" data-sk="tooltip_parent" data-remove-tab-index="true">values</a>&nbsp;that foster a culture where people embrace the belief that everyone can contribute. Learn more about&nbsp;<a class="c-link" href="https://vimeo.com/778157354" target="_blank" data-stringify-link="https://vimeo.com/778157354" data-sk="tooltip_parent" data-remove-tab-index="true">Life at GitLab</a>.</p></div><p>As a Site Reliability Engineer at GitLab, you are responsible for keeping all user-facing services and other GitLab production systems running smoothly. Our SREs are a blend of pragmatic operators and software craftspeople that apply sound engineering principles, operational discipline, and mature automation to our operating environments and the GitLab codebase.</p>
<p>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 SaaS sites on the internet developed and run with transparency in mind. GitLab.com runs using the same tools we provide to GitLab customers running self-managed installations. The experience of our team feeds back into other engineering groups within the company, as well as self-managed customers.</p>
<p>SRE's with Scalability specialization focus on how to scale both the application and the infrastructure supporting the application. This is the main difference between a Scalability SRE and other SRE’s at GitLab, is that your day to day will be spent looking at how to enable other engineers at GitLab to incorporate availability, reliability and performance considerations into their daily work. We do this by providing access to information and systems in a safe and sustainable way. We do this for our application and aim to extend this offering to our infrastructure and services. .</p>
<p><strong>Some examples of projects you could work:</strong></p>
<ul>
<li>Working from the Scalability team’s<a href="https://gitlab.com/gitlab-com/gl-infra/scalability"> issue tracker</a>, driving changes required to <a href="https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/148">&nbsp;scale GitLab at GitLab.com size.</a></li>
<li><a href="https://about.gitlab.com/handbook/engineering/architecture/workflow/">Architectural Blueprints</a> used to define how the component fits into a bigger picture</li>
<li><a href="https://docs.gitlab.com/">Developer Documentation and Guidelines</a> used to ensure consistency between multiple components</li>
<li>Self-service deployment and management tools, used to ensure simpler maintenance of the component</li>
<li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/service-maturity-model/">Service Maturity Model</a>, ensuring that the component has consistent interfaces necessary to operate a robust and reliable component</li>
<ul>
<li>Observability and Forecasting Tools</li>
<li>Logging and Alerting Guidelines</li>
<li><a href="https://gitlab.com/gitlab-com/runbooks/">Operational Runbooks</a></li>
</ul>
</ul>
<p><strong>What you'll do</strong></p>
<ul>
<li>Be on a PagerDuty rotation to respond to GitLab.com availability incidents and provide support for service engineers with customer incidents.</li>
<li>Analyze existing, create and maintain new GitLab.com<a href="https://en.wikipedia.org/wiki/Service-level_objective"> Service Level Objectives</a>.</li>
<li>Troubleshoot, evaluate and resolve operational challenges contributing to defined SLO's.</li>
<li>Define, improve, and engage in adapting architectural application bottlenecks as observed on GitLab.com.</li>
<li>Work with other engineering stakeholders on resolving larger architectural bottlenecks and participate by offering GitLab.com point of view.</li>
<li>Work in close collaboration with software development teams to shape the future roadmap and establish strong operational readiness across teams.</li>
<li>Scale systems through automation, improving change velocity and reliability.</li>
<li>Leverage technical skills to partner with team members and be comfortable diving into a problem as needed.</li>
<li>Work with counterparts in other teams of the Infrastructure department to improve infrastructure running with Chef, Terraform and Kubernetes.</li>
<li>Make monitoring and alerting alert on symptoms and not on outages.</li>
<li><a href="https://gitlab.com/gitlab-com/runbooks">Document every action</a> so your findings turn into repeatable actions–and then into automation.</li>
<li>Debug production issues across services and levels of the stack.</li>
</ul>
<p>&nbsp;</p>
<p><strong>What you'll bring</strong></p>
<ul>
<li>Strong programming skills - Preferably with Ruby and/or Go.</li>
<li>Production experience with the Kubernetes ecosystem</li>
<li>SRE experience in running and operating distributed systems is a bonus</li>
<li>Are able to reason about large systems - how they work on large scale, edge cases, failure modes, behaviors.</li>
<li>Know your way around Linux and the Unix Shell.</li>
<li>Have experience in collaborating and communicating asynchronously.</li>
<li>Have an urge to document all the things so you don't need to learn the same thing twice.</li>
<li>Have an enthusiastic, go-for-it attitude. When you see something broken, you can't help but fix it.</li>
<li>Have a strong sense for action and know how to iterate through a problem quickly.</li>
<li>Share our values, and work in accordance with those values.</li>
<li>Have experience with Nginx, HAProxy, Docker, Terraform, or similar technologies.</li>
<li>A solid understanding of, and experience with, implementing and working&nbsp; with SLI/SLO&nbsp;</li>
<li>Are able to leverage GitLab as your day-to-day go-to tool.</li>
</ul>
<p><strong><br>About the team</strong></p>
<p>The Practices team focuses on tools and frameworks that enable the stage groups to support their features on our production systems. These challenges exist in high-load, critical services without dedicated owners, shared architectures, and complex operational configurations. The expertise within the Practices team helps overcome these challenges by responding to technical needs, promoting uniform processes, and increasing engineering efficiency by eliminating toil.&nbsp;</p>
<h4><strong>How GitLab will support you</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://about.gitlab.com/company/culture/all-remote/guide/">All remote</a>, <a href="https://about.gitlab.com/company/culture/all-remote/asynchronous/">asynchronous</a> work environment</li>
<li><a href="https://about.gitlab.com/handbook/paid-time-off/">Flexible Paid Time Off</a></li>
<li><a href="https://about.gitlab.com/company/culture/inclusion/erg-guide/#:~:text=Definition%20of%20the%20TMRG%20%2D%20Team%20Member%20Resource%20Groups,-TMRGs%20are%20voluntary&amp;text=The%20purpose%20for%20this%20type,developing%20the%20sense%20of%20belonging.">Team Member Resource Groups</a></li>
<li><a href="https://about.gitlab.com/handbook/stock-options/">Equity Compensation &amp; Employee Stock Purchase Plan</a></li>
<li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#growth-and-development-benefit">Growth and development budget&nbsp;</a></li>
<li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave">Parental leave</a>&nbsp;</li>
<li><a href="https://about.gitlab.com/handbook/finance/procurement/office-equipment-supplies/">Home office</a> support</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><div class="content-pay-transparency"><div class="pay-input"><div class="description"><em><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;">The base salary range for this role’s listed level is currently for residents of listed locations only. 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, and alignment with market data. See more information on our </span><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><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;">. Sales roles are also eligible for incentive pay targeted at up to 100% of the offered base salary.</span></em></div><div class="title">Colorado/Washington pay range</div><div class="pay-range"><span>$124,300</span><span class="divider">&mdash;</span><span>$239,700 USD</span></div></div><div class="pay-input"><div class="title">California/New York/New Jersey pay range</div><div class="pay-range"><span>$124,300</span><span class="divider">&mdash;</span><span>$266,400 USD</span></div></div></div><div class="content-conclusion"><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://about.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>

The GitLab [DevSecOps platform](https://about.gitlab.com/solutions/devops-
platform/) empowers 100,000+ organizations to deliver software faster and more
efficiently. We are one of the [world’s largest all-remote
companies](https://about.gitlab.com/company/culture/all-remote/guide/) with
2,000+ team members and [values](https://handbook.gitlab.com/handbook/values/)
that foster a culture where people embrace the belief that everyone can
contribute. Learn more about [Life at GitLab](https://vimeo.com/778157354).

As a Site Reliability Engineer at GitLab, you are responsible for keeping all
user-facing services and other GitLab production systems running smoothly. Our
SREs are a blend of pragmatic operators and software craftspeople that apply
sound engineering principles, operational discipline, and mature automation to
our operating environments and the GitLab codebase.

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
SaaS sites on the internet developed and run with transparency in mind.
GitLab.com runs using the same tools we provide to GitLab customers running
self-managed installations. The experience of our team feeds back into other
engineering groups within the company, as well as self-managed customers.

SRE's with Scalability specialization focus on how to scale both the
application and the infrastructure supporting the application. This is the
main difference between a Scalability SRE and other SRE’s at GitLab, is that
your day to day will be spent looking at how to enable other engineers at
GitLab to incorporate availability, reliability and performance considerations
into their daily work. We do this by providing access to information and
systems in a safe and sustainable way. We do this for our application and aim
to extend this offering to our infrastructure and services. .

**Some examples of projects you could work:**

  * Working from the Scalability team’s[ issue tracker](https://gitlab.com/gitlab-com/gl-infra/scalability), driving changes required to [ scale GitLab at GitLab.com size.](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/148)
  * [Architectural Blueprints](https://about.gitlab.com/handbook/engineering/architecture/workflow/) used to define how the component fits into a bigger picture
  * [Developer Documentation and Guidelines](https://docs.gitlab.com/) used to ensure consistency between multiple components
  * Self-service deployment and management tools, used to ensure simpler maintenance of the component
  * [Service Maturity Model](https://about.gitlab.com/handbook/engineering/infrastructure/service-maturity-model/), ensuring that the component has consistent interfaces necessary to operate a robust and reliable component
    * Observability and Forecasting Tools
    * Logging and Alerting Guidelines
    * [Operational Runbooks](https://gitlab.com/gitlab-com/runbooks/)

**What you'll do**

  * Be on a PagerDuty rotation to respond to GitLab.com availability incidents and provide support for service engineers with customer incidents.
  * Analyze existing, create and maintain new GitLab.com[ Service Level Objectives](https://en.wikipedia.org/wiki/Service-level_objective).
  * Troubleshoot, evaluate and resolve operational challenges contributing to defined SLO's.
  * Define, improve, and engage in adapting architectural application bottlenecks as observed on GitLab.com.
  * Work with other engineering stakeholders on resolving larger architectural bottlenecks and participate by offering GitLab.com point of view.
  * Work in close collaboration with software development teams to shape the future roadmap and establish strong operational readiness across teams.
  * Scale systems through automation, improving change velocity and reliability.
  * Leverage technical skills to partner with team members and be comfortable diving into a problem as needed.
  * Work with counterparts in other teams of the Infrastructure department to improve infrastructure running with Chef, Terraform and Kubernetes.
  * Make monitoring and alerting alert on symptoms and not on outages.
  * [Document every action](https://gitlab.com/gitlab-com/runbooks) so your findings turn into repeatable actions–and then into automation.
  * Debug production issues across services and levels of the stack.



**What you'll bring**

  * Strong programming skills - Preferably with Ruby and/or Go.
  * Production experience with the Kubernetes ecosystem
  * SRE experience in running and operating distributed systems is a bonus
  * Are able to reason about large systems - how they work on large scale, edge cases, failure modes, behaviors.
  * Know your way around Linux and the Unix Shell.
  * Have experience in collaborating and communicating asynchronously.
  * Have an urge to document all the things so you don't need to learn the same thing twice.
  * Have an enthusiastic, go-for-it attitude. When you see something broken, you can't help but fix it.
  * Have a strong sense for action and know how to iterate through a problem quickly.
  * Share our values, and work in accordance with those values.
  * Have experience with Nginx, HAProxy, Docker, Terraform, or similar technologies.
  * A solid understanding of, and experience with, implementing and working  with SLI/SLO 
  * Are able to leverage GitLab as your day-to-day go-to tool.

**  
About the team**

The Practices team focuses on tools and frameworks that enable the stage
groups to support their features on our production systems. These challenges
exist in high-load, critical services without dedicated owners, shared
architectures, and complex operational configurations. The expertise within
the Practices team helps overcome these challenges by responding to technical
needs, promoting uniform processes, and increasing engineering efficiency by
eliminating toil.

#### **How GitLab will support you**

  * [Benefits to support your health, finances, and well-being](https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/)
  * [All remote](https://about.gitlab.com/company/culture/all-remote/guide/), [asynchronous](https://about.gitlab.com/company/culture/all-remote/asynchronous/) work environment
  * [Flexible Paid Time Off](https://about.gitlab.com/handbook/paid-time-off/)
  * [Team Member Resource Groups](https://about.gitlab.com/company/culture/inclusion/erg-guide/#:~:text=Definition%20of%20the%20TMRG%20%2D%20Team%20Member%20Resource%20Groups,-TMRGs%20are%20voluntary&text=The%20purpose%20for%20this%20type,developing%20the%20sense%20of%20belonging.)
  * [Equity Compensation & Employee Stock Purchase Plan](https://about.gitlab.com/handbook/stock-options/)
  * [Growth and development budget ](https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#growth-and-development-benefit)
  * [Parental leave](https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave) 
  * [Home office](https://about.gitlab.com/handbook/finance/procurement/office-equipment-supplies/) support

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](https://about.gitlab.com/company/culture/inclusion/#examples-of-
select-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.

 _The base salary range for this role’s listed level is currently for
residents of listed locations only. 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,
and alignment with market data. See more information on
our[benefits](https://about.gitlab.com/handbook/total-
rewards/benefits/general-and-entity-benefits/) and
[equity](https://about.gitlab.com/handbook/stock-options/). Sales roles are
also eligible for incentive pay targeted at up to 100% of the offered base
salary._

Colorado/Washington pay range

$124,300--$239,700 USD

California/New York/New Jersey pay range

$124,300--$266,400 USD

* * *

**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.](https://about.gitlab.com/handbook/hiring/candidate/faq/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](https://about.gitlab.com/handbook/people-policies/inc-usa/#equal-
employment-opportunity-policy) and [EEO is the
Law](https://about.gitlab.com/handbook/labor-and-employment-notices/#eeoc-us-
equal-employment-opportunity-commission-notices). If you have a disability or
special need that requires
[accommodation](https://about.gitlab.com/handbook/people-policies/inc-
usa/#reasonable-accommodation), please let us know during the [recruiting
process](https://about.gitlab.com/handbook/hiring/interviewing/#adjustments-
to-our-interview-process).

