Cloud & Infrastructure
FinOps Lead
Role Summary
Drives cloud cost discipline and unit-economics programs. Work spans tag governance, commitment-ladder design, right-sizing programs, and the operating model that sustains cost gains beyond a one-time consulting engagement.
Equally comfortable in finance and engineering rooms. Refuses cost-recovery work that depends on indefinite consultant presence to hold the gains; insists on building the client operating model that keeps spend in check after the engagement closes. Treats unit cost as a product metric, not a finance KPI.
Skills
- FinOps Foundation framework and operating-model design
- Cloud cost analytics across AWS, Azure, and GCP
- Cost-management tooling (CloudHealth, Apptio Cloudability, Vantage, native cloud)
- Commitment-ladder design (RIs, savings plans, committed-use discounts)
- Spot and preemptible capacity strategy for batch and stateless workloads
- Tag governance program design and enforcement
- Showback and chargeback model design
- Unit-cost and product-cost economics modeling
- Right-sizing methodology with risk-adjusted recommendations
- Storage tiering and lifecycle policy design (S3 Intelligent-Tiering, Blob lifecycle)
- Network cost optimization (NAT gateway audits, VPC endpoints, inter-AZ traffic)
- Database right-sizing including read-replica strategy
- Reserved capacity and savings-plan portfolio management
- Cloud bill anomaly detection and root-cause analysis
- Pre-renewal hyperscaler negotiation support
- Finance and engineering stakeholder facilitation
- KPI design tied to business outcomes
- Sustainability and carbon-cost-aware architecture
Capabilities & Focus Areas
- Cloud cost diagnostic engagements producing prioritized recovery roadmaps
- Tag governance program design and rollout
- Commitment ladder design (RIs, savings plans, committed-use discounts)
- Right-sizing and waste-removal programs
- Unit-cost metrics tied to product or business outcomes
- FinOps operating model and capability building
- Pre-renewal commitment optimization
Typical Engagement Patterns
- Thirty/sixty/ninety day cloud cost recovery engagements with documented savings
- FinOps operating-model design and standup (eight to sixteen weeks)
- Pre-renewal commitment-ladder optimization (four to six weeks)
- Unit-economics design engagements for SaaS and product organizations
- Embedded FinOps lead for clients consolidating multi-business-unit cloud spend
Outcomes Delivered
- Cloud spend reductions of 20 to 40 percent within ninety days, documented at the line-item level
- Tag coverage above 90 percent across compute, storage, and managed services
- Commitment posture aligned to actual workload patterns, not vendor-suggested defaults
- Unit-cost metrics that engineering, product, and finance all recognize
- FinOps operating models that hold the gains for at least four quarters post-engagement
Need this role for an engagement?
Brief us on the scope and timeline and we'll match a senior practitioner.