Skip to content
Lenny's PodcastLenny's Podcast

The engineering mindset | Will Larson (Carta, Stripe, Uber, Calm, Digg)

Will Larson is the chief technology officer at Carta. Prior to joining Carta, he was the CTO at Calm and held engineering leadership roles at Stripe, Uber, and Digg. He is the author of two foundational engineering career books, An Elegant Puzzle and Staff Engineer, and The Engineering Executive’s Primer, which will be released in February of next year. In our conversation, we discuss: • Systems thinking: what it is and how to apply it • Advice for product managers on fostering productive relationships with engineering managers • Why companies should treat engineers like adults • How to best measure developer productivity • Writing and its impact on his career • How to balance writing with a demanding job • How to develop your company values — Brought to you by DX—A platform for measuring and improving developer productivity: https://getdx.com/lenny | OneSchema—Import CSV data 10x faster: https://oneschema.co/lenny | Vanta—Automate compliance. Simplify security: https://vanta.com/lenny Find the transcript and references at: https://www.lennysnewsletter.com/p/the-engineering-mindset-will-larson Where to find Will Larson: • X: https://twitter.com/Lethain • LinkedIn: https://www.linkedin.com/in/will-larson-a44b543/ • Website: https://lethain.com/ Where to find Lenny: • Newsletter: https://www.lennysnewsletter.com • X: https://twitter.com/lennysan • LinkedIn: https://www.linkedin.com/in/lennyrachitsky/ In this episode, we cover: (00:00) Will’s background (04:12) Changes in the field of engineering (06:27) We need to stop treating engineers like children (08:32) Systems thinking (13:23) Implementing systems thinking in hiring (16:32) Engineering strategy (20:21) Examples of engineering strategies (25:08) How to get good at strategy (26:48) The importance of writing about things that excite you (32:40) The biggest risk to content creation is quitting too soon (35:24) How to make time for writing (37:41) Tips for aspiring writers (41:18) Building productive relationships between product managers and engineers (43:45) Giving the same performance rating to EMs and PMs (48:24) Measuring engineering productivity (55:53) Defining company values (01:02:10) Failure corner: the Digg rewrite (01:11:05) Will’s upcoming book, The Engineering Executive’s Primer (01:12:04) Lightning round 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.

Will LarsonguestLenny Rachitskyhost
Jan 6, 20241h 16mWatch on YouTube ↗

At a glance

WHAT IT’S REALLY ABOUT

Will Larson on engineering strategy, accountability, and sustainable writing careers

  1. CTO Will Larson discusses how the engineering landscape has shifted from hypergrowth and coddling engineers to a more accountable, constraints-driven environment. He explains systems thinking, practical engineering strategy, and how to build healthier EM–PM partnerships with aligned incentives. Larson also shares his approach to writing prolifically while working intense leadership roles, the importance of honest, applicable company values, and lessons from high‑stakes failures like Digg’s disastrous rewrite. Throughout, he emphasizes treating engineers as peers, embracing constraints, and focusing on long-term learning over short-term optics.

IDEAS WORTH REMEMBERING

5 ideas

Stop coddling engineers; give them real accountability and leadership opportunities.

Larson argues that over-optimizing for retention led companies to shield engineers from hard problems, which stunted growth and limited senior IC roles; today’s environment allows holding engineers accountable and putting them into true senior leadership positions.

Use systems thinking to diagnose, not to deny reality.

By modeling stocks and flows (e.g., hiring pipelines, incident processes), you can see where a system is breaking down, but Larson stresses that when your model conflicts with reality, reality is right—your model is what needs updating.

Good engineering strategy is often boring, constraint-heavy, and written down.

Effective strategies look like “we only use our standard tech stack” or “no cloud, only our own data centers”; these constraints focus scarce engineering capacity on what the business actually values and enable faster, more coherent execution.

Align EM–PM incentives, ideally via shared performance ratings.

Many EM–PM conflicts stem from misaligned incentives and unspoken needs; tying their performance reviews together forces them to own outcomes jointly and pushes both to solve for company goals, not just functional metrics.

Measure engineering productivity imperfectly, then use metrics to educate.

Larson recommends starting with DORA-style metrics and basic benchmarks even though they’re flawed, using them for diagnosis and board communication, and layering in qualitative input from engineers who usually know where the real bottlenecks are.

WORDS WORTH SAVING

5 quotes

We often treat engineers a little bit like children instead of giving them the responsibilities and ability to actually thrive as adults.

Will Larson

Reality is never wrong. Reality is always right. Your model is always wrong if it's in conflict with reality.

Will Larson

The goal of good strategy is not to appease everyone. The goal of good strategy is to dictate how we invest the limited capacities we have into the problems we care about.

Will Larson

The biggest risk to content creation of any sort is quitting soon because you get burned out. The biggest risk is not that you grow too slow initially.

Will Larson

Values have to be honest and applicable. If everyone can say them and no one would ever choose the opposite, they’re not helping you make decisions.

Will Larson

Shifts in the engineering landscape post‑ZIRP (hiring slowdown, accountability, team cuts)Treating engineers as accountable adults and enabling senior technical leadershipSystems thinking: stocks, flows, and practical applications (e.g., hiring funnels, incidents)Engineering strategy: constraints, boring but powerful policies, and Rumelt’s frameworkWriting as an engineering leader: process, motivation, and career impactImproving PM–EM relationships and aligning incentives (shared performance evaluations)Measuring engineering productivity (DORA metrics, qualitative diagnosis, and realistic reporting)Designing honest, reversible, and applicable company valuesFailure lessons from Digg V4 and career growth through crisis experiences

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