May 4, 2023 · 1h 29m · lennys-podcast
Building a culture of excellence | David Singleton (CTO of Stripe)
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
Stripe CTO David Singleton breaks down the engineering, hiring, and operational philosophies that power Stripe's culture of excellence, detailing practices like friction logging, high-reliability continuous deployment, and AI-assisted developer workflows.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 16.3% of the talking time here. How this is scored →
Lenny as informed peer 2.6 Guest teaching 4.2 Guest disagreement 0.1 Lenny pushing back 0.1
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 1:17:55 Singleton pushing back against compliment
When Lenny mentions he uses Stripe and starts to offer polite praise, Singleton immediately cuts him off, insisting on hearing real critique and what bugs him rather than flattery.
Hardest push from Lenny ▶ 5:05 Host pre-emptively banning generic answersLenny explicitly refuses conventional platitudes like 'keeping a high bar,' demanding Singleton explain the specific, differentiated mechanics Stripe uses to hire top talent.
Biggest teaching moment ▶ 26:40 Masterclass on compounding craft into 10.5% revenueSingleton breaks down how methodical friction logging and micro-optimizations across checkout flows compound to a massive 10.5% revenue uplift in an industry normally measured in basis points.
Lenny holds their own ▶ 58:25 Host contrasting build pipelines with Airbnb scaleLenny leverages his operational engineering background at Airbnb to contextualize and contrast test run durations against Stripe's 45-minute production turnaround.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Welcome and the Energy of Stripe Sessions | 3 | 5 | 0 | 1 | Lenny opens with high-level praise for Stripe alumni and explicitly rejects generic hiring answers, nudging Singleton to provide distinct mechanics. Singleton lays out Stripe's core thesis, mission clarity, and patient hiring approach in depth. | |
| Solving Deep User Problems: The Stripe Atlas IRS Example | 3 | 5 | 0 | 0 | Lenny summarizes Singleton's points and references PM Jeff Weinstein's work. Singleton details the IRS EIN resolution and walks through Stripe's structured, practical interview loops. | |
| Building Product-Minded Engineering and Cross-Functional Teams | 4 | 5 | 1 | 0 | Lenny brings up the notable fact that Stripe delayed hiring PMs until around employee 200. Singleton gently corrects the exact timeline, explaining that early engineers acted like technical PMs co-creating with alpha users like Slack and Figma. | |
| Operationalizing Meticulous Craft and Friction Logging | 3 | 6 | 0 | 1 | Lenny asks how Stripe reconciles meticulous craft with shipping velocity. Singleton delivers an extensive masterclass on operationalizing principles via friction logging, linking API error docs, and checkout flow optimizations that yielded a 10.5% revenue uplift. | |
| Implementing Friction Logs and Allocating Polish Bandwidth | 3 | 5 | 0 | 0 | Lenny explores how teams balance executive friction log feedback without burnout. Singleton explains prioritization mechanics, incident remediation baselines, and team autonomy in allocating polish bandwidth. | |
| Pre-Shipping UX Reviews and 'Walk the Store' | 3 | 5 | 0 | 0 | Lenny brings up a prompt from Shreyas Doshi about early pre-shipping reviews. Singleton explains collaborative UX walkthroughs and the company-wide 'Walk the Store' practice at Friday Firesides. | |
| Executive Review Advice and Tight Feedback Loops | 2 | 5 | 0 | 0 | Lenny asks how ICs should prepare for high-stakes executive reviews with the CTO. Singleton provides tactical advice to anchor arguments in the user model and build rapid feedback loops. | |
| Sponsor Message: Braintrust | 0 | 0 | 0 | 0 | Sponsor advertisement for Braintrust read as a solo monologue by Lenny. | |
| Measuring and Optimizing Developer Productivity | 3 | 6 | 0 | 0 | Lenny raises Singleton's concept of 'engineer occasions' and quotes high-scale reliability stats. Singleton explains deep immersion in tooling, automated continuous deployment pipelines, and post-incident learning. | |
| Small Developer Productivity Tweaks with Compounding Impact | 4 | 5 | 0 | 0 | Lenny expresses surprise at the 45-minute commit-to-production turnaround time and compares it to Airbnb. Singleton explains parallelization and selective test execution. | |
| Accelerating Engineering with GitHub Copilot | 2 | 4 | 0 | 0 | Lenny asks about internal engineering adoption of GitHub Copilot and the sentiment around AI writing code. Singleton explains where Copilot provides real leverage, such as test boilerplate generation. | |
| Engineering Leadership, Reference Checks, and Energy Management | 2 | 5 | 0 | 0 | Lenny asks for high-level management lessons. Singleton discusses heavy reliance on reference checks over interview loops, radical delegation, and Sunday evening time management routines. | |
| First-Principles Planning and the 'Inverted W' Model | 2 | 6 | 0 | 0 | Lenny asks about Stripe's prioritization prowess. Singleton candidly admits internal planning NPS is mixed due to rapid growth, and explains their first-principles Inverted W planning model. | |
| Live User Feedback and Product Improvement | 4 | 1 | 1 | 0 | Lenny mentions using Stripe for his newsletter, prompting Singleton to solicit direct product feedback. Lenny shares a specific critique about cohort churn retention visualizations. | |
| Lightning Round: Books, AI Videos, Questions, and Tools | 3 | 3 | 0 | 0 | Standard lightning round covering books, Karpathy's AI YouTube videos, creative interview questions, Midjourney with Discord UI, and the internal 'crying octopus' paper-cut reporter. | |
| Connecting with David Singleton and Final Thoughts | 1 | 1 | 0 | 0 | Brief wrap-up where Singleton shares contact information and asks listeners for product feedback. |
Statements from this episode (26)
Many Stripe employees work in entirely different roles than initially hired
“Very, very many people at Stripe today are doing a quite different job to the one that they joined for.”
Stripe Atlas partnered with the IRS to issue EINs instantly
“Eventually we worked with the IRS to make it possible for But for us to issue those numbers much, much more quickly, like instantly as you sign up.”
Singleton: Stripe engineering interviews permit Google and Stack Overflow searches
“The other thing that all these loops have in common is nothing is a trick question. Like we try to put people into an environment, which is as close to doing the actual work together as we possibly can. So I mean, for engineers, for instance, we've got several…”
Singleton: Best PMs for Developer Products Are Highly Technical Engineers
“The best PMs for developer focused products, I think are usually very technical. They're mostly former engineers themselves, or maybe kind of current engineers still tinkering on the side, but bringing, you know, a lot of user insight and strategy to the probl…”
Singleton: Stripe Co-Created Stripe Billing With Slack and Figma
“And when we got to starting the Stripe Billing product, we realized that there were a number of our existing users. These were companies like Figma and Slack. We were already using Stripe for payments, but had these subscriptions business models. And we figure…”
Stripe's API dedicates more codebase to edge cases than main flows
“There's actually more code in the jobs that serve the Stripe API to handle those edge cases than in the actual main flow.”
Migrating to Stripe Checkout increases average customer revenue by 10.5 percent
“What we've found, we've recently measured the difference between, so with a bunch of actual users who've migrated from a fairly vanilla integration where they, you know, built their own checkout flow to one of these surfaces to our payment element or to Stripe…”
CTO David Singleton completes monthly user onboarding to log product friction
“For years and years, I have gone through the process of onboarding as an user to Stripe once a month, writing a friction log, and then tagging in the right people across the company that might need to take action on some of the things that we're observing.”
Singleton: Stripe prioritizes incident remediations over planned roadmap work
“And so that means that we identify incident remediations. That's what we call those. And we prioritize those carefully, and most of them, the ones that matter, actually get prioritized before other work on the roadmap.”
Stripe conducts company-wide product walkthroughs called 'walk the store'
“There's something that, that, that we do occasionally and I've done occasionally at Stripe called walk the store where we'll actually do that process of like looking at the product together with the whole company. So we have a weekly meeting called Friday Fire…”
Stripe engineering managers take annual 'engineercations' to retain operational context
“I advise engineering managers at Stripe that they should do an engineer occasion sometime in their first quarter to six months at the company gives you a tremendous amount of context for what your teams are actually experiencing. And then for folks who do it o…”
Singleton: Stripe's core product infrastructure is mostly implemented in Ruby
“For what it's worth at Stripe, we write a lot of code in Ruby. We write a lot of code in other languages like Java and TypeScript as well, but our kind of core infrastructure is mostly implemented in core product infrastructure, mostly implemented in Ruby.”
Stripe uses rolling monthly engineering surveys to prioritize dev tool roadmaps
“We do a monthly survey. We operate in enough scale now where we can ping enough people once a month that we get a statistically significant sample of the entire organization without having to get everyone to respond. Every individual responds by once every six…”
Stripe now processes as much volume as 2010's entire e-commerce industry
“Stripe today, like we move as much money as all of e-commerce was when Stripe got started.”
Stripe automatically deploys engineer code changes to production within 45 minutes
“Every change that Stripe engineer submits once it's passed those tests, it actually ends up in production automatically over the course of the next 45 minutes or so.”
Stripe's test and CI environment is its largest distributed system
“In fact, our distributed change and test environment at Stripe is the biggest distributed system that we actually run.”
Singleton: Stripe engineers previously had to manually babysit each production deployment
“Before we introduce that, so sometime within the last five years, each deployed to production required An engineer to actually babysit it, to like watch it as it went out, make sure all the charts look good.”
Stripe built custom auto-merge feature on GitHub to eliminate review friction
“About eight months ago, we made it possible. We've got a, we use a tool for code review. It's just quite popular as GitHub enterprise, but we built a bunch of our own experiences and controls around that. And we have a little tick box that you can take on your…”
High GPU compute costs force AI startups to monetize from day one
“One big difference between AI startups and others is it's actually quite expensive to operate an AI startup in terms of the compute resources, like running this stuff in these GPU machines is quite expensive. So typically these companies need to have a monetiz…”
OpenAI uses Stripe to power ChatGPT Plus monetization and financial operations
“OpenAI, for instance, is using us for
monetizing chat GPT plus and all their other products, but they don't just stop there. We're actually helping power all of their subscriptions and revenue tracking and financial operations around the business.”
Stripe deploys internal GPT-4 tool with shareable prompt presets across teams
“We stood up an integration to GPT-IV and an internal UI to use models like that. But here's the thing that I want to kind of relate to all of your viewers. We find that we built presets into that. So when you work with large language models, you want to write …”
Generating test boilerplate with GitHub Copilot profoundly improves overall code quality
“It's actually using co-pilot to generate your test cases turns out to be extremely valuable. There's a reasonable amount of boilerplate that is kind of like repeated code and concepts that goes into writing good tests, but you also have to reason very carefull…”
Stripe utilizes an 'inverted W' framework for company-wide strategic planning
“We run a kind of inverted W process. So we typically have teams surface what, you know, their immediate thoughts are on the most important things to do. We'll then have a group of product leaders, you know, get together and try to synthesize the most important…”
Stripe Connect originated from early marketplace integrations with Lyft and Shopify
“So the ideas behind Stripe Connect came from working with companies like Lyft and Shopify in the very early days. They were using Stripe for pay-ins, but we realized, oh, these companies are operating in these multi-sided marketplaces, and there's a ton of hea…”
Midjourney's Discord interface brilliantly teaches users how to prompt AI from others
“This is not the right interface for this tool, but actually it's very smart because you learn from other people on discord, how they're prompting the AI in order to get the kind of results that they're looking for.”
Stripe dev tools use a crying octopus button for frictionless bug logging
“Probably the most profound thing is we put a little button in every single developer tool at Stripe. It is an emoji of an octopus that is crying. If you click it makes it possible to just type in what your What's gone wrong? And then we have our developer prod…”