Speaker
Abstract
Once a stock market darling and a pioneering hyperscaler in the 1990s and early 2000s, eBay has been in steady decline since the 2010s. A household name with a flat business, eBay has been unable to make substantive strides in its market reach or its engineering outcomes in the last 15 years. What happened?
I was a Distinguished Architect at eBay from 2004 to 2011, and returned as VP of Platform Engineering and Chief Architect from 2020 to 2022. As Chief Architect, I led the company-wide Velocity initiative, which has continued to double engineering productivity across the board. By executing the DevOps playbook, this has been an unqualified success. In the two years I was there, and continuing over the three years since, teams have improved on all of the DORA software delivery metrics, and report better collaboration and developer satisfaction. At the same time, improvements have stagnated, and teams consistently struggle to reach Elite status or to alter the overall trajectory of the business.
This talk is an insider’s attempt to make sense of this seeming contradiction between micro-successes and macro-failures, and attempts to abstract 20 years of participation and observation into a set of actionable lessons for any organization attempting to transform itself.
We will deep dive into the following:
- Technology Evolution, moving over time Innovator to Laggard, from early adopter to isolated holdout
- Business Strategy, encompassing Learned Helplessness, the Innovator’s Dilemma, and Centralized Planning
- Organizational Culture, epitomizing Westrum’s pathological culture with zero-sum thinking, empire building, risk aversion, and a constitutional inability to acknowledge failures
Come for the Continuous Delivery story; stay for the unvarnished retrospective on eBay’s hidebound engineering and organizational culture. As the old joke goes, “I may be slow, but I do poor work!”
QCon San Francisco 2025 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.
From the same track
Monday 17 November
10:35 Seacliff ABC Session Platform Engineering Continuous Delivery for Foundational Platforms Ian Nowland CEO @Junction Labs, Author of O'Reilly's Platform Engineering, Previously SVP Core Engineering at Datadog and Leader of AWS Nitro Platform teams frequently inherit systems that were never architected for their current scale, yet are so foundational that downtime can halt the business. 11:45 Seacliff ABC Session Beyond Line Charts: Why Some Diversity in Telemetry Visualization Is Long Overdue Yao Yue Founder & Chief Executive Officer @IOP Systems, Platform Engineer, Distributed System Aficionado, Cache Expert For decades, visualization of service metrics overwhelmingly converges to line charts. The time-centric nature of real-time telemetry further cemented this phenomenon via storage layouts and domain-specific query languages. 13:35 Ballroom BC Session Microservices Platforms: When Team Topologies Meets Microservices Patterns Chris Richardson Creator of microservices.io, Java Champion, & Core Microservices Thoughtleader When many teams work on a large, complex application, the microservice architecture potentially enables them to work independently and deliver a continuous stream of changes. 14:45 Seacliff D Unconference Unconference: Modern Platform Engineering and Dev Enablement 15:55 Ballroom BC Session Platform Engineering: Lessons from the Rise and Fall of eBay Velocity Randy Shoup SVP Engineering @Thrive Market, Previously @eBay, @Google, @Stitch Fix Once a stock market darling and a pioneering hyperscaler in the 1990s and early 2000s, eBay has been in steady decline since the 2010s. A household name with a flat business, eBay has been unable to make substantive strides in its market reach or its engineering outcomes in the last 15 years. 17:05 Ballroom BC Session Resilience Enhancing Reliability Using Service-Level Prioritized Load Shedding at Netflix Anirudh Mendiratta, Benjamin Fedorka How does Netflix maintain a seamless viewing experience for millions of users, especially during traffic spikes or when backend datastores are overloaded? Autoscaling can help during traffic spikes, but it costs money, takes a few minutes to kick in, and capacity may not always be available.