Brian’s Notes How I work

A desk phone left quiet, and a personal phone showing a text message and a reply at home in the evening, with a lamp on and the moon in the window

I don’t interrupt.

How I reach out, and why you can answer on your own time.

Here’s a promise I’ve kept for a long time: I don’t cold-call engineers. Not at work, not at home, not ever. And the modern version of the cold call, the “Got five minutes for a quick chat?” with no hint of what it’s about, I don’t do that either.

It started as a reaction to one of the oldest habits in recruiting: find an engineer’s work number and pitch the next job while the current boss sits ten feet away. Desk phones are mostly gone now. The habit isn’t. It just moved to a Slack ping, a LinkedIn message asking to “hop on a call today,” or a voicemail that says nothing except “call me back.”

What’s wrong with a quick call?

Think about when it lands. You’re in the middle of something good. Maybe your team is in the thread with you. You can’t talk freely, you can’t think it over, and you’re being asked about your next job on your current employer’s time, by someone who hasn’t yet told you what the job is. Serious people don’t want that conversation on demand, and most engineers I know are serious people.

A call also asks for the most expensive thing you have, your attention, before earning it. I’d rather earn it first.

So how do I reach out?

With a message you can read whenever you like, by text or email, on your own time. The first one names the company and the salary range, describes the seat, and says why I thought of you in particular. Not a keyword from your profile. Something you actually built.

If it’s not for you, a one-word reply is plenty, and I mean that. If you’re curious, we’ll find a time to talk that works for you. When we do get on the phone, it’s because you said yes to the call. That’s the only kind of call I make.

And nothing about you goes anywhere until you say so. That’s a separate promise, with a note of its own.

Why does that matter?

Because the whole relationship starts there. If the first thing a recruiter does is put you on the spot, it’s hard to trust what comes next. If the first thing they do is respect your time, tell you the company, and wait, you can judge everything else on its merits.

It’s also just better recruiting. The engineers I want to talk to are busy doing good work. The way to reach them isn’t to interrupt the work. It’s to be worth a minute when the work is done.

The short version

  • No cold calls, and no “quick call?” before you know what it’s about.
  • The first message names the company and the range, and says why you.
  • Read it on your own time. Answer in a word if that’s all it needs.
  • We talk on the phone when you’ve said yes to talking.

I think that’s a big part of why so many engineers answer when I text. They know it’ll be worth reading, and that it can wait until they’re ready. (If you’re wondering how to tell a message like that from the other kind, there’s a note for that too: When to answer a recruiter.)

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.