Intermediate Site Reliability Engineer, Cloud Cost Utilization

As a Cloud Cost Utilization SRE at GitLab, you will make cloud spending visible, understandable, and actionable across our infrastructure. This role sits at the intersection of engineering and financial accountability, partnering with Engineering, Finance, and Product to improve how cloud usage is tracked, attributed, and optimized across GitLab.

You will build and improve the systems, standards, and workflows that help teams understand the real cost of the services they run. This includes developing resource tagging and labeling approaches, improving billing data quality, and creating tooling that supports better decisions across AWS and GCP.

In this role, you will work through technical and organizational ambiguity, connect infrastructure data with business context, and help teams act on cost signals with confidence. It is a strong fit for someone who enjoys systems thinking, cross‑functional collaboration, and building practical solutions in GitLab’s all‑remote, asynchronous, and values‑driven environment.

Some examples of our projects

• Building cloud billing data pipelines that normalize multi‑cloud cost data using the FinOps Open Cost and Usage Specification (FOCUS)
• Improving cloud resource tagging and labeling standards so teams can understand spend by service, environment, and ownership
• Developing cost anomaly detection, forecasting, and alerting workflows that give teams timely insight into infrastructure usage
• Extending observability systems so cost signals can be reviewed alongside reliability and operational data

What you’ll do

• Design and maintain cloud resource tagging and labeling strategies across GCP and AWS to support accurate cost attribution
• Develop tooling and pipelines to ingest, normalize, and report on cloud billing data using the FOCUS specification
• Automate cost anomaly detection, forecasting, and alerting so engineering teams can respond quickly to changes in infrastructure spend
• Contribute to GitLab’s observability and monitoring stacks, including Prometheus, LGTM (Loki, Grafana, Tempo, and Mimir), and ELK, focusing on surfacing cost efficiency signals
• Partner with Finance and Engineering leadership to support cloud cost forecasting for planning and budget discussions
• Act as a subject matter expert for cloud cost attribution, tagging strategy, and FOCUS adoption across GitLab Infrastructure
• Collaborate with Finance and Compliance teams on audits, certifications, and financial reporting needs related to cloud infrastructure usage
• Contribute to infrastructure‑as‑code efforts, including Terraform and Ansible, so cost controls and tagging requirements are built into provisioning workflows from the start

What you’ll bring

• Hands‑on experience with cloud cost management in GCP and/or AWS, including billing data, pricing models, and optimization approaches
• Familiarity with, or interest in adopting, the FinOps FOCUS specification for multi‑cloud cost analysis
• Experience designing or implementing cloud resource tagging and labeling strategies and improving adoption across teams
• Comfort working across technical and business functions, including Engineering, Finance, and other stakeholders
• Experience with infrastructure as code, including Terraform and Ansible
• Familiarity with observability tooling, including Grafana, and an understanding of how reliability and cost signals can be connected
• Ability to explain technical cost data clearly to non‑engineering audiences and support informed decision‑making
• A self‑directed approach to work, with comfort operating in a fully remote and asynchronous environment

How GitLab Supports Full-Time Employees

• Benefits to support your health, finances, and well‑being
• Flexible Paid Time Off
• Team Member Resource Groups
• Equity Compensation & Employee Stock Purchase Plan
• Growth and Development Fund
• Parental leave
• Home office support

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

Privacy Policy: Please review our 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 and EEO is the Law. If you have a disability or special need that requires accommodation, please let us know during the recruiting process.