<div class="content-intro">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>.</div><h4>An overview of this role</h4>
As a Distribution Engineer, your work within the<a href="https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#distribution-deploy"> Distribution: Deploy team</a> surrounds configuration, deployment, and operation of GitLab as a whole product. The goal is to deliver an intuitive, clear, and frictionless installation experience, followed by smooth, seamless upgrade and maintenance processes for deployments of any scale.<a href="https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#distribution-deploy-team"> We</a> strive to deliver ongoing operational behaviors for scaling, little to zero downtime upgrades, and highly reliable experiences for not only instance administrators but their users. Omnibus packages, Helm Charts and Operators are primary deployment methods Distribution currently supports.
As a Distribution Engineer on the Distribution: Deploy team you regularly interface with broader development teams in supporting newly created features.
Some interesting links about the team and role
<ul>
<li>Our<a href="https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#primary-projects"> primary projects</a></li>
<li>Our work with the<a href="https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#working-with-the-community"> community</a></li>
<li>Our<a href="https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/demo.html"> Demo video’s</a></li>
</ul>
What you’ll do&nbsp;&nbsp;
<ul>
<li>Build and maintain tools for initial installation and composability for self-managed installations and GitLab.com</li>
<li>Productize Upgrades / Downgrades from a single node installation to large scale enterprise installation</li>
<li>Secure configuration &amp; communication</li>
<li>Research and document cloud and platform migration and integration</li>
<li>Investigate and analyze installation and upgrade incidents, identify root cause, and develop appropriate mitigation strategies and fixes</li>
</ul>
What you’ll bring&nbsp;
<ul>
<li>Production experience designing, building, and packaging cloud-native applications.</li>
<li>Experience with the Kubernetes ecosystem (Operators, Helm, registries, etc.).</li>
<li>Experience with shipping production ready code in Golang</li>
<li>Experience with oher high-level programming languages such as as Bash, Shell, Ruby or Python</li>
<li>Production experience with IaC and orchestration tooling at scale (Ansible, Terraform, Chef, etc.).</li>
<li>Knowledge of service scaling and rollout strategies.</li>
<li>Proficiency in the English language, both written and verbal, sufficient for success in a remote and largely asynchronous work environment.</li>
<li>User of modern DevOps platforms. (GitLab is a bonus.)</li>
<li>Production experience with building container images and container build tooling. (Desired)</li>
</ul>
About the team
The Distribution team is composed of two subgroups: Distribution:Build and Distribution:Deploy.&nbsp;
The Build team is focused on producing artifacts including system packages, container images, and related components like marketplace listings along with tooling required to create and maintain them. The Deploy team is focused on installation and upgrade mechanisms to ensure smooth deployments. This includes system integration, scripting, templating, and related configuration management tooling.&nbsp;
In addition to product deliverables, both groups review a large number of MR's authored outside the team. These include dependency and security updates along with configuration controls and other bundled components like PostgreSQL, Consul, Patroni. Deployments include everything from single node deployments for evaluating GitLab all the way through the 50K user reference architecture and beyond. The primary goal is to ensure end users have a high-speed, low-friction experience when managing GitLab with limited downtime or service disruptions.
<h4>How GitLab will support you</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>
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.<div class="content-conclusion"><hr>
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.&nbsp;&nbsp;
Privacy Policy: 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.
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>.</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).

####  **An overview of this role**

As a Distribution Engineer, your work within the[ Distribution: Deploy
team](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#distribution-
deploy) surrounds configuration, deployment, and operation of GitLab as a
whole product. The goal is to deliver an intuitive, clear, and frictionless
installation experience, followed by smooth, seamless upgrade and maintenance
processes for deployments of any scale.[
We](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#distribution-
deploy-team) strive to deliver ongoing operational behaviors for scaling,
little to zero downtime upgrades, and highly reliable experiences for not only
instance administrators but their users. Omnibus packages, Helm Charts and
Operators are primary deployment methods Distribution currently supports.

As a Distribution Engineer on the Distribution: Deploy team you regularly
interface with broader development teams in supporting newly created features.

Some interesting links about the team and role

  * Our[ primary projects](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#primary-projects)
  * Our work with the[ community](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#working-with-the-community)
  * Our[ Demo video’s](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/demo.html)

**What you’ll do**  

  * Build and maintain tools for initial installation and composability for self-managed installations and GitLab.com
  * Productize Upgrades / Downgrades from a single node installation to large scale enterprise installation
  * Secure configuration & communication
  * Research and document cloud and platform migration and integration
  * Investigate and analyze installation and upgrade incidents, identify root cause, and develop appropriate mitigation strategies and fixes

**What you’ll bring  **

  * Production experience designing, building, and packaging cloud-native applications.
  * Experience with the Kubernetes ecosystem (Operators, Helm, registries, etc.).
  * Experience with shipping production ready code in Golang
  * Experience with oher high-level programming languages such as as Bash, Shell, Ruby or Python
  * Production experience with IaC and orchestration tooling at scale (Ansible, Terraform, Chef, etc.).
  * Knowledge of service scaling and rollout strategies.
  * Proficiency in the English language, both written and verbal, sufficient for success in a remote and largely asynchronous work environment.
  * User of modern DevOps platforms. (GitLab is a bonus.)
  * Production experience with building container images and container build tooling. (Desired)

**About the team**

The Distribution team is composed of two subgroups: Distribution:Build and
Distribution:Deploy.

The Build team is focused on producing artifacts including system packages,
container images, and related components like marketplace listings along with
tooling required to create and maintain them. The Deploy team is focused on
installation and upgrade mechanisms to ensure smooth deployments. This
includes system integration, scripting, templating, and related configuration
management tooling.

In addition to product deliverables, both groups review a large number of MR's
authored outside the team. These include dependency and security updates along
with configuration controls and other bundled components like PostgreSQL,
Consul, Patroni. Deployments include everything from single node deployments
for evaluating GitLab all the way through the 50K user reference architecture
and beyond. The primary goal is to ensure end users have a high-speed, low-
friction experience when managing GitLab with limited downtime or service
disruptions.

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

* * *

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

