Hire number one set that bar. Everyone who followed had to clear it.
The first hires are not a requisition list
Most companies never hire a sixtieth engineer. Many never need a twentieth — and nothing in this paper requires them to. The lesson of the engagement it draws on — a founding team built to close to sixty over more than a decade — applies just as fully to a company that stops at twelve: the first hires are not seats to fill. They are the people who set the technical culture, define the standard every later hire is measured against, and quietly set the ceiling on what the company can build.
That makes the first hires a different job from recruiting-as-volume, which optimizes for filling seats: postings, applicant flow, screens, throughput. A founding-stage team has no slack for that — each person is a large percentage of the whole organization, with no management layer to absorb mistakes. Hire a merely adequate engineer at number eight and you have not made one weak hire; you have lowered the bar that hires nine and beyond will be calibrated to, because the interviewers learned what “good” looks like from the people already in the room.
The alternative — define each hire precisely before sourcing, present small slates of exactly-right people, spend the founder's time up front in calibration — is slower at the front and faster everywhere else. We lived it end to end.
Get the full paper
The complete paper — the rest of the argument, the working detail, and the record — as a PDF.
Hiring for a role like the ones in this paper?
Start with the question we open every search with: if we're successful a year from now, what are we talking about that really worked out well — with the candidate we place?