Nov 11, 2018 · 56m · y-combinator
A Conversation with Werner Vogels · Y Combinator
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this Y Combinator talk, Amazon CTO Dr. Werner Vogels explores the genesis of AWS, Amazon's unique engineering culture, and key advice for startup founders. He details how customer-driven innovation, operational discipline, and long-term thinking drive sustainable software architecture.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
The partners as informed peer 2.0 Guest teaching 3.4 Guest disagreement 1.1 The partners pushing back 0.0
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 47:22 Where is the outrage over data breaches?
Vogels forcefully breaks conversational tone to condemn tech leaders and founders for normalizing massive data breaches instead of treating security as job number one.
Hardest push from the partners ▶ 28:06 Challenging whether AWS knew it would change the landscapeThe host presses Vogels on whether Amazon genuinely foresaw AWS revolutionizing global software development or if it was merely an incremental, slow iteration.
Biggest teaching moment ▶ 6:35 Prompt correction on CTO promotion timelineVogels swiftly corrects the host's premise that it took years to become CTO, noting it took only six months before laying out the rigor needed for multi-order-of-magnitude scaling.
The partners hold their own ▶ 32:18 Citing the 130-service catalog to probe product strategyThe host demonstrates active preparation by citing AWS's catalog of 130 services to guide the conversation into internal feature prioritization and roadmap decision-making.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| Early Career and Path to Amazon | 1 | 3 | 1 | 0 | The host asks open-ended background questions about Vogels' career prior to Amazon. Vogels explains his transition from radiotherapy to distributed systems academia and demystifies early Amazon as an advanced tech powerhouse rather than just a simple online bookstore. | |
| Scale, Innovation, and Engineering Trade-Offs | 2 | 3 | 1 | 0 | The host asks whether distributed systems research shifted from academia to big tech. Vogels explains how Amazon operated 5-10 years ahead of industry standards and had to deliberately accept technical debt and duplication to prioritize velocity. | |
| Becoming CTO and Reliability Engineering Programs | 1 | 4 | 1 | 0 | Vogels immediately corrects the host's timeline by noting he became CTO in six months, not a couple of years. He then provides an extensive breakdown of introducing academic rigor, p99 latency controls, and game days pulling data center plugs. | |
| The Creation and Genesis of AWS | 2 | 4 | 1 | 0 | The host asks about scaling engineering culture and the inception of AWS. Vogels delivers a comprehensive breakdown of flat organizational hierarchy, the distinction between a VP of Engineering and CTO, and the architectural journey from monolith to microservices and cloud primitives. | |
| AWS Scale and Customer-Driven Innovation | 3 | 3 | 1 | 0 | The host brings specific knowledge of AWS's vast directory of over 130 services to ask about product development. Vogels details Amazon's balance sheet investment criteria and explains why AWS launches rock-solid minimal feature sets rather than fragile MVPs. | |
| Working Backwards and Narrative Memos | 3 | 3 | 1 | 0 | The host references Vogels' decade-old blog post on the 'Working Backwards' process. Vogels elaborates on the PR/FAQ framework and explains Amazon's strict ban on PowerPoint slides in favor of six-page silent narrative memos. | |
| Future of Cloud Development and Cybersecurity | 2 | 4 | 2 | 0 | The host asks about the next five years of cloud computing. Vogels passionately shifts focus to cybersecurity, sharply criticizing the tech industry's complacency regarding repeated customer data breaches and demanding engineering accountability. |
Statements from this episode (17)
Werner Vogels: Amazon was a technology company, not a retailer
“One glimpse in that kitchen, however, and I realized that this is a massive technology operation. It's not a retailer. It's a technology company. And operating at a scale that I had never seen before. Definitely not at other companies that I'd consulted for.”
Werner Vogels: Amazon accepts duplication and technical debt to maximize speed
“At Amazon, moving fast and innovating fast, and having a very long pipeline of experiments, that's the more and most important thing, so you're willing to allow duplication to happen, you're allowed to create technical debt, as long as you know that you have t…”
Werner Vogels: 10x growth requires revisiting almost all processes and technologies
“In essence, we go from order of magnitude growth. You have to revisit almost everything that you do, whether it's your processes, but also your technologies.”
Werner Vogels: Median latency is useless; engineers must optimize the 99th percentile
“A medium latency of, let's say, 1.2 seconds off your webpage to your customers doesn't say anything. Just says that 50% of your customers have a worse experience. You need to know how much worse. And then, from an engineer, so for example, the 99 percentile or…”
Werner Vogels: A CTO drives major programs and commercializes internal technology
“Mostly the role of a CTO is to drive really big programs and think about sort of what is the technology that we need for the future to be able to be on solid footing as a business? Or in the case of Amazon, what are the kind of unique technologies that we've d…”
Werner Vogels: Early startups failed due to physical IT infrastructure costs
“So most of those companies that were initially successful around the Amazon catalog
All failed.
And they didn't fail because they didn't have great ideas.
They failed because they couldn't get their IT staff ready, or get the money to actually do, do, do, d…”
Werner Vogels: Hierarchy is unnatural; fast-moving companies should remove structure
“There's a very unique culture at Amazon, I think, that works really well for fast-moving companies, and that is to have, to build your teams as independent as possible, to remove as much hierarchy and structure from your organization as that is possible.
Hier…”
Werner Vogels: VP of Engineering manages people, CTO drives technology strategy
“The VP of engineering every morning wakes up thinking, do I have the absolute best team?
Is my team in the best position to deliver what they need to deliver?
It's a people person.
Yeah, I'm really thinking about making sure that your engineer's in the righ…”
Werner Vogels: Shared engineering resources make development organizations move slower
“Shared resources are the thing that sort of make you move slower.”
Werner Vogels: Fast provisioning fails to stop engineers hoarding server capacity
“And apparently just an hour to get capacity is not enough. It's not a good enough incentive to sort of release stuff again. So we needed to go to a model, first of all, where you could take engineers out of the loop, and where you could have business rules to …”
Werner Vogels: Major investments must materially move the Amazon balance sheet
“Then at Amazon you have to rule that if you do that, If it's going to be successful, it needs to be successful in a way that has significant impact on the Amazon balance sheet. Now, it's not that we're interested in another, let's say, ah, that sounds coy, but…”
Werner Vogels: 95% of AWS features are direct customer requests
“About 95% of features and services that we deliver are in response to direct requests from our customers.”
Werner Vogels: Engineer-led product development results in pure technology, not actual products
“If you're a heavy technology company, lots of engineering, there's a risk that the engineers get in charge. Yeah? If they get in charge, you do not necessarily build products, you build technology.”
Werner Vogels: Clear narrative writing is impossible without clarity of mind
“It's very hard to write a clear document if you do not have clarity of mind. Writing a narrative is extremely hard”
Werner Vogels: Retrofitting security into a growing product is a massive nightmare
“I think the only way, if you actually build your new business without security in mind, it will be very hard to retrofit it into it. Yeah, and so, you will have a nightmare, let's say, two, three years down the road, when you become successful and you grow, an…”
Werner Vogels: Continuous deployment is far more secure than massive code reviews
“Now, I honestly believe continuous deployment actually is better from a security point of view, because in the past you would write 50,000 lines of code, Security team would come in, would review it, would bless it, and they had no clue what they were doing. T…”
Werner Vogels: Mercenary and missionary startups require fundamentally different tech architectures
“Jeff often makes the distinction between mercenaries and missionaries. Yeah? Mercenaries are the startup founders that are in it for the money. Yeah? And missionaries are the ones that are in it for the love of the product. Yeah? I want to build this product, …”