Skip to content
Lenny's PodcastLenny's Podcast

Building a culture of excellence | David Singleton (CTO of Stripe)

David Singleton is Chief Technology Officer at Stripe, where he oversees engineering and design teams. Since joining Stripe, David has helped grow the technology org across the U.S. and developed new engineering hubs in Singapore and Dublin as well as Stripe’s fifth hub, remote engineering, across the globe. Before Stripe, he spent 11 years at Google, where he was VP of Engineering, leading product development and coordinating more than 15 different hardware partnerships. In today’s episode, we cover: • Hiring secrets that set Stripe employees apart • How to build a product-minded engineering team • How to operationalize meticulousness • Strategies for maintaining developer productivity at scale • The process of “friction logging” used to make better products • How AI is changing the way engineers work • Insights for planning and prioritizing at scale — Brought to you by Mixpanel—Product analytics that everyone can trust, use, and afford | Eppo—Run reliable, impactful experiments | Braintrust—For when you needed talent, yesterday Find the full transcript at: https://www.lennysnewsletter.com/p/building-a-culture-of-excellence Where to find David Singleton: • Twitter: https://twitter.com/dps • LinkedIn: https://www.linkedin.com/in/davidpsingleton/ • Website: https://blog.singleton.io/ Where to find Lenny: • Newsletter: https://www.lennysnewsletter.com • Twitter: https://twitter.com/lennysan • LinkedIn: https://www.linkedin.com/in/lennyrachitsky/ In this episode, we cover: (00:00) David’s background (04:22) How Stripe’s unique hiring process has helped them build an incredible team (12:27) An example of a relentlessly curious and passionate employee (14:11) Structured hiring loops at Stripe (16:39) How Stripe built a product-minded engineering culture (21:56) Stripe’s operating principles  (25:39) How Stripe uses “friction logging” to build a meticulous product culture  (32:22) How to operationalize friction logging (35:02) How to set PMs up for success (36:53) Stripe’s collaborative approach to product evaluation (41:17) Advice for presenting to CTOs  (42:58) How to get better at building products (45:28) Stripe’s “engineerications” and the importance of getting into the weeds as a leader (52:03) Auto-testing and other strategies to improve shipping speeds (59:29) Improving developer productivity (1:00:54) How AI has impacted the way Stripe builds product  (1:07:03) Why David is excited about Copilot (1:09:24) Lessons from managing people (1:14:30) Planning and prioritization based on first-principles thinking (1:18:23) Lenny’s feedback from using Stripe (1:19:14) What’s next for Stripe (1:22:10) Lightning round Referenced: • Stripe: https://stripe.com/ • Jeff Weinstein: https://www.linkedin.com/in/jeffwweinstein/ • How we use friction logs to improve products at Stripe: https://dev.to/stripe/how-we-use-friction-logs-to-improve-products-at-stripe-i6p • GitHub Copilot: https://github.com/features/copilot • High Output Management by Andrew Grove: https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884 • Build by Tony Fadell: https://www.amazon.com/Build/dp/1787634116/ref=tmm_pap_swatch_0 • Scaling People: Tactics for Management and Company Building by Claire Hughes Johnson: https://www.amazon.com/Scaling-People-Tactics-Management-Building/dp/1953953212/ • Andrej Karpathy on YouTube: https://www.youtube.com/@AndrejKarpathy • Midjourney: https://www.midjourney.com/home/ • Emily Sands: https://www.linkedin.com/in/egsands/ • Michelle Bu: https://www.linkedin.com/in/michellebu/ Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com. Lenny may be an investor in the companies discussed.

David SingletonguestLenny Rachitskyhost
May 3, 20231h 29mWatch on YouTube ↗

At a glance

WHAT IT’S REALLY ABOUT

Inside Stripe’s Craft-Obsessed, User-First Culture of Product Excellence

  1. Stripe CTO David Singleton explains how Stripe builds a deeply product-minded engineering culture, anchored in operating principles like “users first” and “be meticulous in your craft.” He details practices such as co-creating products with early customers, friction logging, engineer vacations, and rigorous UX reviews that keep quality and reliability extremely high while shipping changes continuously.
  2. The conversation covers Stripe’s unique hiring approach, cross-functional product development model, and how they balance meticulousness with speed using strong tooling, automation, and incident learning. Singleton also discusses how AI and ML are already embedded in Stripe’s products and workflows, along with lessons on leadership, planning, and scaling high-performing teams.

IDEAS WORTH REMEMBERING

5 ideas

Co-create products with a small set of high-intent early users.

Stripe systematically finds power users (e.g., Figma, Slack, Atlassian) and builds products like Billing alongside them via shared channels, rapid feedback, and iterative demos—only launching broadly once this alpha group is truly delighted.

Make engineers deeply product-minded and embed PM-like responsibilities.

Early Stripe engineers acted as both builders and PMs, directly engaging users and owning product decisions; even today, engineers are expected to exercise many classic PM skills, with PMs acting as strategists and cross-functional locomotives rather than order-takers.

Operationalize “meticulous craft” through concrete practices, not slogans.

Stripe runs routine friction logs, UX reviews, and whole-company “Walk the Store” sessions to experience the product like users, identify high-friction moments, and then invest heavily in those moments (e.g., API error messages that deep-link to exactly the right docs).

Continuously ship safely by combining strong automation with rigorous learning.

Every change runs through comprehensive automated tests, staged deployments, and gradual traffic ramp-ups; incidents are treated as learning moments, with remediations prioritized ahead of roadmap work so reliability and iteration speed can both remain high.

Invest deliberately in developer productivity as a product in itself.

Stripe’s dev tools team treats internal developers as users—measuring pain, surveying monthly, and even adding a “crying octopus” button in tools for instant bug reports—leading to impactful changes like auto-deploys and auto-merge that compound productivity gains.

WORDS WORTH SAVING

5 quotes

Almost anything that you talk about as a value needs a practice behind it for the value to become real.

— David Singleton

We really do think that we can do the best work behind the scenes, so our users can have the splashy launches.

— David Singleton

If you have a tight feedback loop with users, it’s actually very hard to go wrong in product development.

— David Singleton

There’s one way to be very reliable, which is to never change anything. We chose to be very reliable and change things all the time.

— David Singleton

I ask candidates which leader they most admire—and then what performance feedback they’d give that person. Your ability to think critically about someone you lionize is very telling.

— David Singleton

Stripe’s user-first, product-minded engineering culture and late introduction of PMsHiring philosophy, interview structure, and rigorous use of referencesOperating principles in practice: meticulous craft, friction logging, UX reviews, Walk the StoreDeveloper productivity: auto-deploys, testing, dev tooling, and incident learningBuilding ultra-reliable systems while shipping fast and oftenAI and ML at Stripe: fraud detection, docs Q&A, SQL generation, internal tools, CopilotLeadership lessons: trust, time management, planning, and managing at scale

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.

Add to Chrome