Brian’s Notes How I work

An open notebook with handwritten notes and a short profile, a red pen, a laptop showing code, and a mug of coffee

How I vet an engineer.

What I ask, and what goes in the vignette.

A résumé tells you where someone sat. It doesn’t tell you what they did there, how hard it was, or whether they’d do it again for you.

So before I introduce anyone, we talk. Not an interview, exactly. More like two engineers comparing notes. I came out of a software agency and have spent twenty-five years inside engineering teams, so I can talk through someone’s work before you do.

What do I actually ask?

I go deep on something they built. Not the whole résumé, just one or two things they’re proud of. What was the hard part? What did they trade away to ship it? What would they do differently now?

You learn a lot from how someone answers. The engineer who did the work can take you three levels down without blinking: the decision, the reason, the thing that broke at two in the morning. And the answer to “what would you do differently?” says a great deal about how someone grows.

Why ask what they want next?

Because a great engineer in the wrong seat is a bad hire for everyone. I ask what they’d love to work on, and what would actually make them move. Not “are you open to opportunities,” but what would make them leave a job they like.

The answer saves everyone time. If someone’s heart is in infrastructure, I won’t send them to build your marketing site, however good they are. And if what would make them move is exactly what your seat offers, that’s the start of a good introduction.

Who else do I check with?

People who know their work. Often that’s someone I already know who has worked with them, one of the quiet benefits of doing this for a long time. And references, where I ask specific questions and listen closely to the answers.

What goes in the vignette?

Every engineer I introduce comes with a custom-written vignette, not just a résumé. It answers one question, in plain words: why this person, for this seat?

It isn’t a list of skills you could read off the résumé yourself. It’s the specific reason they fit. By the first interview, you’ll feel like you already know them.

What don’t I do?

I don’t send a pile. You’ll meet a small group of three to five, and I’ve talked with every one of them. And nobody’s name goes anywhere without their yes. (More on that in Nothing without your yes.)

The short version

  • I go deep on one or two things they built: the hard part, the trade-offs, what they’d change.
  • I ask what they want next, and what would make them move.
  • I check with people who know their work, and with references.
  • Every introduction comes with a custom-written vignette: why this person, for this seat.
  • You meet a small group of three to five, never a pile.

A résumé says where someone has been. My job is to tell you where they’d be great.

Hiring? Talk to Brian

An engineer? Say hello

Talk to Brian

Tell me what you need. I’ll think of someone.

Skip the formal job description. The more honest you are about the seat, the stack and the room, the faster a warm intro shows up. If I can help, great. If not, I’ll point you in the right direction.

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.

When do you need someone in the chair?

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