Brian’s Notes If you’re an engineer

Three steps rising to the right with a compass on the top step, and a few old calendars leaning together, set aside

What “senior” actually means.

It isn’t years.

Picture two engineers, each with eight years of experience.

One has spent them owning hard problems. She’s built things, shipped them, watched them break, fixed them and explained what happened. The other has spent them doing exactly what was asked, very well.

On paper, they’re both senior. In a room, you can tell the difference in about ten minutes.

Isn’t senior just a number of years?

That was the old shortcut: so many years and you’re senior. It was never a good one. By that math, someone who did the same year ten times over is very senior indeed.

Years tell you how long someone has been around. They don’t tell you what that person can be trusted with. What makes you senior is scope, judgment and the problems you’ve owned.

So what does senior mean?

A senior engineer owns hard problems from start to finish.

Hand them something messy and half-defined, and they’ll figure out what it really is, build it, ship it, live with it, and leave it better than they found it. They don’t need the problem pre-chewed. They know when to ask for help, and they ask early.

And staff?

A staff engineer owns outcomes across teams.

Their problems don’t fit inside one team: a migration everyone has to make, reliability across a whole system, a platform other engineers build on. A lot of their work shows up in other people’s work. They write things down, bring people along and clear the way. Much of their value is the engineers they make better. (More on that in The best engineer in the room.)

And principal?

A principal engineer sets technical direction.

They decide what the organization will build on, and why. They look further ahead than anyone else in the room, make the calls other people’s work depends on, and say no more often than you’d expect.

Why don’t titles line up from company to company?

Because every company draws the lines differently. A senior engineer at a ten-person startup might own more than a staff engineer at a big company. Or less.

So when a job description says “senior,” I ask what the person in that seat will own. That’s the real level, whatever the title says.

It cuts the other way, too. A strong engineer from a different stack can step into a senior seat sooner than the years suggest. Many of the hiring managers I work with would rather have a sharp engineer who’s new to their tools than a long résumé without the judgment.

How do I show I’m senior?

Don’t recite your years. Show what you’ve owned:

  • Walk through a hard problem you owned from start to finish, including the parts that went wrong.
  • Explain the trade-offs you chose, and why you chose them.
  • Name the people you made better along the way.
  • Say what you’d do differently now. That’s judgment, and it’s what people listen for.

When I talk with an engineer, that’s where I go deep: the hard parts, the trade-offs, what they’d do differently. It tells me more than any résumé can.

The short version

  • Senior isn’t years. It’s scope, judgment and the problems you’ve owned.
  • Senior owns hard problems from start to finish.
  • Staff owns outcomes across teams.
  • Principal sets technical direction.
  • Titles vary by company, so ask what the seat will own.

Count what you’ve owned, not how long you’ve been there.

Wondering which level your next seat should be?

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.