FinOps Maturity Model - Crawl Walk Run

A cloud bill that doubles every quarter is one of the most common opening lines in a FinOps interview. The interviewer isn't just checking if you know the jargon. They want to know if you understand why cost control usually fails as an organizational problem, not a tooling problem.

The answer interviewers want

The FinOps maturity model has three stages: Crawl, Walk, and Run.

Crawl is reactive firefighting. There's no real process yet, just basic dashboards that show spend after the fact. Teams find out about a cost spike because someone noticed the invoice, not because anything caught it early.

Walk is where process gets built. This stage implements budgets and alerts, so teams get warned before a number gets out of hand instead of after. There's some ownership of spend, some reporting cadence, some accountability starting to form.

Run is where automation takes over. This stage has ML-driven rightsizing, meaning the system is actively adjusting resource allocation based on usage patterns instead of a human manually resizing instances after a quarterly review.

The detail that actually matters in an interview: most organizations get stuck in Walk. They have the dashboards, they have budgets and alerts configured, but they never get to Run. The reason isn't technical. They skip the cultural change. Alerts firing into a channel nobody acts on isn't FinOps maturity, it's just a louder version of Crawl. Getting to Run requires engineering teams to actually own their cost numbers the way they own uptime or latency, and that's an organizational shift, not a dashboard you buy.

Why interviewers ask this

This question separates people who've memorized a framework from people who've seen it fail in practice. Anyone can recite Crawl, Walk, Run. The interviewer is really listening for whether you understand that tooling alone doesn't move an org between stages, and whether you can name the actual blocker: culture and ownership, not missing dashboards.

Follow-ups to expect

"Why do most orgs stall in Walk instead of reaching Run?" Because they treat FinOps as a reporting function instead of an engineering responsibility. The budgets and alerts exist, but no one's job depends on acting on them.

"What's the difference between a Walk-stage alert and a Run-stage response?" In Walk, an alert tells a human something looks wrong. In Run, the system is already adjusting resources through automated rightsizing before a human needs to look at it.

"How would you move a team from Walk to Run?" Start by making cost a shared metric engineering teams are accountable for, not just something finance reports on, then layer automation on top of that ownership.

The common wrong answer

Candidates often answer this by listing tools, naming a cost dashboard product for Crawl, a budgeting tool for Walk, and an ML rightsizing platform for Run, as if buying the right software automatically advances maturity. That misses the point entirely. The model is about process and ownership maturing over time; the tools are just what each stage happens to use, not what causes the progression.