Your Startup First Hire: What Founders Actually Choose

TL;DR: Your startup first hire should be the person who removes the single biggest bottleneck to your growth — usually an engineer, occasionally a salesperson. Based on 200+ founder interviews on the PMF Show, founders now wait longer than ever to make that first hire (often past $500K–$1M in revenue), give first engineers roughly 1.5%–2% equity, and hire only when they feel real pull from the market.

After interviewing 200+ founders on the PMF Show, one pattern about the startup first hire is unmistakable: the timing has shifted dramatically. According to Peter Walker, who leads Insights at Carta and analyzes cap table data across 45,000+ US startups, founders are stretching the gap between incorporation and first hire longer than they have in years. The reason is capital efficiency — small teams can now build and sell on their own far longer before needing help. This guide breaks down who founders actually hire first, when they do it, and what they pay, drawing entirely on real founder stories shared on the show.

When should you make your startup's first hire?

The old playbook said raise a seed round, then immediately staff up. The data says otherwise. According to Peter Walker, CEO insights lead at Carta, the time from incorporation to first hire is now longer than it has been in a long time.

"Founding teams getting together saying, we have an idea. We can build it ourselves and we can start selling it ourselves. And we don't actually need to hire until we really feel that pull from the market." — Peter Walker, Carta

That pull-based timing showed up again and again. David Paffenholz, founder of Juice Box, didn't make his first hire — a founding engineer named Minju — until the company was at roughly $700K in revenue, growing 20%–30% every month. Within about two months of that hire, Juice Box crossed $1M ARR.

Wayne Slavin of SureApp took the patience further: he spent an entire year — "day 366," as he put it — building solo before bringing on his first five founding employees. Three of those five were still at the company ten years later.

Key stat: Juice Box waited until ~$700K ARR (growing 20–30% monthly) to make its first hire, then hit $1M within two months.

Should your first hire be an engineer or a salesperson?

For most software startups, the first hire is a developer — because building velocity is the constraint. Forrest Zeisler, co-founder of Jobber, knew exactly what came first.

"We made our plans that, like, the first thing we needed to do was hire another developer. As we were talking to people, our roadmap was growing." — Forrest Zeisler, Jobber

But the engineer-first default isn't universal. Eric Foster, founder of Tenex, argues the founding team itself must contain both a builder and a seller before you ever hire — and if it doesn't, your first hire should fill that gap.

"You have to have both roles in the founding team of your company. You have to have somebody who can sell and you have to have somebody who can build." — Eric Foster, Tenex

Foster is a vocal proponent of founder-led sales in the earliest innings, noting that early adopters "are buying the founders as much as they are the product." His point: don't outsource the function you most need to learn yourself. If you're a technical founder who can't sell, your first hire — or co-founder — should be someone who can, because in 2024–2025, defensibility and distribution win.

Key stat: Eric Foster has sold to the same customer four times across four different companies — proof that early trust, not headcount, drives a first sale.

How much equity should you give your first hire?

Founders consistently overestimate how much equity early employees expect. The Carta data is clear: the first engineer typically gets 1.5%–2% of the company, and that number has barely moved in years.

"Where you might give that first engineer one and a half percent of the company, maybe two percent of the company. That's been pretty standard for a while. It's not like the engineers today are getting five percent of the company on a regular basis." — Peter Walker, Carta

Walker added a forward-looking note for the rising wave of solo founders — roughly 36%–37% of companies joining Carta in the most recent year were solo-founded, up from about 10% a decade ago. His advice: solo founders sitting on an extra ~40% of equity should use it to attract a stronger founding team.

"So that's a shout to solo founders: if you have that extra forty percent of equity, use it on the early team." — Peter Walker, Carta

The honest counterpoint, also from the show: the financial expected value of being early employee #1 is often lower than staying at a big tech job. As Walker put it bluntly, "The expected value is much higher at Google." Which means your pitch to a first hire has to be about agency, upside, and mission — not just the cash-and-equity spreadsheet.

Key stat: First engineers receive ~1.5%–2% equity — a figure that has stayed flat even as solo-founded companies jumped from ~10% to ~37% of new startups on Carta.

How do you compete for talent when you can't pay top dollar?

This is the universal first-hire problem. Forrest Zeisler hit it the moment Jobber raised its first $250K.

"We have $250,000. It feels like all the money in the world. And then you go and try and make your first hire, and you can't hire anyone." — Forrest Zeisler, Jobber

Based in Edmonton, Alberta — outside any major tech ecosystem — Jobber couldn't outbid established employers. So the founders took candidates out for coffee and pitched them on the vision, asking engineers to "risk their career" on a startup. It worked because they sold the mission, not the paycheck.

Robert at Float took a more systematic approach to early comp. Rather than trying to match Google or Shopify (an impossible game), Float benchmarked cash salaries to the 80th–90th percentile within its actual cohort — a seed/Series A Canadian tech company.

"We have to be thoughtful about cash conservation, but it's also just not worth it because if we don't work with the best people, we're not going to have success anyways." — Robert, Float

The lesson across both stories: define your comparison set honestly (you're not competing with FAANG), pay competitively within it, and make equity meaningful.

Key stat: Float benchmarked early cash comp to the 80th–90th percentile of seed/Series A peers — not big tech — while Jobber landed its first engineer on a $250K total budget.

What's the most common first-hire mistake founders regret?

Holding on too long to a hire that isn't working. Bhaskar Sunkara, founder of Bicycle AI, named it directly as the thing he'd do differently.

"I would say fail fast on hiring... if you feel like someone's not really working out, or you're afraid of someone having carried the load so far but they're not sort of scaling beyond that level. Just make decisions quickly." — Bhaskar Sunkara, Bicycle AI

This applies double to your first hire, because in a tiny company a single mis-hire is a huge percentage of the team. The flip side, drawn from Peter Walker's data on a flat hiring market: with net headcount changes across Carta companies effectively flat over recent quarters, there's an enormous pool of strong talent available — startup salaries and equity packages have stayed flat precisely because supply is high. That's leverage for founders who hire carefully and decisively.

Key stat: Net startup headcount on Carta has been roughly flat for 9–12 months, leaving a large pool of available senior talent — and keeping early-stage salaries and equity packages flat.

Key Takeaways: How to Approach Your Startup First Hire

1. Wait for market pull, not a funding milestone. Founders now routinely hire their first employee past $500K–$1M in revenue, building and selling themselves until demand forces the hire.

2. Hire against your biggest bottleneck. For most software startups that's a developer (Jobber), but if your founding team lacks a seller or builder, fill that gap first (Tenex).

3. Budget ~1.5%–2% equity for your first engineer. Carta's data shows this has stayed flat for years; don't assume you need to give away 5%.

4. Solo founders should spend their equity surplus on the team. With ~40% extra equity versus a co-founded company, use it to land a stronger founding hire.

5. Stop competing with Google on cash. Benchmark to your real cohort (Float's 80th–90th percentile), and sell agency, upside, and mission instead.

6. Sell the vision in person. Jobber landed engineers in Edmonton by pitching the mission over coffee, not by outbidding incumbents.

7. Fail fast on a first hire that isn't scaling. A mis-hire is a huge share of a tiny team — Bhaskar Sunkara's biggest hindsight lesson.

8. Use the flat talent market to your advantage. Strong senior people are available; hire deliberately while the supply is high.

FAQ: Common Questions About a Startup First Hire

Q: What should my startup's first hire be?

A: For most software startups, the first hire is an engineer, because build velocity is the main constraint early on. The deeper rule from 200+ PMF Show interviews: hire against whatever is your single biggest bottleneck, and make sure your founding team already covers both building and selling.

Q: When should a startup make its first hire?

A: Later than most founders think. Carta data shows the gap from incorporation to first hire is at multi-year highs, with founders often waiting until they feel clear market pull — frequently past $500K–$1M in revenue, as with Juice Box at roughly $700K ARR.

Q: How much equity does a first engineer at a startup get?

A: Roughly 1.5%–2% of the company, according to Carta's cap table data. That figure has stayed remarkably stable, so founders generally don't need to grant 5% to attract a strong first engineer.

Q: How do I hire when I can't match big-tech salaries?

A: Don't try. Benchmark compensation to your actual cohort (Float targeted the 80th–90th percentile of seed/Series A peers), make equity meaningful, and sell the mission and agency that a startup offers and a large company can't.

Sources: Listen to the Full Founder Stories

• Peter Walker, Carta (Q2 2025 data episode) — Cap table data on first-hire timing, equity norms, and the rise of solo founders.
• David Paffenholz, Juice Box — Making a founding-engineer hire at ~$700K ARR while growing 20–30% monthly.
• Wayne Slavin, SureApp — A full year solo before bringing on five founding employees.
• Forrest Zeisler, Jobber — Why the first hire was a developer, and landing engineers in Edmonton on a tight budget.
• Eric Foster, Tenex — Why the founding team must contain both a builder and a seller before you hire.
• Robert, Float — Benchmarking early-stage comp to your real cohort instead of big tech.
• Bhaskar Sunkara, Bicycle AI — "Fail fast on hiring" as the biggest hindsight lesson.

Last updated: June 2026