Skip to content

Cloud & Cost 90 days 2-3 hours/day updated 2026-06-01

FinOps 90-Day Learning Path

Master FinOps in 90 days — FOCUS spec, unit economics, showback/chargeback, reserved instances vs spot, and cloud cost governance. Make every cloud dollar accountable.

What FinOps means

FinOps (Financial Operations) is the practice of bringing financial accountability to cloud spending by fostering collaboration between engineering, finance, and business teams. FinOps practitioners implement cost visibility, showback and chargeback models, and unit economics to help organizations understand and optimize the business value of their cloud investments. The FinOps Foundation defines the framework and the FOCUS spec standardizes cost and usage data.

Who should follow this path

  • Cloud engineers owning cost optimization
  • Engineering managers accountable for cloud budgets
  • Finance and business partners working with engineering
  • Platform engineers building cost governance tooling

Prerequisites

  • Experience with cloud infrastructure (AWS, GCP, or Azure)
  • Basic understanding of cloud billing and pricing models
  • Familiarity with tagging and resource organization
  • Business communication skills for cross-functional work

The 90-day plan

Daily study recommendation: 2-3 hours/day, six days a week. Consistency beats intensity — block the time in your calendar like a meeting.

Days 1–15: Foundation

  • FinOps Foundation framework and maturity model (Crawl, Walk, Run)
  • FinOps lifecycle: Inform, Optimize, Operate
  • FOCUS spec: FinOps Open Cost and Usage Specification
  • Cloud pricing models: on-demand, reserved, savings plans, spot
  • Cloud billing anatomy: accounts, services, and tags

Outcome: Map your organization to the FinOps maturity model and identify the Inform phase gaps.

Days 16–30: Core concepts

  • Cost allocation tags and resource hierarchies
  • Showback reporting design
  • Chargeback implementation patterns
  • AWS Cost Explorer and Cost and Usage Reports
  • GCP Billing and BigQuery export analysis

Outcome: Implement showback reporting that allocates cloud spend to teams and products accurately.

Days 31–45: Tools and workflows

  • Reserved instance and savings plan analysis
  • Spot instance strategy and interruption handling
  • Compute right-sizing methodologies
  • Storage lifecycle policies and tier optimization
  • Idle and underutilized resource detection

Outcome: Identify and implement reserved instance purchases reducing compute costs by 30 percent.

Days 46–60: Hands-on projects

  • Unit economics: cost per transaction, customer, and feature
  • FinOps dashboards with Grafana and Looker
  • Anomaly detection for cost spikes
  • Budget alerts and threshold notifications
  • Engineering KPIs tied to cloud efficiency

Outcome: Build unit economics dashboards that express cloud cost as a business metric.

Days 61–75: Advanced practices

  • FinOps culture: engineering and finance collaboration models
  • FinOps tooling: CloudHealth, Apptio Cloudability, Infracost
  • Kubernetes cost allocation with Kubecost
  • Multi-cloud cost management
  • Cloud cost as code with Infracost in CI/CD

Outcome: Integrate Infracost into CI/CD to surface cost impact of infrastructure changes pre-merge.

Days 76–90: Portfolio, interview & certification prep

  • Portfolio: FinOps implementation case study with measurable savings
  • FinOps Certified Practitioner exam preparation
  • FinOps interview question preparation
  • Building a FinOps center of excellence charter
  • Presenting cloud cost business case to leadership

Outcome: Pass FinOps Certified Practitioner prep and present a documented FinOps transformation.

Weekly outcomes at a glance

PhaseOutcome
Days 1–15Map your organization to the FinOps maturity model and identify the Inform phase gaps.
Days 16–30Implement showback reporting that allocates cloud spend to teams and products accurately.
Days 31–45Identify and implement reserved instance purchases reducing compute costs by 30 percent.
Days 46–60Build unit economics dashboards that express cloud cost as a business metric.
Days 61–75Integrate Infracost into CI/CD to surface cost impact of infrastructure changes pre-merge.
Days 76–90Pass FinOps Certified Practitioner prep and present a documented FinOps transformation.

Tools to learn

  • AWS Cost Explorer
  • GCP Billing
  • Azure Cost Management
  • Infracost
  • Kubecost
  • CloudHealth
  • Apptio Cloudability
  • Grafana
  • Looker
  • AWS Budgets

Labs to practice

Mini projects

  • Build a showback/chargeback system for a 10-team engineering organization
  • Implement Infracost in a Terraform CI/CD pipeline with PR cost comments
  • Create a Kubecost dashboard for per-namespace Kubernetes cost allocation

Interview questions to prepare

  1. What is the FinOps Foundation framework and its three lifecycle phases?
  2. Explain the difference between showback and chargeback.
  3. What is the FOCUS specification and why does it matter?
  4. How do reserved instances differ from savings plans and when do you use each?
  5. What is unit economics in the context of cloud spending?
  6. How would you build a cost anomaly detection system?
  7. Describe how you would embed FinOps practices into an engineering team’s workflow.
  8. How does Kubecost enable Kubernetes namespace cost allocation?

Certification suggestions

  • FinOps Certified Practitioner (FOCP) — FinOps Foundation
  • AWS Certified Cloud Practitioner — AWS
  • Google Cloud Digital Leader — Google Cloud
  • AWS Certified Solutions Architect – Associate — AWS

Browse the full certification registry for exam details and official links.

Free resources

// instructor-led option

Prefer live, guided training with mentors and certification support? DevOpsSchool.com runs paid instructor-led programs that pair well with this free path.

Explore paid training on DevOpsSchool.com ↗