Building The Function By Stage

A recruiting function breaks in predictable places

The recruiting function that works at fifty people is the wrong one at five hundred, and the failure is predictable enough to plan for. The mistakes that hurt most are made one stage too late: keeping founder-led hiring after it stops scaling, or adding recruiters without the operations to support them.

Around 50 people

Hiring is founder-led and mostly works on taste and network. The risk is that the founder’s standard lives only in the founder’s head. The job at this stage is to start writing the standard down (a simple scorecard, a consistent interview question set) so it can survive being handed off later.

Around 150 people

The founder can no longer touch every hire, and the first real recruiters come in. This is where founder taste has to become a shared decision model, or quality starts drifting the moment the founder steps back. The common error is delegating the function (handing off the process) without distributing the standard (making the rubric legible enough that others produce the same signal).

Around 500 people

Volume forces specialization. Sourcing and operations split out from full-cycle recruiting, and the function needs a real operating plan and reporting. The break here is adding bodies faster than the operating layer can hold them, so the team grows but velocity and quality don’t.

Around 1,500 people

The function is a system with its own internal services, and the leader’s job is mostly design and capacity allocation rather than individual reqs. The risk shifts to bureaucracy: process that was protective at 500 becomes drag at 1,500 if nobody is pruning it.

The throughline

At every stage the same thing determines success: whether the standard lives in the system or in a few people’s heads. That’s why I treat operations and bar protection as the spine of the whole function, not as back-office support.