Brian’s Notes If you’re hiring

A paper airplane with a red seal flies up and away from a calendar with a rising run of filled-in days, beside a stopwatch

Keep the momentum.

Where good hiring processes stall.

The first conversation went great. Your engineer liked the team, the team liked her, and everyone agreed on next steps. That was nine days ago. The next round still isn’t on the calendar.

Most good searches don’t die at the offer. They die in the gaps between steps, quietly, while everyone’s busy with something else.

Where do hiring processes stall?

In my experience, two places, over and over.

  • Scheduling the next round. Four calendars, one final interviewer who’s traveling, and a week disappears. Nobody decided to slow down. It just happened.
  • Responsiveness, in general. An email that sits for three days. Feedback that shows up a week after the interview. A question about the offer that waits on someone’s vacation. Each delay is small. Together they say something you never meant to say.

What does the engineer hear in the silence?

The same doubts you’d have in her place. Are they still interested? Did I say something wrong? Are they talking to someone better?

Meanwhile, the strong engineers are talking with other companies, too, and some of those companies call back the same day. I wrote the engineer’s side of this in Didn’t get the offer?: a great first interview, then a slow reply, and a good match fades. It cuts both ways.

How do I keep it moving?

  • Book the next step before this one ends. Leave the first interview with the second already on the calendar.
  • Hold time for it. While a search is open, ask your interviewers to keep a few slots free each week.
  • Answer within a day. Even when the real answer is “we’ll know Thursday.” A quick holding reply beats a perfect one next week.
  • Give feedback while it’s fresh. A few honest lines the day of the interview, so the next step can happen.
  • Name one owner. One person whose job is to make sure the next step happens. On a small team, that’s usually the hiring manager.

If you’re working with me, I’ll nudge. But the searches that go best are the ones where the company sets the pace.

What does a quick process tell the engineer?

More than you’d think. Every quick reply says something about what it’s like to work with you: decisions get made here, people follow through, nobody’s left wondering. That’s a message no job post can send, and the engineer hears it before you’ve said a word about the role.

A slow process says something, too, and it’s rarely what’s true. Most slow companies aren’t uninterested or disorganized. They’re just busy. The engineer can’t see that from the outside.

Isn’t moving fast risky?

Fast doesn’t mean rushed. Take all the time you need to decide well. Just don’t spend it waiting for a calendar slot. The care belongs in the conversations, not in the gaps between them.

The short version

  • Searches stall between steps, not at the offer.
  • The usual culprits: scheduling the next round, and slow replies in general.
  • Book the next step before this one ends, and answer within a day.
  • Give one person the job of keeping it moving.

Good engineers rarely say no to a great process. They just stop waiting for a slow one.

Have a search that’s lost its momentum?

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.