GitLab
Mid
Site Reliability Engineer, Cloud Cost Utilization at GitLab
A FinOps-adjacent SRE role at GitLab making multi-cloud spend visible and actionable across AWS and GCP, sitting between Engineering, Finance, and Product. Interviews test hands-on cloud billing/cost-attribution experience, tagging strategy design, infrastructure-as-code fluency, and the ability to explain cost data to non-engineering stakeholders in a fully remote, async environment.
Step into this interview
Free · a live voice mock calibrated to this exact role
What this interview tests
- Cloud cost attribution and resource tagging/labeling strategy
- Multi-cloud billing data pipelines and the FinOps FOCUS specification
- Cost anomaly detection and forecasting workflows
- Infrastructure as code (Terraform, Ansible) for cost controls
- Cross-functional communication with Finance and non-engineering stakeholders
Common question themes
How would you design a tagging strategy so teams can attribute cloud spend by service and owner
Walk through normalizing AWS and GCP billing data into a single cost model
Building a cost anomaly detection or forecasting alert — what signals would you use
How you'd explain a spend spike to a Finance stakeholder with no infra background
Baking cost controls into Terraform/Ansible provisioning workflows
Related interviews
GitLab
Senior
Senior Solutions Architect, MEA
GitLab
Senior
Senior Solutions Architect - Northeast
GitLab
Senior
Engineering Manager, Data Foundations
Dropbox
Mid
Site Reliability Engineer
Netflix
Senior
Systems Development Engineer 5 - Creative Compute and Storage
Cohere
Mid