Brian’s Notes If you’re hiring

Two empty office chairs face each other across a small table, where a magnifying glass looks closely at a little model of a company's office building

They’re interviewing you, too.

What senior engineers check before they say yes.

When I reach out to a senior engineer about a seat, I don’t get to start with my pitch. I get questions. Good ones, fast, before they’ll agree to a single conversation.

It’s worth knowing what they ask, because those questions decide whether your seat gets a hearing at all.

What do they ask first?

Four things.

The pay range, and whether it’s remote. Senior engineers have no patience for a mystery salary, and they want to know where they’d work: at home, in an office or some mix. If the range isn’t settled, settle it before the search starts.

The runway. How the company is funded, and how long the money lasts. They’ve watched good companies run out of time. They’ll ask about revenue, the last raise and when you’ll need the next one. Founders who answer plainly earn a lot of trust.

The real work. What’s the actual problem? What’s the stack? And, more and more often: is the AI work real? Engineers can tell the difference between AI work and AI words, and they ask.

Who they’d work with. The boss and the team. Who’s great? Who just left, and why? People don’t quit jobs nearly as often as they quit bosses, and senior engineers know it. (I give engineers the same advice in Interview them back.)

Why should a hiring manager care?

Because a senior engineer decides about you long before your first interview. If the answers are vague, the call never happens, and you never find out why.

The engineers worth hiring have options. They’re choosing where to spend their next few years, and they ask hard questions because they intend to stay. That’s exactly the kind of person you want asking.

How do I get ready for those questions?

  • Write down the range, and where the person will work.
  • Know your runway, and say it plainly. Nobody expects a startup to be risk-free. They expect you to be honest about the risk.
  • Describe the real work: the problem, the stack, and what the AI actually does, if there is any.
  • Let them meet the team, including the boss. If someone just left, say so, and say why.

What if I can’t answer one yet?

Say so. Sometimes the honest answer is “we don’t know yet.” The raise isn’t closed, or the team is still forming, or the range depends on who you find. “We’re closing our next round, and here’s the plan if it slips” is an answer an engineer can work with. Spin isn’t, and senior engineers have heard plenty of it.

Honesty about the unknowns is its own kind of answer. It tells them what it will be like when things get hard, and that’s what they’re really asking.

When I introduce an engineer, these answers travel with the seat. So the people I bring you have already heard the hard parts, and they still want to talk.

The short version

  • Senior engineers interview you before they’ll talk with you.
  • They ask about the pay range and remote, the runway, the real work and the people.
  • Have honest answers ready before the search starts.
  • Vague answers don’t get a no. They get silence.

The best engineers are choosing, too. Make it easy to choose you.

Want to know how your seat sounds to a senior engineer?

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.