Hiring at a Startup
Hiring at a startup.
Most startups don't get into trouble because they hired the wrong number of people; they get into trouble because they hired the wrong people in the wrong order and moved too slowly to correct it, hoping the mistakes would quietly resolve themselves over time. They rarely do, and by the time the cost is obvious it has usually compounded into something far harder to unwind.
Over the past decade I've run hiring inside companies growing from a handful of people to several hundred, and the pattern holds regardless of stage or sector: the earliest hires quietly set the ceiling for everything that follows. What I've learned about getting those hires right is what the rest of this page is about.
Your first hires are the company.
When you're ten people, everyone you bring on meaningfully shifts the average of how the team works, what it tolerates, and who it goes on to attract, which means there is no separate culture layer waiting to be added once things settle down. The first fifteen or so hires simply are the culture, and they are already recruiting the next fifty in your image whether or not you've consciously asked them to.
That's why the bar for an early hire can't just be whether they can do the job in front of them. The more useful question is whether you'd want a team full of people like this one, because that is more or less what you're signing up for.
Hire to the next twelve months, not the org chart.
A startup doesn't have a stable organization to fill so much as a plan it's trying to execute, so the right opening question isn't which roles are technically open but what has to become true over the next year and who you actually need to make that happen. When you start there, the roles fall out of the plan naturally, and any headcount that isn't tied to a real outcome reveals itself as little more than burn.
It also means resisting the reflex to reach for the most senior name you can afford. A leader who looks impressive on the deck but is unwilling to get their hands dirty for the next twelve months tends to be the most expensive mistake an early team can make.
Speed is a feature, not a compromise.
The strongest candidates tend to be off the market in a matter of days rather than weeks, so a slow and indecisive process doesn't actually protect the quality of your hiring the way people like to believe. In practice it does the opposite, quietly filtering out everyone who had other options and leaving you to choose from the people who didn't.
Moving quickly isn't the same as lowering the bar. It means respecting a candidate's time, making decisions on genuine signal instead of an endless series of rounds, and closing while the enthusiasm is still real, because every additional week you spend deliberating is another week someone else spends closing the person you wanted.
You are always selling.
In the early days you're rarely the obvious choice, and it's worth being honest about that: you're a risky bet standing next to a name-brand offer with real compensation and real stability, and almost every strong candidate you want is being courted by somebody who looks safer on paper.
Recruiting at that stage is an exercise in persuasion rather than processing. It comes down to understanding what a particular person genuinely wants from the next chapter of their career and then showing them, honestly, whether this is the place to find it, and that is a conversation no tool will ever close on your behalf.
Build the engine before you're desperate.
The worst possible moment to work out how you hire is the quarter you suddenly need ten people, because by then you're reacting instead of choosing, drifting off-brand, and making rushed calls that you'll spend the following year quietly unwinding.
It helps to treat recruiting as infrastructure rather than an errand: sourcing workflows, a clear scorecard, an interview loop that is both fast and humane, and enough automation that the work can scale without the quality slipping. Putting that in place while it still feels a little early is the difference between hiring on your own terms and hiring under duress.
Quality of hire is the only number that matters.
Time-to-fill and pipeline volume are worth keeping an eye on, but they only ever matter in service of a single outcome, which is the right person in the right seat doing the work you actually hired them to do. That's the real scoreboard, and everything else is a leading indicator pointing toward it.
Get the early hires right and the whole company compounds off the back of them; get them wrong and no amount of process, tooling, or later heroics ever fully recovers what was lost. That's precisely why I do the hiring myself at this stage rather than hand it off, because it's simply too consequential to delegate.