Skip to content
Artwork for FinOps in Action
FinOps in Action · March 26 · 37 min

Making Cost a First-Class Engineering Concern ft. Jai Padmanabhan | Ep #62

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 Chapters: 00:00 - FinOps First Class & Guest Intro 01:14 - Cost Becomes Engineering 06:59 - Kubernetes Autoscaling 10:26 - Risk Versus Savings 12:48 - Dev Prod Mindset 14:36 - Storage In Regulated 18:31 - Big Savings Surprises 22:24 - Day One Playbook 24:40 - AI Spend Management 27:57 - Security And Compliance 31:58 - Final FinOps Advice 37:03 - Connect And Wrap 🎧 Subscribe for more FinOps leadership conversations → https://www.finopsinaction.com/ Quote of the Show: “ Treat cloud costs as if you were paying a bill from your credit card.” - Jai Padmanabhan Links: LinkedIn: https://www.linkedin.com/in/jaishankar-padmanabhan-software-executive/ Ways to Tune In: Amazon Music: https://music.amazon.com/podcasts/f25a9d18-c12f-4ee4-93f5-2aa96e509b55 Apple Podcasts: https://podcasts.apple.com/us/podcast/finops-in-action/id1790497808 iHeart Radio: https://iheart.com/podcast/268443483/ Podchaser: https://www.podchaser.com/podcasts/finops-in-action-5958339 Spotify: https://open.spotify.com/show/3IpjMc3qxDXZAjic5Zq21t Substack: https://finopsinaction.substack.com/ Transistor: finopsinaction.com YouTube: https://www.youtube.com/@PointFiveCloudCostEfficiency

0:00-37:22

transcript

No transcript — this publisher did not publish one.

show notes

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


Chapters:

00:00 - FinOps First Class & Guest Intro

01:14 - Cost Becomes Engineering

06:59 - Kubernetes Autoscaling

10:26 - Risk Versus Savings

12:48 - Dev Prod Mindset

14:36 - Storage In Regulated

18:31 - Big Savings Surprises

22:24 - Day One Playbook

24:40 - AI Spend Management

27:57 - Security And Compliance

31:58 - Final FinOps Advice

37:03 - Connect And Wrap



 🎧 Subscribe for more FinOps leadership conversations → https://www.finopsinaction.com/ 


Quote of the Show:

  • “ Treat cloud costs as if you were paying a bill from your credit card.” - Jai Padmanabhan


Links:


Ways to Tune In:

links10