Picture the job description for your senior seat. Four pages. Twenty-two bullets under “Requirements,” a paragraph about the company’s values, and a line about a fast-paced environment.
I’ll read every word of it. Then I’ll ask you two questions, because the answers are almost never in there.
What are the two questions?
What does this person really do on day one? Not the list of skills. The work. What’s waiting for them the first morning? Which problem do they pick up first, and who do they pick it up with?
What’s keeping you up at night? The thing that made you open this seat. A launch that keeps slipping. A system that falls over every Friday. A team that grew faster than anyone could lead it.
Those two answers tell me more than most job descriptions do. They tell me who’ll love this seat, and who’d be miserable in it.
Why not just send the job description?
Because a job description is written for a pile. It has to cover every case and offend no one, so it ends up describing nobody.
The engineers I reach out to aren’t applying. They’re happy where they are, and I’m asking them to consider a change. “Fast-paced environment” won’t do it. “You’d own the payments rewrite, and the team needs someone who’s done one before” might.
Keep the description, by the way. It’s useful for HR and for the post. It just isn’t how a senior engineer decides.
Why only fifteen minutes?
Because that’s usually all it takes, if we spend it on the right things. Fifteen honest minutes beat an hour of reading. The more honest you are, the better I match.
The rest tends to come up on its own: the team, the stack, the range, where the person will work. If you know those already, wonderful. If you don’t yet, I’ll help you think them through.
How honest is honest?
Honest includes the hard parts. If the codebase is a mess, say so. If the seat is hard to fill, tell me why you think it is. The right engineer can handle almost anything except a surprise, and the hard parts are often exactly what makes the right person say yes.
What happens after the fifteen minutes?
I go to work. Within about 72 hours, you meet a small group, typically three to five engineers, each with a custom-written vignette and my honest take on why they fit. Not a stack of résumés. People who’ve already heard the hard parts and still want to talk.
That only works because of the fifteen minutes. The better I understand day one and the thing keeping you up at night, the better I know who to text, and who not to bother.
The short version
- Skip the job description. Bring two answers.
- What does this person really do on day one?
- What’s keeping you up at night?
- Tell me the hard parts. The right engineer can handle anything but a surprise.
Fifteen minutes, two questions and the truth. That’s how a good search starts.
Have fifteen minutes?
I 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.