First Hire

RR
Ryan Rutan

First Hire

The first hire is the first non-founder employee of a startup, typically receiving outsized equity and disproportionately shaping company culture and trajectory. Equity often lands in the 0.5-3% range depending on role and stage, dramatically more than later equivalent-level hires. The first hire sets the tone for company culture because they become the cultural template for everyone hired after. At small team sizes, each person represents an enormous percentage of total capacity, so the role is usually a functional generalist (the first hire typically wears multiple hats) and personality fit often matters more than narrow skill fit. It is the highest-stakes hiring decision most startups make and the one that founders most often get wrong because they hire for narrow skill rather than for the broader needs of an early-stage company.

The principles that should guide first-hire decisions:

Hire for the gap, not the function:

  • Identify what the founders cannot or should not do. The first hire fills that gap.
  • For technical-founder pairs, the first hire often is the first sales or operations hire (the gap is non-technical).
  • For non-technical founders without a technical cofounder, the first hire is often the senior engineer who will effectively become the technical cofounder.
  • Don't hire the second of something the founders already do well; hire the first of something missing.

Hire generalists, not specialists:

  • The first hire will do many things. A narrow specialist (e.g., "senior frontend engineer") is often less valuable than a capable generalist (e.g., "senior full-stack engineer who can also do DevOps and customer support").
  • The job description should be wide. Expect the first hire to absorb 3-5 functions.

Hire for culture trajectory, not current culture:

  • The first hire establishes the cultural template. They're not joining an existing culture; they're co-creating it.
  • Hire someone whose values and operating style match what you want the company to be at 100 employees, not what's comfortable now.
  • The first hire often "doubles" the culture: their habits become the company's habits.

Pay attention to commitment level:

  • The first hire takes nearly founder-level risk (small startup, equity-heavy comp, no infrastructure, founder-level chaos).
  • Their commitment to the mission and willingness to operate in early-stage conditions matters more than their resume.
  • Test commitment through process (trial periods, projects, multiple deep conversations) before extending offers.

The equity math for first hires:

  • Typical first-hire equity at venture-backed startups: 0.5-3% of fully diluted, depending on role criticality and company stage.
  • Senior engineering first hire post-funding: often 1-3%.
  • Senior business first hire post-funding: often 0.5-2%.
  • Pre-funding first hires sometimes get higher equity (3-5%) reflecting higher risk and lower cash compensation.

Concrete example: A two-technical-cofounder pre-seed SaaS company is hiring their first sales-side employee. The "first hire" decision is whether to hire (a) an entry-level SDR (cheap, narrow skill), (b) a sales-focused founder who'll close the first 50 customers, run customer development, and partner with founders on go-to-market (mid-level salary, 1-2% equity, broad scope), or (c) a senior VP Sales (expensive, established, may be overqualified for the stage). The right answer is almost always (b): a sales-capable generalist with founder-level commitment, broad scope, and 1-2% equity. Hiring (a) or (c) is the common mistake.

Ryan's Take

First hire is the most important hire most startups make and the one founders most often get wrong. The two failure modes: (1) hiring someone narrow when you needed a generalist (you wanted "a great engineer" and got someone who can only do frontend work; you needed someone who could do engineering, deploy infrastructure, and respond to customer support tickets all in week one); (2) hiring for the resume rather than for the early-stage chaos (you hired a senior VP from a large company who immediately wanted process and headcount you don't have). The right discipline: write down what the first six months actually require (the real list of work that will need to happen), find someone who can do most of that list, and evaluate their willingness to operate in early-stage chaos as much as their narrow skill. The first hire often becomes a long-term key employee or even a cofounder-equivalent; spend the time to get it right.

What founders get wrong: Hiring narrow specialists when they needed generalists, or hiring senior people from larger companies who can't operate in early-stage conditions. The right discipline: write a list of the actual work that will need to happen in the next six months, look for someone who can credibly do most of that list, and evaluate their willingness to operate in chaos as much as their narrow skill. Pay generously in equity to compensate for the risk and chaos; the first hire typically deserves significantly more equity than later equivalent-level hires.

Related: Employee Zero · Co-founder · Hiring Plan · Company Culture · Founder

FAQ

What is the first hire at a startup?
The first non-founder employee of a startup. Typically receives outsized equity (often 0.5-3% of the company), sets the tone for company culture, and disproportionately shapes the company's trajectory because at small team sizes each person represents an enormous percentage of total capacity.

How much equity should a first hire get?
Typical range for venture-backed startups is 0.5-3% of fully diluted, depending on role criticality and company stage. Senior engineering first hires often get 1-3%. Senior business first hires often get 0.5-2%. Pre-funding first hires sometimes get higher equity (3-5%) reflecting higher risk and lower cash comp.

Who should I hire first?
The person who fills the biggest gap left by the founders. For technical-founder pairs, often the first sales or operations hire. For non-technical founders without a technical cofounder, often a senior engineer who effectively becomes the technical cofounder. Hire for the gap, not for a second of something the founders already do well. Prioritize generalists over narrow specialists.

Find this article helpful?

This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!

OR

GoogleLinkedInFacebookX/Twitter

Submission confirms agreement to our Terms of Service and Privacy Policy.