How to Hire at Pre-Seed: Your First 3 Engineers

Your first three engineering hires are the most consequential decisions you'll make as a founder. They shape your technical culture, your codebase's DNA, and your ability to recruit for the next 5 years. Getting this wrong is recoverable. Getting it right compounds. Here's how to approach it.

The Pre-Seed Engineering Hire Sequence

Most founders hire in the wrong order. Here's the right sequence:

```
Pre-Seed Engineering Org Build (Recommended Sequence)

HIRE #1 ─── Founding Engineer / Full-Stack Lead
- Can ship end-to-end (frontend + backend)
- Comfortable with ambiguity and frequent context-switching
- Strong architecture opinions without over-engineering
- You want this person to build the culture, not just the code

HIRE #2 ─── Domain-Critical Specialist
- Fill the biggest technical risk in your stack
- If ML is core: ML engineer before second backend engineer
- If infra is core: DevOps/Platform before second frontend
- This person plugs the gap that blocks shipping

HIRE #3 ─── Mirror / Velocity Engineer
- A strong generalist who can pair with #1 and ship fast
- Often mid-level, can grow into senior
- Chemistry with founding engineer matters as much as skills

AFTER THESE THREE: establish architecture, tooling, and code review standards
before hiring more. Adding engineers 4–6 to a messy foundation is painful.
```

What Founding Engineers Look Like

The founding engineer role is not "lead engineer" or "principal engineer." It's a specific archetype:

• Full-stack competence: Can build the API, the frontend, and the data pipeline solo if needed
• Low ego, high standards: Writes clean code under pressure without perfectionism paralysis
• Product instinct: Cares about what gets shipped, not just how it's built
• Recruiter: Will be the biggest factor in engineers 4–10 joining. They MUST be someone people want to work with
• Comfortable with chaos: Requirements change daily; they adapt without drama

What founding engineers are NOT: pure specialists, people who need large teams to be effective, or those who need perfect specs before starting.

Compensation at Pre-Seed

Role	Salary Range	Equity Range	Notes
Founding Engineer (Engineer #1)	$120K–$160K	0.5%–2.0%	Depends heavily on stage and funding
Engineer #2 (specialist)	$130K–$165K	0.3%–1.0%	Smaller discount; early risk visible
Engineer #3 (generalist)	$125K–$160K	0.2%–0.75%	Often mid-level growing into senior

Source: RFS pre-seed placement data and lethain.com founding team compensation analysis.

Important: These are funded pre-seed numbers (post $500K–$2M raise). Bootstrapped or friends & family-funded companies have to offer more equity to offset lower cash.

What We've Seen at RFS

> Based on 30+ pre-seed engineering searches:
>
> - Average founding engineer equity: 0.85% (median)
> - Most common mistake: first hire is too senior — principal engineers don't thrive at pre-seed
> - Median time to fill founding engineer role: 62 days (longest search in our portfolio)
> - Most common sourcing success: warm referrals from founders' prior networks (71% of fills)
> - Most predictive interview signal: "Tell me about the last thing you shipped solo, start to finish"

Where to Find Pre-Seed Engineers

• Your own network: Former colleagues, college roommates, people you've worked with and admired
• YC talent network: If you're a YC company, the talent pool is dense and trust-based
• Founder alumni groups: Seed-stage founder alumni from accelerators often know great engineers
• Technical co-founder communities: Indie Hackers, Pioneer.app, Hacker News "Who's hiring?"
• Recurse Center alumni: Self-directed learners who built for fun — often great pre-seed fits
• RFS: We specialize in early-stage engineering searches; warm referral network is our main lever

The Interview That Matters Most

At pre-seed, the most predictive interview is a 3-hour paired coding session on a real problem from your product. Not LeetCode. Not a take-home. Not a verbal system design.

Specifically:

• Give them a real bug or small feature in your actual codebase (or a sanitized version)

• Watch how they orient in an unfamiliar codebase

• Notice: Do they ask good questions? Do they read existing patterns? Do they over-engineer?

• Debrief: What would they do differently if this were their codebase from day one?

This tells you more than 10 hours of standard technical interviews.

Frequently Asked Questions

Q: Should our first engineer be more senior (principal/staff) or more mid-level? A: Err toward senior-but-not-principal. You want someone with 5–8 years of experience who has built systems end-to-end. True principal/staff engineers often struggle with pre-seed ambiguity and the lack of team structure. Senior engineers who've worked at 1–2 companies and want to "own something" are the sweet spot. Q: How important is culture fit at pre-seed? A: More important than any other stage. These engineers will define your culture for the next 3–5 years. A technically brilliant person who creates drama or hoards knowledge will cause permanent damage. Trust your instincts about interpersonal dynamics here. Q: Can we use contractors or agencies for the first engineering hire? A: Agencies don't work at pre-seed — you need someone who owns the outcome, not a vendor. Contractors can be useful for a specific project (e.g., "build our MVP MVP") but don't substitute for founding engineers who will stay and grow. Q: How much equity should we reserve for the first 5 engineers? A: Plan for 4–7% of the fully diluted cap table for the founding engineering team (engineers 1–5). Common mistake: under-equitizing early engineers and facing retention problems at Series A when institutional investors push for refreshes. Q: What's the biggest pre-seed engineering hiring mistake? A: Hiring too fast. It's tempting to hire 4–5 engineers right after raising pre-seed. But engineers 4–5 hired before you have a coherent architecture, working deployment pipeline, and code review culture will slow you down, not accelerate you. Get 3 solid engineers working well together before scaling. Related: How to Hire a Software Engineer at a Series C Startup (2026) · How to Hire Your Founding Engineer: What Actually Works

---

Start an engineering search with Recruiting from Scratch →