GitLab
Intermediate Site Reliability Engineer, Cloud Cost Utilization
Remote Site Reliability Engineer role with clear candidate location fit.
PostedJul 27, 2026
Eligible countries1 accepted country
Seniority signalMiddle
Work settingRemote
Accepted candidate locations
USA
Role overview
Intermediate Site Reliability Engineer, Cloud Cost Utilization
Requirements and responsibilities
Readable role content extracted into sections for faster review.
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, 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
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
Similar roles
Keep a backup shortlist.
Stack
Use these tags to compare similar remote roles.
Location eligibility
Candidates should apply only when their profile country is listed here.
Your profileCountry not setSign in to check your country against this role.
Hiring flow
WithMira shows the role, then sends candidates to the company application.
1Check role fit, stack, and location eligibility in WithMira.
2Open the company application page from the tracked apply link.
3Save the role or subscribe for similar opportunities before leaving.