Matt and Ganesh discuss why compliance can be mostly automated rather than a mandatory bottleneck, how to turn 30-day approval processes into continuous audit readiness through controls as code, and why treating platform teams as product teams drives natural adoption. They also explore decision latency as a core organizational problem, the importance of stakeholder management as a DevOps skill, and how AI agents may shift infrastructure drift management from prevention to embrace.

Sneha and Ahmed explain why developer platforms need a product mindset alongside engineering, how renaming their team from Delivery Engineering opened a broader strategic mandate, and why SRE and reliability belong inside the platform rather than a separate function. They also share how to think about build vs. buy, when to start a platform function, and why AI is another evolution in the platform story rather than a revolution.

Dan and Ganesh discuss weekly operational reviews that tie technical metrics back to user experience, how load testing and chaos engineering help Series A companies mature faster, and why dogfooding their own on-call product creates better engineering decisions. They also explore a concerning trend in Rootly's customer data showing that AI coding assistants are driving more incidents, and why reliability practices become even more critical as code generation speeds up.

Tamar walks through how the job fundamentally changes as you move from manager to director to VP, including a key shift at director level where you stop working within constraints and start reshaping them. She and Ganesh dig into how AI is less a new challenge than a pressure test on existing engineering practices, and why teams with strong CI/CD and observability will move faster while undisciplined teams will struggle. Tamar also shares a mentorship pairing program where engineers already effective with AI coach those still learning, sometimes reversing the usual seniority dynamic. And she explains how Box's platform team connects internal standardization directly to external customer value through security, access control, and product cohesion.

Rob and Ganesh discuss why velocity without direction is the wrong thing to optimize for, how LLMs can help teams think like a great QA engineer again, and what it takes to run exploration and core systems teams at fundamentally different speeds. They also get into why traditional delivery metrics fall short for innovation work, and what to measure instead when teams are discovering rather than just executing.

Boyan and Ganesh discuss why velocity and quality don't have to be a trade-off, how SIXT's standardization work paid off unexpectedly when AI arrived, and what it looks like to build a platform that earns its own adoption. They also get into how to measure platform value with cycle time and product ROI, and what starting from scratch would look like in an AI-first world.

https://www.cortex.io/podcast

Randy and Ganesh chat about how fear can block progress, why recovery speed matters more than trying to prevent every failure, and how teams improve through steady, incremental gains. They also discuss a few practical ways to build trust around metrics so organizations can use visibility for learning instead of punishment.

Steve and Ganesh discuss why traditional engineering metrics like cycle time and deploy frequency can paint a dangerously misleading picture, how business context breaks down as it cascades through an org, and why round tables—not all-hands meetings—are the best way to diagnose where context stops flowing.

Fred and Ganesh discuss criticality tiering based on customer jobs to be done, why automation is essential to avoid overloading engineering teams, the inseparable relationship between security and production readiness, and why the best advice for starting a production readiness program is to start small and treat it as a journey.

Ganesh and Kaspar unpack why standardization doesn't kill creativity, the critical difference between "rigid paths" and "Golden Paths," and why treating your platform as a product is non-negotiable. They also discuss the emerging role of AI, arguing that AI agents are effectively a new class of "junior engineer" that makes robust platforms more essential than ever.

Nathen and Ganesh discuss value stream mapping as a planning tool for 2026, why SLOs are becoming more important in an AI-first world, the trust paradox in AI adoption, how to use AI as a catalyst for cultural change, and why measuring lines of code generated by AI misses the point entirely. They also explore how foundational practices like working in small batches, strong version control, and user-centric focus become even more valuable when AI is writing more of your code.

Tyler and Ganesh discuss their thinking around build vs. buy, how to measure the value of internal tools beyond traditional ROI, the psychology of sunk costs, and more.

The conversation explores the key moments that forced a fundamental mindset shift from prioritizing speed to engineering for enterprise-grade reliability and scale. Anish and Ganesh discuss the cultural and architectural decisions that defined this transition and offer a playbook for engineering leaders navigating today's AI-driven landscape, where the pressure to move fast is greater than ever.

On Braintrust, Ganesh Datta, CTO and Co-founder of Cortex, sits down with CTOs, VPs of Engineering, and technical leaders who've been in the trenches—the ones who've made the hard calls, shipped through the chaos, and built teams that actually work.

They talk about the real stuff: the architectural decisions that come back to haunt you, the cultural rituals that keep teams aligned, and the practices that separate high-performing teams from everyone else.

Whether you're leading a team of ten or a thousand, if you're trying to ship faster without breaking things, this podcast is for you.