Speaker
Abstract
We have all seen the moment: the platform goes live, the launch deck looks sharp, the portal is polished, the golden paths are documented, and yet teams quietly continue doing things the old way. Not always because the platform is bad, but because adoption was assumed, not owned.
Drawing on my platform experience across banking, healthcare, telecom, automotive, and travel tech at Booking.com, this talk explores the adoption problem behind platform engineering initiatives and internal developer platforms. Using real platform patterns, team behaviours, and lessons from both successful and struggling platforms, we will examine why technically successful platforms often fail to deliver business outcomes.
I will explore why “build it and they will come” rarely works, what the evidence tells us, why platform decisions create long-lived operational memory, and how team structures, ownership, contracts, and trust determine whether a platform becomes a multiplier or another system people work around.
And the journey does not stop with developer platforms. As we move towards Agentic AI Platforms, what changes when AI agents become platform consumers? I will share an early preview of my ongoing work, exploring emerging architectural challenges, what principles still hold, and what we must rethink.
The session will leave platform engineers, architects, and technology leaders with practical ways to spot adoption risks early, reduce friction before enforcing standards, and design platforms that teams can actually rely on in production.
Make the title more conciseClarify the audience takeaways.
$3,250, Conference (3 days). Current pricing ends November 20th. All pass options.
QCon San Francisco 2026 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Part of the track
Real World Platform Engineering Hosted by Daniel Bryant Platform Engineer, Co-Author of "Mastering API Architecture", Java Champion, and InfoQ News ManagerFrom the same track
Wednesday 18 November
10:35 Pacific DEKJ Session Platform Engineering Platform Engineering’s Second Act: From Vending Machine to Passport Control Smruti Patel, Alex Mann Three years ago on the QCon SF stage, I made the case for “Acceleration, Autonomy, and Accountability” as the pillars of a successful platform. Those pillars haven't moved. AI has just rewritten what each one requires, and the platform team's job along with it. 11:45 Pacific DEKJ Session Beyond the Kubernetes API: Building LinkedIn’s Compute Platform Ronak Nathani Principal Staff Software Engineer, Compute Infra @LinkedIn, Podcast Host @Software Misadventures LinkedIn’s Kubernetes-based compute platform spans more than 500k bare-metal machines, 5M pods, with thousands of developers doing more than 110k deploys a week. We don’t expose raw Kubernetes to developers and instead, provide a curated set of platform offerings. 13:35 Pacific DEKJ Session Observability: The Missing Control Plane for Agentic Engineering Rachael Wonnacott Global Head of Machine Learning and Applied AI Engineering @Capital Group, OpenUK Ambassador & Founding Member of FastFlowConf, Previously Head of Cloud Engineering @Fidelity International As AI agents move from generating code to testing, deploying, and operating it, the important question is no longer “How autonomous is the agent?” It’s “What can this agent safely decide without a human?”… 14:45 Pacific DEKJ Session Why Platform Teams Fail: From Developer Platforms to Agentic AI Shweta Vohra Architecture Leader @Booking.com, Author of "Decoding Platform Engineering Patterns" & "Dear Software and AI Architect", 24+ Years Experience Building Cloud, Platform, and AI Systems We have all seen the moment: the platform goes live, the launch deck looks sharp, the portal is polished, the golden paths are documented, and yet teams quietly continue doing things the old way. 15:55 Seacliff ABC Session Platform Engineering Building a Migration Platform: Moving 100+ Netflix RDBMS Workloads to Aurora PostgreSQL Ammar Khaku, Kshitij Gupta In late 2024, Netflix made a bet: consolidate the vast majority of our relational database use cases onto a single engine: Amazon Aurora PostgreSQL.