The First Hire at a Startup Is Different From Every Hire After It

← All posts

The first person you hire at a startup does three jobs simultaneously: the job you described in the posting, a job nobody else is doing yet, and the job of deciding whether they trust you enough to stay when things get hard. Most founders optimize for the first and ignore the other two.

Operator founders make specific mistakes here. They bring corporate hiring instincts to a context where those instincts backfire — and the startup first hire is the place it shows up first.

What you're actually hiring for

At a 10-person company, every hire is a company-builder for a specific function. The first sales hire isn't going to execute a sales process — they're going to build one from scratch, with no infrastructure, under time pressure, with a product that's still changing under them.

The question that matters isn't "can this person do the job?" It's "can this person build the function?" Those are different things. A great account executive at a company with a mature CRM, defined territory structure, and clear ICP can be a weak first sales hire at a startup where none of that exists. The skill of selling is not the same as the skill of figuring out how to sell something that's never been sold at scale before.

Operator founders make this mistake because their hiring instincts come from companies with defined processes. When a process exists, you hire people who execute it well. When a process doesn't exist, you hire people who build one from observation and judgment — and those are different candidate profiles.

Equity and compensation math

Early startup hires accept below-market cash in exchange for equity that might become meaningful later. Most first-time founders price this badly — either too generous on cash (unsustainable burn) or too stingy on equity (a cap table problem that surfaces at the series A).

Market benchmarks for non-founding early employees:

  • First five hires: 0.5–1.5% for a senior individual contributor, four-year vest with one-year cliff
  • Employees six through fifteen: 0.1–0.5%, depending on seniority and funding stage

These ranges move with your last valuation and how much below-market cash you're paying. If you're paying 80% of market rate, equity should be toward the top of the band. If you're paying 60%, you're asking for a bigger bet from the employee and the equity should reflect it.

One mistake operator founders make: offering no equity for early hires because the company is too early to know what it's worth. That reasoning is accurate, but it signals something problematic — that the founder isn't willing to share upside with the people building the company. The best early-stage candidates know what startup equity is and what it could be worth. Offering nothing filters out exactly who you want to hire. Our breakdown of how to think about equity splits covers the mechanics in more detail.

The best early-stage candidates are evaluating whether you're willing to share the outcome with them. Zero equity isn't frugal. It's a filter against the people who build rather than execute.

Defining the 90-day bar

Most companies have a 90-day probationary period on paper. Most founders don't actively use it as a decision point.

The ones who use it well define — before the first day — what success looks like at day 90. Not "good culture fit" or "seems to be settling in." Specific outcomes. For a first engineering hire: shipped three features to production and capable of running the next sprint independently. For a first sales hire: made 50 outbound contacts, completed 10 demos, and has a formed view on why the first 10 prospects responded the way they did.

That standard sounds demanding. It is. Early-stage startups can't absorb a six-month hiring mistake. The cost isn't just salary — it's every decision that person influenced, every hire they might have made, every customer relationship they touched. The 90-day standard exists to make the decision point explicit rather than letting an underperforming hire linger because the moment of clarity never came.

When to make the startup first hire

The right time to make your first hire is when there's work you genuinely can't do — not work you dislike, not work that feels beneath your time, but work that requires skills you don't have and that's blocking the company's next step.

That sounds obvious. The non-obvious version: most things you think require a hire can be done longer as a founder than you'd expect. Customer calls, investor updates, financial modeling, first-draft copy — these feel like they should be delegated, but founders who do them personally learn things that are hard to recover if handed off too early. The feedback loops that come from direct execution calibrate every other decision.

The right first hire goes toward the function where the company's next unlock sits — and where the required skills genuinely aren't present on the founding team. Not the function the founder likes least. The function that's actually blocking progress.

Operator founders who've managed teams for years sometimes hire too quickly because managing people feels familiar and building from scratch feels uncomfortable. Sit with the discomfort a little longer than feels right. The hires that matter most are the ones you're sure about.

If you're building a team around a product thesis and want a partner who thinks through the structure early, here's how Alder works with operators.

Related reading

Building the team? Get the structure right early.

Describe the vertical and where you are. We'll talk through what the founding team needs to look like.

Pitch us