Site Reliability Engineer, US Public Sector Services at GitLab Remote 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 Engineer, US Public Sector Services The GitLab DevOps 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 1,600 team members and values (https://about.gitlab.com/handbook/values/) that guide a culture where people embrace the belief that everyone can contribute.

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.

SRE's with Public Sector specialization focus primarily on operating a large number of GitLab environments that are built to meet US Government, State, and third-party entity requirements. 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.