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

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

Lenny's PodcastMay 4, 20231h 29m

David Singleton (guest), Lenny Rachitsky (host), Narrator, Narrator

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

In this episode of Lenny's Podcast, featuring David Singleton and Lenny Rachitsky, Building a culture of excellence | David Singleton (CTO of Stripe) explores inside Stripe’s Craft-Obsessed, User-First Culture of Product Excellence 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.

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

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.

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.

Key Takeaways

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

Stripe systematically finds power users (e. ...

Get the full analysis with uListen AI

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.

Get the full analysis with uListen AI

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. ...

Get the full analysis with uListen AI

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.

Get the full analysis with uListen AI

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.

Get the full analysis with uListen AI

Use AI to augment both customer experience and internal effectiveness.

Beyond long-standing ML in products like Radar, Stripe now uses LLMs to power docs Q&A, natural-language-to-SQL in Sigma, and internal presets for knowledge work; engineers use tools like GitHub Copilot especially for test generation and boilerplate, shifting focus to higher-order design.

Get the full analysis with uListen AI

At scale, leaders must over-index on hiring, trust, and intentional time use.

Singleton emphasizes rigorous references, delegating slightly more than feels comfortable, modeling operating principles, and weekly intentional planning of his own time, since most important decisions are made far from the CTO and must still align with mission and principles.

Get the full analysis with uListen AI

Notable 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

Questions Answered in This Episode

How could a much smaller startup practically adopt friction logging and “Walk the Store” without Stripe’s scale and resources?

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. ...

Get the full analysis with uListen AI

What trade-offs has Stripe made where meticulousness was intentionally *not* pursued, and how were those decisions made?

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. ...

Get the full analysis with uListen AI

How does Stripe prevent co-creating with power users from biasing the roadmap too much toward large, sophisticated customers at the expense of smaller ones?

Get the full analysis with uListen AI

What risks or failure modes has Stripe seen so far with AI tools like Copilot and internal LLM-based systems, and how are they mitigated?

Get the full analysis with uListen AI

If Stripe’s operating principles had to be reduced to just two for a new company, which would Singleton choose and why?

Get the full analysis with uListen AI

Transcript Preview

David Singleton

The way we think about product development at Stripe, it, it really is to find the correct set of early users to kind of co-create the product with. Maybe, uh, the best example of that is Stripe Billing. 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, um, who were already using Stripe for payments, but had these subscriptions business models. And we figured that there were gonna be many more of these kind of companies into the future and we, we could see that they, they were really kind of pushing the boundaries of what was possible here. So we decided to co-create the product with them. So we had shared Slack channels. We'd actually show them product on a very regular basis, get their feedback on it. And only when that original kind of alpha group was super, super happy with the product did we then think it might be ready to go to, to a broader audience. So that is just how we build product at Stripe. And that means that every engineer building product at Stripe really has many of the kind of attributes and will exercise many of the attributes that you'll often find in, in PMs in, in other companies.

Lenny Rachitsky

(instrumental music) Welcome to Lenny's Podcast, where I interview world-class product leaders and growth experts to learn from their hard-won experiences building and growing today's most successful products. Today my guest is David Singleton. David is chief technology officer at Stripe, where he's responsible for guiding its engineering and design teams, a role he's had for over five years. Prior to Stripe, David was VP of engineering at Google, where he spent over a decade. And in hearing from David, you'll quickly be able to tell how passionate he is about the craft of building great products and building great teams. We dig into Stripe's unique approach to hiring, how they built a very product-oriented engineering team which allowed them to hold off on hiring their first product manager for many, many years, how they operationalize their operating principle of be meticulous in your craft, including a number of fascinating internal processes like engineer occasions, walking the store, and something called friction logging. David also shares what it takes to run an engineering culture with the uptime and scale requirements of a Stripe, plus how AI is already impacting how they work and lessons around leadership, management, and planning. I am so thankful David carved out time to come on the podcast, and I know that you'll learn something valuable from it. With that, I bring you David Singleton after a short word from our sponsors. This episode is brought to you by Mixpanel, offering powerful self-serve product analytics. If you listen to this podcast, you know that it's really hard to build great product without making compromises. And when it comes to using data, a lot of teams think that they only have two choices: make quick decisions based on gut feelings or make data-driven decisions at a snail's pace. But that's a false choice. You shouldn't have to compromise on speed to get product answers that you can trust. With Mixpanel, there are no trade-offs. Get deep insights at the speed of thought at a fair price that scales as you grow. Mixpanel builds powerful and intuitive product analytics that everyone can trust, use, and afford. Explore plans for teams of every size and see what Mixpanel can do for you at mixpanel.com. And while you're at it, they're hiring. Check out mixpanel.com to learn more. This episode is brought to you by Eppo. Eppo is a next-generation A/B testing platform built by Airbnb alums for modern growth teams. Companies like DraftKings, Zapier, ClickUp, Twitch, and Cameo rely on Eppo to power their experiments. Wherever you work, running experiments is increasingly essential, but there are no commercial tools that integrate with a modern growth team stack. This leads to wasted time building internal tools or trying to run your own experiments through a clunky marketing tool. When I was at Airbnb, one of the things that I loved most about working there was our experimentation platform where I was able to slice and dice data by device types, country, user stage. Eppo does all that and more, delivering results quickly, avoiding annoying prolonged analytic cycles, and helping you easily get to the root cause of any issue you discover. Eppo lets you go beyond basic click-through metrics and instead use your North Star metrics like activation, retention, subscription, and payments. Eppo supports tests on the front end, on the back end, email marketing, even machine learning claims. Check out Eppo at GetEppo.com. That's GetEppo.com and 10X your experiment velocity. David, welcome to the podcast.

Install uListen to search the full transcript and get AI-powered insights

Get Full Transcript

Get more from every podcast

AI summaries, searchable transcripts, and fact-checking. Free forever.

Add to Chrome