How I Doubled eBay’s Productivity - And Still Got Fired @infoq
How I Doubled eBay’s Productivity - And Still Got Fired  @infoq
Uploaded May 2026 | Updated September 2026, 2 weeks ago
📩 Subscribe to the InfoQ Weekly newsletter!

No hype. No fluff. Just the signals senior engineers actually care about - from #AI, #DevOps, and #Java to #CloudComputing & #SoftwareArchitecture.

🗓️ Delivered every Tuesday, it's your quick round-up of innovator & early-adopter technologies.

Join 250,000+ developers who read it to stay ahead 👉 infoq.com/news/#infoq-nl
************************************************
Can you double engineering productivity and still fail to save the company?

Former eBay Chief Architect Randy Shoup reveals the raw, "middle-out" truth of eBay’s massive DevOps transformation. From co-inventing database sharding and Kafka-style messaging in 2000 to battling a "culture of fear" and 10-day lead times in 2020, Randy shares the technical triumphs and the organizational "third rails" that eventually led to his exit.

If you are a senior developer, architect, or engineering leader, this is a masterclass in the Innovator’s Dilemma. Learn why DORA metrics and high-performance "Velocity" initiatives are often not enough to overcome centralized waterfall planning and "learned helplessness" in a flat business.

⏱️ Video Timestamps (For Navigation)
0:00 — The Rise and Fall of eBay Velocity
1:15 — What eBay invented (Sharding, Tracing, Circuit Breakers)
3:45 — The State of eBay in 2020: 10-day Lead Times
6:10 — The Value Stream Map: Identifying the Bottlenecks
9:00 — Doubling Productivity: Outcomes of the Velocity Initiative
12:30 — The "Randy Shoup" Playbook: No Original Ideas, Just Execution
15:55 — Scaling the Transformation: S-Curves and Pilot Teams
18:40 — Modernizing Mobile: From "Impossible" to Weekly Releases
21:15 — Why We Didn’t Save the Company: The Innovator’s Dilemma
24:30 — Strategy vs. Execution: The $1.5B Payment Project
27:10 — Pathological vs. Generative Cultures (Westrum Typology)
31:00 — The "Third Rail" that got Randy fired
33:45 — Lessons Learned: Top-Down, Bottom-Up, and Middle-Out

🔗 Transcript & slides available on InfoQ: bit.ly/4nABJjC

#SoftwareArchitecture #DevOps #EngineeringLeadership #DORAmetrics #eBay #TechStrategy
How I Doubled eBay’s Productivity - And Still Got FiredAI Amplifies Team Strengths and Weaknesses in Software DevelopmentChris Richardson EXPOSES the Microservices Cognitive Load TrapHow Monzo Survived a 2-Year Migration (and Why You Might Not)Unmasking Dev Productivity: AI, Bias & the Hidden TruthsJavas Data Blindspot EXPOSED: 1000x Faster In-Memory Processing?20 years of InfoQ 🎂 #ClaudioMasolo #InfoQ20 #DevCommunityCloud and DevOps InfoQ Trends Report 2026: AI, Resilience, Platforms, FinOps, and SovereigntyHow Meta Scaling AI-Native Engineering Tripled Code Coverage (And Cut Slop)Mental Models in Architecture & Societal Views of Technology: A Conversation with Nimisha AsthagiriFormal Methods for Every Engineer in an AI-Powered FutureChasing Efficient Java Development: From 1BRC to Developing Hardwood AI Natively
InfoQ |

How I Doubled eBay’s Productivity - And Still Got Fired

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER