<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>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.</p>
<p>The<a href="https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/observability.html"> Observability Team</a>'s mission is to Build, Run and Own the entire lifecycle of the suite of services that enable observability of the GitLab SaaS environments. These services allow Infrastructure, Development and Product teams to observe how their code runs on GitLab’s SaaS Platforms and contribute to our overall reliability and scalability goals. This also extends from metrics gathering and telemetry to how that information is used by the Infrastructure and Development teams.&nbsp;</p>
<h4><strong>As an SRE you will:</strong></h4>
<ul>
<li>Build: Automating as much as possible. Tasks should not be manual. Our Observability stack needs to be extended to support our growth and we need engineers to focus on how to build sustainably.&nbsp;</li>
<li>Maintain: Our metrics environment as well as the tools and processes we have developed to provide this information throughout the company.&nbsp;&nbsp;</li>
<li>Plan: Develop monitoring and alerting systems that predict capacity needs based on the customer usage patterns. Plan for new service rollouts, expansion of existing services and preparing advice for customers to optimize their resource consumption.&nbsp;&nbsp;</li>
<li>Respond: There is a requirement to be part of an on-call rota in this role.</li>
<li>Partner: Act as Subject Matter Experts for metrics gathering, observability guidelines, and capacity planning.&nbsp;</li>
<li>Collaborate: Work with other engineering stakeholders on resolving larger architectural bottlenecks and participate by offering a large scale operational point of view. Work in close collaboration with software development teams.</li>
</ul>
<h4><strong>You may be a fit to this role if you:</strong></h4>
<ul>
<li>Have experience with Infrastructure as a Code technologies, and libraries powering GitLab.</li>
<li>Have experience with Grafana’s LGTM stack, or Elastic’s stack (ELK)</li>
<li>Are able to reason about large systems - how they work and can be operated on a large scale, edge cases, failure modes, behaviors.</li>
<li>Enjoy working with peers and collaborating across teams to deliver unique solutions to various technical challenges.&nbsp;</li>
<li>Are able to leverage GitLab as your day-to-day go-to tool.</li>
</ul>
<p>&nbsp;You share our<a href="https://about.gitlab.com/handbook/values/"> values</a>, and work in accordance with those values.</p>
<h4><strong>Projects you could work on:</strong></h4>
<ul>
<li>Work on the GitLab core projects such as, GitLab Rails, GitLab Workhorse, Gitaly, etc.</li>
<li>Coding infrastructure automation with Ansible and Terraform, and comfortable with managed Kubernetes platforms.</li>
<li>Work on the GitLab observability stack (e.g. ELK, Prometheus, Grafana).</li>
<li>Interact with various cloud provider systems (e.g. GCP, AWS).</li>
<li><a href="https://handbook.gitlab.com/handbook/engineering/error-budgets/">Error Budgets for Engineering at GitLab</a>.</li>
<li>Capacity Planning with <a href="https://gitlab.com/gitlab-com/gl-infra/tamland">Tamland</a>.</li>
</ul>
<p>&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>All remote,<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>
<p>#LI-BC2</p><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).

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.

The[ Observability
Team](https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/observability.html)'s
mission is to Build, Run and Own the entire lifecycle of the suite of services
that enable observability of the GitLab SaaS environments. These services
allow Infrastructure, Development and Product teams to observe how their code
runs on GitLab’s SaaS Platforms and contribute to our overall reliability and
scalability goals. This also extends from metrics gathering and telemetry to
how that information is used by the Infrastructure and Development teams.

#### **As an SRE you will:**

  * Build: Automating as much as possible. Tasks should not be manual. Our Observability stack needs to be extended to support our growth and we need engineers to focus on how to build sustainably. 
  * Maintain: Our metrics environment as well as the tools and processes we have developed to provide this information throughout the company.  
  * Plan: Develop monitoring and alerting systems that predict capacity needs based on the customer usage patterns. Plan for new service rollouts, expansion of existing services and preparing advice for customers to optimize their resource consumption.  
  * Respond: There is a requirement to be part of an on-call rota in this role.
  * Partner: Act as Subject Matter Experts for metrics gathering, observability guidelines, and capacity planning. 
  * Collaborate: Work with other engineering stakeholders on resolving larger architectural bottlenecks and participate by offering a large scale operational point of view. Work in close collaboration with software development teams.

#### **You may be a fit to this role if you:**

  * Have experience with Infrastructure as a Code technologies, and libraries powering GitLab.
  * Have experience with Grafana’s LGTM stack, or Elastic’s stack (ELK)
  * Are able to reason about large systems - how they work and can be operated on a large scale, edge cases, failure modes, behaviors.
  * Enjoy working with peers and collaborating across teams to deliver unique solutions to various technical challenges. 
  * Are able to leverage GitLab as your day-to-day go-to tool.

 You share our[ values](https://about.gitlab.com/handbook/values/), and work
in accordance with those values.

#### **Projects you could work on:**

  * Work on the GitLab core projects such as, GitLab Rails, GitLab Workhorse, Gitaly, etc.
  * Coding infrastructure automation with Ansible and Terraform, and comfortable with managed Kubernetes platforms.
  * Work on the GitLab observability stack (e.g. ELK, Prometheus, Grafana).
  * Interact with various cloud provider systems (e.g. GCP, AWS).
  * [Error Budgets for Engineering at GitLab](https://handbook.gitlab.com/handbook/engineering/error-budgets/).
  * Capacity Planning with [Tamland](https://gitlab.com/gitlab-com/gl-infra/tamland).



#### **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,[ 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.

#LI-BC2

* * *

**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).

