Site Reliability Engineer, Cloud Cost Utilization

GitLab is the intelligent orchestration platform for DevSecOps, enabling organizations to improve operational efficiency and accelerate digital transformation. As a Cloud Cost Utilization SRE, you will enhance visibility and accountability of cloud spending, partnering with cross-functional teams to optimize cloud usage and develop effective cost management strategies.

Responsibilities:

• 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, with a focus 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

Requirements:

• 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