Cloud spend is growing faster than revenue and leadership wants it under control across dozens of teams. How do you set up org-wide cost governance, or FinOps, without turning into the team that says no to everything?
What they are really testing: Whether you can make cost a shared engineering responsibility through visibility, accountability, and incentives, rather than policing spend centrally, and whether you balance savings against velocity.
A real interview question
Cloud spend is growing faster than revenue and leadership wants it under control across dozens of teams. How do you set up org-wide cost governance, or FinOps, without turning into the team that says no to everything?
What most people say
drag me
“I would set up cost monitoring and alerts, find the biggest spenders, buy reserved instances and savings plans for our steady-state usage, and set budget limits so teams get cut off when they overspend.”
These are real tactics but it is a central-policing model. Committing to discounts before eliminating waste locks in inefficiency, and hard cutoffs treat cost as a constraint to enforce rather than a metric teams own.
The follow-ups they ask next
A team is way over budget but their spend is driving the fastest-growing revenue line. What do you do?
Listen for unit economics and value framing rather than a reflexive cut. Cost per dollar of revenue, not absolute spend.
How do you get engineers to actually care about cost instead of treating it as someone else final problem?
Listen for ownership, visibility, incentives, and cultural framing, not just alerts and limits.
What the interviewer is listening for
- Starts with visibility and cost attribution before any optimization
- Pushes budget ownership to the teams that incur spend
- Sequences waste, rightsize, then commit, in that order
- Frames cost as unit economics and balances savings against velocity
What sinks the answer
- Centralizes cost policing instead of distributing ownership
- Commits to discounts before eliminating waste
- Uses hard cutoffs that ignore the value the spend generates
- Optimizes the absolute bill with no view of unit economics
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I would treat cost as [a shared engineering responsibility]. First I get [visibility and attribution], then push [budgets and dashboards] to each team. I optimize in the order [waste, rightsize, commit], surface [unit economics] alongside performance, and balance savings against [velocity] so FinOps optimizes [value], not just [the bill].”
Keep going with strategy & leadership
Principal
You are asked to lead the migration of 200 services to the cloud. What is your strategy and how do you de-risk it?
Principal
A few teams want an internal feature-flag and config service. You could build one on top of your cloud primitives or buy a SaaS. How do you make the build-vs-buy call for a platform capability the whole org will depend on?
Principal
You have 30 teams each spinning up cloud infrastructure their own way, with wildly different quality. How do you establish golden paths or paved roads so teams stop reinventing the wheel without grinding delivery to a halt?
Principal
Design a globally distributed, multi-region active-active system. Walk me through the hard parts.
Principal
The org is moving to many cloud accounts across many teams. How do you design the multi-account landing zone and guardrails so teams move fast safely, instead of locking everything down or letting it become the wild west?
Principal
Design a global rate limiter that protects your APIs across many regions, enforcing per-customer quotas. Walk me through the design and, more importantly, the trade-offs you would make and how you would sequence building it.
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free