
What I Look For When Evaluating a New Role
7 min read
After several career moves, I've developed a framework for evaluating new roles that goes beyond compensation and title. Here's what actually matters for long-term career satisfaction.
12 posts

7 min read
After several career moves, I've developed a framework for evaluating new roles that goes beyond compensation and title. Here's what actually matters for long-term career satisfaction.

6 min read
1-on-1s are the most underutilized meeting on most engineers' calendars. Here's how I turned them from status updates into the most valuable 30 minutes of my week.

5 min read
The ability to explain technical decisions in terms that non-engineers care about is one of the most valuable skills a senior engineer can develop.

4 min read
Design reviews aren't just for designers. As an engineer who regularly participates in them, I've gained perspectives that make me better at building products.

4 min read
The engineer-PM relationship is one of the most important dynamics on any product team. Here's how I've learned to make it productive instead of adversarial.

4 min read
Production incidents are inevitable. How you handle them defines your growth as an engineer. Here's what I learned from my first major one.

5 min read
The transition from feature engineer to system owner is the biggest career leap most engineers make. Here's what changed for me and what I wish I'd known earlier.

4 min read
Senior engineering isn't about writing more code or knowing more frameworks. It's about making the people and systems around you more effective.

5 min read
Tech debt isn't inherently bad. It's a tool. The problem is when teams accumulate it unconsciously, without tracking it or paying it down strategically.

4 min read
Speed and quality aren't always at odds. But when they are, knowing which one to optimize for is one of the most important judgment calls an engineer can make.

4 min read
Joining a new team means inheriting a codebase you didn't build. Here's the system I use to get productive fast without pretending to understand things I don't.

5 min read
I didn't start writing because I had all the answers. I started because writing forced me to figure out what I actually knew, and what I was just pretending to know.