How to Hire Your First Employee at a Startup

The first hire changes everything. Done right, it doubles your output and gives you leverage on the constraints that matter most. Done wrong, it absorbs your time in management overhead, creates team culture problems that compound, and costs $20-50K to unwind.

Most early-stage founders hire too early, hire for the wrong role, or hire someone who's a great person but wrong for the stage. Here's how to do it correctly.

Quick answer: Hire when you have a specific, identified bottleneck — not when you feel generally overwhelmed. For most solo technical founders, the first hire is a generalist marketer or sales person to own go-to-market. For non-technical founders, it's a developer. Always run a paid 1-2 hour work sample before any offer, and confirm you have 12 months of runway to cover the full cost (1.3-1.5x base salary).

When to hire: the three signals

Signal 1: You have a clear bottleneck and you can't hire around it. The right first hire solves a specific constraint that's limiting growth. If your bottleneck is "not enough engineering hours to ship features while handling support and sales," you know the gap. If you're generally "overwhelmed and need help," that's not a hiring decision — it's a prioritization problem.

Signal 2: You have the revenue to fund it without betting the company. The full cost of a first hire (salary, benefits, equipment, taxes, recruiting costs) is typically 1.3-1.5x their base salary annually. A $60K hire costs ~$78-90K in total. Before hiring, confirm you have 12 months of that cost in runway beyond your current burn, or a revenue trajectory that will cover it within 90 days.

Signal 3: You can spend 30%+ of your time managing and developing this person. A common first-hire failure: the founder hires someone to "handle things" and then doesn't have the bandwidth to onboard, train, and manage them. A new hire with poor guidance underperforms and leaves. Hiring someone is only worth it if you can invest in making them excellent.

Who to hire first: the two most common patterns

Pattern A: The executor (most common for solo technical founders) You've been the only engineer and the only product person, and sales/marketing has been an afterthought. Hire someone who can execute the go-to-market side — a generalist marketer or sales/customer success person who can own customer acquisition while you build.

Good first hire if: you have product-market fit evidence but growth is stalling because you can't focus on both building and selling.

Pattern B: The builder (most common for solo non-technical founders) You've been selling, marketing, and doing customer success, but you need to ship faster. Hire a developer or technical lead.

Good first hire if: you have customer demand and revenue but are bottlenecked on product development speed.

Pattern C: Operations / virtual assistant (often premature) Hiring an admin to "take things off your plate" before you have a clear bottleneck is almost always premature. The work of deciding what to delegate, writing SOPs, and managing a VA often costs more time than it saves until you've reached significant scale.

Writing the job description

Be specific about the stage. "Startup" means different things. "Series A, 15 people, $2M ARR, in hyper-growth mode" is different from "bootstrapped, 2 people, $150K ARR, building slowly." The right candidate for one is wrong for the other.

Be honest about what early-stage means:

"You'll be figuring things out with minimal process — we're building the playbook together"
"Direct access to the founding team and real ownership over your function"
"Compensation is [salary range] + equity [X%] — below market on cash, meaningful ownership"

Candidates who need structure, process, and clear career ladders are wrong for early-stage. Write the JD in a way that attracts people who know what they're signing up for.

Define the three things this person will own in 90 days. "Responsibilities include..." followed by a list of 15 things tells a candidate nothing about priority. "In your first 90 days, you'll own: (1) building the outbound sales sequence, (2) onboarding the next 10 customers, and (3) creating our first customer success process" is specific and honest.

Evaluating candidates: beyond the resume

Work sample first. Ask every finalist to complete a short (1-2 hour) paid work sample relevant to the actual role:

For a marketer: rewrite a section of your landing page or draft an outbound email sequence
For an engineer: fix a specific bug in a sandbox environment or design the architecture for a feature
For a customer success hire: write a response to a difficult fictional support ticket + a 30-day onboarding plan

Pay for their time ($50-100). The work sample tells you more than three interviews about how they actually think and operate.

Reference checks (really call them). Don't just collect references — call them with specific questions:

"What was [candidate]'s single biggest failure in this role, and how did they handle it?"
"What environment brings out the best in [candidate]? What environment would they struggle in?"
"If you were building a company at [your stage], would you hire them again?"

The specific questions get past the "yes I'd recommend them" boilerplate.

Culture fit for stage, not culture fit for personality. Many founders hire for personality match and miss stage fit. A person who thrives in a 50-person company with clear processes will often struggle in a 5-person company where everything is ambiguous. Ask: "Tell me about a time you had to figure something out with no playbook and no manager to ask." The answer reveals whether they can operate in your environment.

The first 30 days: onboarding

Your first employee will underperform in their first month even if they're excellent. The context they need to be effective (your customer knowledge, your product decisions, your communication style) takes time to transfer.

Week 1: Full context download. Every important Notion doc, recording, customer story, and strategic decision they need to understand your world. Pair them on everything.

Week 2-3: Let them try things with close feedback. They'll do things differently than you would. Some of those differences are better. Give them the latitude to show you.

Week 4: First independent project with clear success criteria. "Own X end-to-end and report back in 2 weeks" builds ownership and accountability.

The 30-60-90 day plan: Set expectations in writing before day one. What does success look like at 30 days? 60 days? 90 days? Both of you should be able to answer that question without ambiguity.

Frequently Asked Questions

Should my first hire be a contractor or a full-time employee?

Start with a contractor if the scope is project-based or you're uncertain about the need. A 3-month contract with option to convert is a low-risk way to evaluate someone before a full-time commitment. For ongoing, core functions (engineering, sales), a full-time employee provides more commitment and ownership.

How much equity should I give a first hire?

Depends on their role and stage. Early employees (first 5-10 hires) at pre-seed or seed typically receive 0.1-1.0% equity, vesting over 4 years with a 1-year cliff. The range reflects role seniority and how early they joined. An engineer joining a 2-person company at $0 revenue deserves more than an SDR joining a $500K ARR company with 10 employees.

Should I hire a specialist or a generalist first?

Generalist for most early-stage companies. A specialist who's excellent at one function but can't flex across related areas requires you to hire additional specialists sooner. A strong generalist covers 80% of multiple functions adequately — which is what early-stage usually needs.

What if the first hire doesn't work out?

Acknowledge it quickly. Prolonged underperformance in a first hire sets bad precedents for how the company handles performance issues and drains energy that should go into the product. Have the direct conversation early, give clear expectations with a timeline, and make the separation decision within 60-90 days of recognizing the problem.

Find tools for running and scaling a small startup team at tools.cafe.