The engineer who taught engineers how to lead.
CTO at Imprint. Author of four books. Publisher of Irrational Exuberance since 2007. The person your skip-level probably quotes in 1:1s without mentioning where they got it.
There is a certain irony in the fact that Will Larson, whose career is built on writing things down, once lost his ability to write entirely. It happened at Digg, where the demands of a struggling company ground his prose to dust. He recovered it slowly, deliberately, at Stripe - and then wrote a book. Then another. Then two more.
That is who Will Larson is: someone who processes the world through the act of articulation. His blog, Irrational Exuberance, has run continuously since 2007. Engineering leadership, hiring, technical debt, organizational design - nearly two decades of posts, frameworks, and hard-won observations from inside some of tech's most consequential companies.
The career itself reads like a deliberate map of modern tech infrastructure. Yahoo!, then Digg (where he was Director of Engineering during its turbulent decline). Then Uber, where he grew the Platform Engineering team from five people to seventy in under two years. Then Stripe, where he founded the Foundation Engineering organization from scratch. Then three CTO roles - Calm, Carta, and now Imprint, the fintech startup where he landed in June 2025.
The books came because a gap existed. An Elegant Puzzle (2019, Stripe Press) addressed what no one had quite named before: the specific, unglamorous work of engineering management. Sizing teams. Managing technical debt. Succession planning. The things that actually break organizations. It sold thirty thousand copies. So did Staff Engineer (2021), which tackled the question lurking behind every IC's annual review: how do you grow without becoming a manager?
The answer, per Larson, is through four archetypes: Tech Lead, Architect, Solver, Right Hand. He built an entire companion site - staffeng.com - with interviews from staff engineers at leading companies. The book became required reading. Then came The Engineering Executive's Primer (2024, O'Reilly) and Crafting Engineering Strategy (November 2025, O'Reilly) - the latter including Wardley maps, systems models, and thirty-five-plus chapters drawing on case studies from Stripe, Uber, and Calm.
What makes these books stick is not that they are comprehensive. It is that they are honest. Larson writes like someone who has made the mistakes, measured the damage, and built a better heuristic. He doesn't promise easy. He gives you frameworks for thinking through hard.
Before any of this, Will Larson spent a year teaching English in rural Japan through the JET Program. He returned, studied computer science at Centre College in Kentucky, and moved to San Francisco in 2009 - the year everyone seemed to be moving to San Francisco. In 2008, between the two, he co-founded Monocle Studios with a friend and made a mobile game called touchDefense for iOS. He calls it a total disaster. Also formative.
The throughline is systems thinking. Larson approaches organizations the way good engineers approach architecture: identify the constraints, name the tradeoffs, document the decisions, iterate. His handle everywhere is lethain - GitHub, Twitter/X, Mastodon, the URL of his blog. Consistent identity across eighteen years of online presence. A man who figured out who he was on the internet and stayed there.
He is not a hot-take merchant. He doesn't traffic in controversy for clicks. He writes long, careful posts about things like headcount planning and engineering strategy, and a few thousand senior engineers read every one of them. That is a harder audience to hold than a general one, and he holds it by being genuinely useful.
Currently, he is building Imprint's engineering organization in fintech, writing on GitHub about MCP servers and AI tooling for knowledge bases, and - you can be reasonably certain - drafting the post that will document what he learned from all of it. That is just what Will Larson does.
The book that named what engineering managers actually do. Team sizing, technical debt, succession planning. Thirty thousand copies sold. Still referenced in every serious eng leader's toolkit.
Four archetypes. Thirteen interviews. One answer to the question every senior IC is quietly asking: how do I grow without becoming a manager? Built staffeng.com alongside it.
For leaders making the move from manager to executive. Headcount planning, cross-org communication, technology strategy. Written for people who've graduated from individual playbooks.
Thirty-five-plus chapters. Wardley maps. Systems models. Case studies from Stripe, Uber, and Calm. Plus an AI Companion for LLM collaboration. His most ambitious work yet.
Fear of micromanaging has created a culture of under-managing.
Managing is an ethical and moral profession. Managers have to make ethical decisions in regards to deciding who gets promoted, fired, given a raise.
A good piece of written communication is the most effective means of broadcasting ideas and scaling yourself.
Give everyone an explicit area of ownership that they are responsible for. Reward and status should derive from finishing high-quality work.
Metrics keep you honest.
If you just write things down, no matter how bad they are, your strategy will improve almost overnight.
Spent a year teaching English in rural Japan through the JET Program - before any of the engineering leadership career happened.
His first startup made a game called touchDefense for iOS in 2008. He calls it a total disaster. He also calls it formative. Both are true.
His handle is 'lethain' everywhere - GitHub, Twitter/X, Mastodon, and his blog URL. Eighteen years of consistent identity across the whole internet.
Irrational Exuberance launched in 2007. That predates the iPhone, Twitter going mainstream, and modern cloud computing as we know it.
Grew Uber's platform engineering from five engineers to seventy in under two years. That's not linear scaling. That's a small organization becoming a real one.
Recently building MCP servers on GitHub to navigate Markdown knowledge bases - actively experimenting with the same AI tools he's thinking about strategically.