Brian’s Notes If you’re an engineer

A tall potted plant holding a red watering can on one branch, watering a row of smaller seedlings

The best engineer in the room makes everyone better.

Every team has one. The engineer people quietly route the hard problems to. The one whose code reviews everybody actually reads, start to finish.

If that’s you, first: thank you. Teams run on people like you. Second: there’s a next level, and it isn’t more of the same.

What’s the next level?

Making the people around you better.

However good you are, there’s a limit to how much code you can write in a day and how many bugs you can fix in a week. Your own output has a ceiling. The output of the people you teach doesn’t.

You know the old line about fishing: give someone a fish and they eat today; teach them to fish and they eat for life. Teach a whole team, and you’ve changed what the team can build. Imagine you could clone the best engineer at your company. Mentoring is how you do it, a little at a time.

Why does that separate senior from staff?

Because the jobs are different. A senior engineer owns hard problems from start to finish. A staff engineer owns outcomes across teams, and nobody does that alone.

You do it by raising everyone you touch: the review that teaches instead of just correcting, the design doc that leaves the next person smarter, the newer engineer who’s suddenly shipping things she couldn’t have six months ago. That isn’t a soft skill bolted onto the technical ones. At that level, it is the technical work. (More on the levels in What “senior” actually means.)

What does good mentoring look like?

Mostly small things, done every day:

  • Explain the why, not just the fix.
  • Make reviews lessons. Ask a question before you rewrite someone’s code.
  • Hand over the interesting work, with a safety net under it.
  • Be safe to ask. The best mentors make the “dumb” question easy.
  • Cheer someone else’s win as loudly as your own.

None of it takes a title. You can start on your current team, this week.

It pays you back, too. Explaining something is the fastest way to find out whether you really understand it. And a team that can carry your work is the only way you ever get free to take on something bigger.

Will a hiring manager notice?

Expect the question in any interview for a senior seat: who have you helped grow? Have a real answer, with the people you’d be proud to mention and what they can do now that they couldn’t before.

It’s one of the most convincing things an engineer can say, because it’s so hard to fake. Anyone can describe a system. Not everyone can point to the people who got better because they were there.

The short version

  • Your own output has a ceiling. Your team’s doesn’t.
  • Mentoring is what separates senior from staff.
  • Teach the why, and make reviews lessons.
  • Hand over interesting work, with a safety net.
  • Have a real answer to “Who have you helped grow?”

The best engineer in the room is the one working hardest to make it a tie.

Looking for a seat where you’ll raise the whole team?

Talk to Brian

Say hello. Or just tell me where you’re headed.

You don’t have to be looking. Most of the people I’ve placed weren’t. Tell me what you’re working on and what would make you pick up, and I’ll keep you in mind for the right thing, not the next thing.

Brian MarianiI read these myself. Jonathan Soo Hoo, my partner at Mirror, does the first outreach on some searches; if you hear from him, that’s why.

No sequence, no platform. A person reads this. Questions first? Read the FAQ.