Senior Site Reliability Engineer, Environment Automation

Senior Site Reliability Engineer, Environment Automation Remote, Canada 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. 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. As an SRE you will: Build: Automating 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. Partner: Act as Subject Matter Experts within the GitLab Infrastructure team when interacting with internal and external compliance assessors during certification and recertification of regulatory requirements (ex. FedRAMP, SOC2, ISO). 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. You may be a fit for this role if you: Have experience with Infrastructure as a Code technologies, and libraries powering GitLab. Are able to reason about large systems - how they work and can be operated on a large scale, edge cases, failure modes, behaviors. Are comfortable using GoLang or Ruby. 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. You share our values and work in accordance with those values. Projects you could work on: Develop, evangelize, and monitor the adoption of solid cloud security practices. Working from the team’s issue tracker, driving changes required to operate a large number of GitLab environments. Work on the GitLab core projects such as GitLab Rails, GitLab Runners, GitLab Workhorse, Gitaly, etc. Work on projects that create deployment packages of GitLab such as GitLab Helm Chart, omnibus-gitlab, etc. Coding infrastructure automation with Ansible and Terraform, and comfortable with managed Kubernetes platforms. Work on the GitLab observability stack (e.g. ELK, Prometheus). Interact with various cloud provider systems (e.g. GCP, AWS). 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 * LinkedIn Profile What name would you prefer us to use throughout the interview process? Are you subject to any employment agreements and/or post-employment restrictions with your current employer or a past employer? * 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. 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... Provide an example, or enter N/A if you do not have this experience. * 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... Please choose the country in which you will be located if hired by GitLab. * Select... Will you now or in the future require sponsorship for a visa to remain in your current location? * Select... #J-18808-Ljbffr