Blogs / Personal blogs

Will Larson

lethain.com

Hey folks, I’m Will Larson! I wrote An Elegant Puzzle, Staff Engineer, The Engineering Executive’s Primer, and Crafting Engineering Strategy. You might also be interested in my collection of popular blog posts over the years, or to read my writing as it’s published via my newsletter or my RSS feed.

Popular posts
25
Total points
4,823
HN comments
2,445
Rank
#234 personal

Visit lethain.com → RSS feedOn Hacker News Apr 2009 – Nov 2025

Career & Management 22Tech Industry & Business 10Software Engineering 5Systems & Performance 3Web & Frontend 1Life, Learning & Writing 1

1

Staff Engineer Archetypes (2020)

Most career ladders define a single, uniform set of expectations for Staff Engineers. These career ladders attempt to identify the commonalities across many folks performing similar roles in their organization, but in the end these ladders are a tool that apply better against populations than people. In the case of…

2

Hard to work with

Managing teams has taught me a lot about my own behaviors and motivations. For example, I overworked for a long time. This left me continually teetering on the brink of burnout, and I had no energy left to absorb the typical sorts of organizational changes that happen at any company. Despite doing good work, I handled…

3

Career Advice in 2025

Yesterday, the tj-actions repository, a popular tool used with Github Actions was compromised (for more background read one of these two articles). Watching the infrastructure and security engineering teams at Carta respond, it highlighted to me just how much LLMs can’t meaningfully replace many essential roles of…

4

Writing an engineering strategy

Once you become an engineering executive, an invisible timer starts ticking in the background. Tick tick tick. At some point that timer will go off, at which point someone will rush up to you demanding an engineering strategy. It won’t be clear what they mean, but they will want it, really, really badly. If we just…

5

Downturn career decisions

When I joined Yahoo in 2008, I received a small number of options. I don’t remember how many–it was very few–but I do know my strike price was roughly $16. I don’t remember that because my strike price was particularly lucrative, but rather because some of my coworkers would complain about their underwater strike…

6

How to present to executives (2021)

Have you presented to company executives about a key engineering initiative, walking into the room excited and leaving defeated? Maybe you only made it to your second slide before unrelated questions derailed the discussion. Maybe you worked through your entire presentation only to have folks say, “Great job,” and…

7

Build versus Buy

A few years ago I was working on a contract negotiation with Splunk, and we kept running into what felt like a pretty unreasonable pricing structure. They wanted some number of millions of dollars for a three year license, which felt like a high price to pay for roughly thirty-two ascii characters in a particular…

9

Founding Uber SRE

This is my personal story of starting the SRE organization at Uber. If you want advice rather than reminiscence, take a look at Trunk and Branches Model and Productivity in the age of hypergrowth. After I left SocialCode in 2014, I spent a month interviewing at a handful of companies trying to figure out what to do…

10

"Good engineering management" is a fad

As I get older, I increasingly think about whether I’m spending my time the right way to advance my career and my life. This is also a question that your company asks about you every performance cycle: is this engineering manager spending their time effectively to advance the company or their organization?…

11

Some career advice (2019)

One unexpected perk of publishing a book is that folks start to ask you questions about all sorts of loosely related things. One pretty common thread has been around career advice, I’ve written up most of my advice for easier reusability. Some of the ideas are a bit contradictory, which I suspect is the nature of all…

12

How to Safely Think in Systems

While there are a decent number of folks out there modeling systems, there’s a much larger group of folks who think of themselves as systems thinkers but utilize techniques like modeling rather casually (a polite way of saying that they don’t use them). Even with modeling tools available, I’ve often taken the shortcut…

13

How the Digg team was acquihired

About a year after the catastrophic Digg V4 launch, our last-ditch experiment to salvage the site showed a spark of hope. We’d cajoled our way into a Facebook beta that allowed us to publish each Digg users’s read articles into their Facebook newsfeed, sending every clicking friend directly to Digg’s permalink page…

14

A Forty Year Career

The Silicon Valley narrative centers on entrepreneurial protagonists who are poised one predestined step away from changing the world. A decade ago they were heroes, and more recently they’ve become villains, but either way they are absolutely the protagonists. Working within the industry, I’ve worked with quite a few…

15

One-on-ones with executives

Often when an organization is going through some turmoil, executives think to themselves, “Ah, I should have some one-on-ones with the team so they can hear how we’re handling this.” On the other side, I frequently hear from folks who get nervous when they get these meeting invites, “The CEO/CTO/CPO/etc just scheduled…

16

Measuring an engineering organization

For the past several years, I’ve run a learning circle with engineering executives. The most frequent topic that comes up is career management–what should I do next? The second most frequent topic is measuring engineering teams and organizations–my CEO has asked me to report monthly engineering metrics, what should I…

17

Reminiscing: The retreat to comforting work

In Work on what matters, I wrote about Hunter Walk’s idea of snacking: doing work that is easy to complete but low impact. The best story of my own snacking behaviors comes from my time at Stripe. I was focused on revamping the engineering organization’s approach to operating reliable software, and decided that it…

19

Better to micromanage than be disengaged

For a long time, I found the micromanager CEO archetype very frustrating to work with. They would often pop out of nowhere, jab holes in the work I had done without understanding the tradeoffs, and then disappear when I wanted to explain my decisions. In those moments, I wished they would trust me based on my track…

21

Company, Team, Self

Back when I was managing at Uber, I latched onto a thinking tool that I drilled into the teams I worked with: reach the right outcomes by prioritizing the company first, your team second, and yourself third. This company/team/self framework proved itself a helpful decision-making tool, and almost always led to the…

23

Building personal and organizational prestige

Most months I get at least one email from an engineering leader who believes they’d be a candidate for significantly more desirable roles if their personal brand were just better known. Similarly, when funding is readily available during periods of tech industry expansion, many companies believe they are principally…

24

Managing Technical Quality in a Codebase

If there’s one thing that engineers, engineering managers, and technology executives are likely to agree on, it’s that there’s a crisis of technical quality. One diagnosis and cure is easy to identify: our engineers aren’t prioritizing quality, and we need to hire better engineers or retrain the ones we have. Of…