Podcasts

GenAI Security: Defending Against Deepfakes and Automated Social Engineering

In this episode, QCon AI New York 2025 Chair Wes Reisz speaks with Reken CEO and Google Trust & Safety founder Shuman Ghosemajumder about the erosion of digital trust. They explore how deepfakes and automated social engineering are scaling cybercrime and argues defenders must move beyond default trust, utilizing behavioral telemetry and game theory to counter attacks that simulate human behavior.

Looking for Root Causes is a False Path: A Conversation with David Blank-Edelman

In this podcast, Michael Stiefel spoke with David Blank-Edelman about the relationship between software architecture and site reliability engineering. Site reliability engineering can give architecture vital feedback about how the system actually behaves in production. Architects and designers can then learn from their failures to improve their ability to build systems that can evolve.

How to Use Apache Spark to Craft a Multi-Year Data Regression Testing and Simulations Framework

Vivek Yadav, an engineering manager from Stripe, shares his experience in building a testing system based on multi-year worth of data. He shares insights into why Apache Spark was the choice for creating such a system and how it fits in the "traditional" engineering practices.

Cloud Security Challenges in the AI Era - How Running Containers and Inference Weaken Your System

Marina Moore, a security researcher and the co-chair of the security and compliance TAG of CNCF, shares her concerns about the security vulnerabilities of containers. She explains where the issues originate, providing solutions and discussing alternative routes to using micro-VMs rather than containers. Additionally, she highlights the risks associated with AI inference.

Architecture Should Model the World as it Really is: a Conversation with Randy Shoup

In this podcast, Michael Stiefel spoke with Randy Shoup about how to evolve your software after a software failure, and how to improve the resilience of your software by modeling transient states using events and workflows. Software failure is inevitable, but learning from failure, including making the necessary changes to organizational culture, can make your software more resilient.