Jai Padmanabhan on Making Cost a First-Class Engineering Concern
Why does cloud cost optimization only start after it’s already too late?
In this episode of FinOps in Action, I sit down with Jai Padmanabhan, who shares why cloud cost is no longer just a finance concern; it’s a core responsibility for engineering teams. Drawing on decades of experience leading platforms in complex and regulated environments, Jai explains how the shift to the cloud fundamentally changed how organizations think about cost, and why treating it as an afterthought leads to reactive, high-pressure optimization later on.
He breaks down how teams can build cost awareness into their day-to-day workflows, from setting budgets and enforcing guardrails to leveraging automation that scales infrastructure up and down based on real demand.
Jai also explores the trade-offs between efficiency and reliability, emphasizing why SLAs should always take priority in production and how over-optimization can introduce unintended consequences. From storage strategies in regulated industries to the hidden complexity of data transfer costs, he shares practical insights on where organizations commonly overspend and how to avoid it.
Here’s what we talked about:
The dangers of reactive cost optimization after the bill shows up
Building cost awareness into engineering teams through budgets and guardrails
How Kubernetes changes the approach to cost optimization
Storage optimization strategies, especially in regulated industries
How AI usage is impacting cloud spend (and why it’s still early)
Why FinOps should be treated as everyone’s responsibility
Quote of the Show:
“ Treat cloud costs as if you were paying a bill from your credit card.” - Jai Padmanabhan
Connect with Jai:
In this episode of FinOps in Action, Jai Padmanabhan shares how his experience leading engineering and platform teams shaped his perspective on cloud cost, and what he learned after seeing organizations treat optimization as a reactive exercise once the bill arrives. He explains why cost must be treated as a first-class engineering concern alongside performance and security, how the shift to the cloud turned every engineer into a daily decision-maker on spend, and why building guardrails, automation, and accountability into engineering workflows is critical to avoiding unnecessary costs.