Nautis Logo
Team · Hiring

How to Hire Your First 10 Employees

Sourcing, interviewing, comp, equity, and references for the most important hires of your company's life. The bar, the process, and the most expensive mistakes.
10 min readUpdated Apr 30, 2026

Your first 10 employees set the culture, the technical foundation, and the operational bar of every employee that comes after. Most founders hire too slowly for the first 3, then too fast for the next 7. The right pattern is steady, high-bar, fast-process.

Hire generalists, then specialists

At sub-10 employees, you don't need a specialist for every function — you need 5-7 generalists who can each cover 1-2 areas plus pick up whatever's broken. The right early-stage hires:

  • Engineer #1-3: Full-stack, comfortable shipping across product, infrastructure, and data. Senior enough to make architectural decisions; pragmatic enough to skip premature abstractions.
  • Designer #1: Product designer who can also do basic brand/marketing assets. Most early-stage companies don't need a separate visual designer until 10-15 people.
  • First customer-facing hire: Either a senior sales person (if you've got product-market fit and a known sales motion) or a customer success person (if you have early customers needing a lot of hand-holding).
  • Operations / first PM hire: Around hire #5-7. Owns calendar, hiring ops, vendor management — frees the founders from everything that isn't sales or product.

Source from your network first

Your first 5 hires should mostly come from people you've worked with or known professionally. Reasons:

  • You skip 80% of cultural-fit risk.
  • References are essentially built in.
  • Early employees take less convincing about the company because they trust you.

After hire 5, you'll need to source actively. The best channels:

  • Your investors' portfolio companies (often have great people transitioning out).
  • Founder peer network (friends-of-friends introductions).
  • Targeted outbound on LinkedIn — but only after defining a tight ICP for the role.
  • Accelerator alumni networks.

Avoid recruiters for the first 10. They produce volume; you need precision.

The interview loop

Tight, structured, ~5 hours of contact:

  1. Founder screen (30 min). Mutual qualification. Are they a real candidate? Are you a real opportunity for them?
  2. Technical / craft interview (60-90 min). Real problem from your domain. Not LeetCode. The closer to actual work they'll do, the better the signal.
  3. Paid trial project (4-12 hours). Skip for the most senior hires; required for everyone else. Pay market rate. Use real but non-critical work.
  4. Team interviews (30-45 min × 2-3). Future peers. Focus on collaboration, communication, judgment.
  5. Founder closing conversation (30-45 min). Vision, equity, comp, timeline. The close, not the qualification.
  6. References (3 calls of 20-30 min each). Always. No exceptions.

Reference calls — what to ask

References are where bad hires get caught. The structure:

  • "What was their highest-impact contribution?"Concrete answer = strong candidate. Vague generalities = weaker signal.
  • "What kind of environment do they need to thrive?"Tells you whether your environment fits.
  • "What are they not great at?" Everyone has weaknesses. References who can't name any are usually telling you they didn't know the person well.
  • "Would you hire them again?" The headline question. Hesitation is a yellow flag.
  • "Who else should I talk to?" The off-list reference is often the most informative.

Equity bands by hire

Approximate ranges for pre-seed/seed-stage companies. Wider at later stage; tighter at higher seniority.

  • Co-founder hire (post-incorporation): 5-15%
  • Engineer #1 (very senior): 1-3%
  • Engineer #2-4: 0.5-1.5%
  • Engineer #5-10: 0.2-0.7%
  • First sales / GTM hire: 0.5-1.5%
  • First product designer: 0.5-1.0%
  • First non-tech operations hire: 0.2-0.5%

See our offer letters guide for the full structure of an early-stage offer.

Common early-hiring mistakes

  • Hiring for the company you'll be, not the company you are. A senior VP of engineering at 5 people will be bored in 3 months. Hire for the next 12-18 months, not the 3-year vision.
  • Skipping the trial project. Interviews catch maybe 60% of mismatches. Trial projects catch another 25%. References catch most of the rest.
  • Stretching the offer. If a candidate negotiates past your top of band, re-evaluate fit. Stretch hires are disproportionately likely to leave within 12 months.
  • Hiring around the team. Bringing in someone existing team members oppose almost always backfires. Listen to their concerns.
  • Not firing fast enough. Early-stage hiring mistakes cost you 10x more than they would at a 100-person company. Address performance issues within 30 days. See our guide on firing well.

Pair this guide with our offer letters guide and ESOP setup guide for the operational machinery to actually make great hires close.

FAQ

What's the equity range for early employees?+
Engineer #1: 1-3%. Engineer #5: 0.3-0.7%. Engineer #10: 0.15-0.4%. First non-eng hire: 0.3-1.5% depending on role. These widen for senior hires and shrink for more junior ones.
Should early employees be generalists or specialists?+
Generalists, with one specialty deep enough to ship without help. The rule: every early hire should both produce work in their core area and pick up adjacent work without management.
How long should the interview process be?+
1-2 weeks total, 4-6 hours of contact time. Anything longer signals founder indecision; anything shorter risks bad hires. Always include a paid trial project for senior or critical hires.
Should I require offer references?+
Yes for every hire. 2-3 references each — at least one former manager, one peer, one direct report (if applicable). Reference calls catch 30-40% of bad hires that interviews miss.
What's the biggest early hiring mistake?+
Hiring slowly because you can't decide, then panic-hiring once runway pressure hits. The right move: keep the bar high but compress the timeline. 1-2 weeks max from first conversation to offer.