Intermediate Site Reliability Engineer, Environment Automation

Intermediate Site Reliability Engineer, Environment Automation

Remote, EMEA

GitLab is an open core software company that develops the most comprehensive AI-powered DevSecOps Platform, used by more than 100,000 organizations. Our mission is to enable everyone to contribute to and co-create the software that powers our world. When everyone can contribute, consumers become contributors, significantly accelerating the rate of human progress. This mission is integral to our culture, influencing how we hire, build products, and lead our industry. We make this possible at GitLab by running our operations on our product and staying aligned with our values.

An overview of this role

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.

As an SRE within the Environment Automation specialization, you primarily focus on operating a large number of GitLab environments, through automating all workflows - from provisioning new environments to daily operating tasks. This is the main difference between Environment Automation SRE and other SREs at GitLab; your day to day will be occupied by automation tasks of a large number of GitLab environments (and the environments used by GitLab), and operational tasks across many environments.

Some examples of the projects you could work on:

• The automation used to operate a large number of GitLab environments.
• Creating deployment packages of GitLab such as GitLab Helm Chart, omnibus-gitlab, etc.
• Building Dedicated GitLab setups using infrastructure as code automation with Ansible and Terraform and integrate with Cloud Native services from cloud providers (e.g., GCP, AWS).
• Building tools to orchestrate infrastructure as code workloads.
• Deploy and operate microservices on top of Kubernetes.
• Working on the GitLab observability stack (e.g., ELK, Prometheus).
• Interact with various cloud provider systems (e.g., GCP, AWS).
• Developing, evangelizing, and monitoring the adoption of sound cloud security practices.

What you’ll do

• Build: Automate every operational task is a core requirement for Environment Automation SRE. E.g., package updates, configuration changes across all customer platforms without interruptions, tools for automatic provisioning of customer-facing services, etc.
• Maintain: Develop a good (early) warning system and system that allows for reliable and quick maintenance tasks, such as library upgrades, version migrations and similar.
• 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: Respond to user emergencies, platform alerts and support requests.
• Enhance: Implement new, and update existing security measures for the protection of GitLab infrastructure.
• 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 to shape the future roadmap and establish strong operational readiness across teams.

What you’ll bring

• Have experience in running and operating production workloads.
• Have strong programming skills - preferably with Ruby and/or Go.
• Have a strong background with Infrastructure as Code technologies, and libraries powering GitLab, such as Terraform, Ansible. Experience with data templating tools such as Jsonnet would be considered a bonus.
• 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.
• Have experience regularly interacting with customers, and a focus on resolving their requests with a sense of urgency.

About the team

GitLab’s Dedicated team in which the SRE Environment Automation sits has the mission to create a fully managed, single-tenant GitLab environment, served through a GitLab Dedicated platform. It is developed to remove any manual interactions with customer tenant installations, and to ensure that the customer tenants are fully focused on unlocking the power of The One DevOps Platform.

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.

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.

Apply for this job

* indicates a required field

First Name *

Last Name *

Email *

Phone

Location (City) *

Resume/CV

Enter manually

Accepted file types: pdf, doc, docx, txt, rtf

LinkedIn Profile

What's the name you'd prefer us to use throughout the interview process?

Please choose the country in which you will be located if hired by GitLab. * Select...

Were you referred by a current GitLab team member? If so, please write their name below.

Are you subject to any employment agreements and/or post-employment restrictions with your current employer or a past employer? * Select...

Have you developed a tool or application using a programming language (excluding Infrastructure-as-Code languages)? To clarify: We're interested in experience building software applications or programs, rather than writing automation scripts or configuration files. * Select...

If yes, please describe briefly. If you answered no, please put N/A. *

Do you have professional experience using the Terraform CLI and creating Terraform modules for Infrastructure-as-Code (IaC) automation? * Select...

How frequently have you used kubectl/Helm/Kustomize/ArgoCD/or similar to manage Kubernetes clusters in your professional experience over the past two years? * Select...

It is important to us to create an accessible and inclusive interview experience. Please let us know if there are any adjustments we can make to assist you during the hiring and interview process.

Will you now or in the future require sponsorship for a visa to remain in your current location? * Select...