Last month I watched a founder offer 1.5% equity to a senior backend engineer, get a yes on the call, and then lose him two days later to a company that had done almost nothing different — except answer his questions straight. That's the whole job in a sentence: recruiting early startup engineering talent is not a sourcing problem, it's a trust problem, and most founders fail it after they've already passed the technical bar.
I've been on both sides of this table. I've hired six engineers across two seed-stage companies, and I've watched three of those hires nearly fall apart because of something I said (or didn't say) in the final conversation. What follows is what I actually do now, including the parts that didn't work.
Key takeaways
- Speed beats polish. Great engineers are off the market in 10 to 14 days, so your process must be shorter than that, not longer.
- Sourcing is mostly reputation and referrals. Job boards are a rounding error.
- The candidate is interviewing you harder than you're interviewing them, especially above the senior level.
- If you're a non-technical founder, hire one person whose job is to vouch for the technical bar — a technical co-founder, an advisor, or a senior contractor.
- Equity conversations go badly when you improvise. Decide the numbers before the first call.
How to recruit early startup engineering talent without burning six months
The median seed-stage startup takes somewhere between two and four months from "we need an engineer" to a signed offer. Most of that time is wasted in two places: waiting for inbound applications that never come, and running a five-stage interview loop designed for a company ten times your size. Cut both and you can compress the whole thing to three weeks.
Here's the sequence I use now.
Start with the referral graph, not the job board
When I posted a founding engineer role on two job boards in early 2025, I got 140 applications. I interviewed four. I hired none. The person I eventually hired came from a Slack message in a community of about 300 backend developers, sent by someone I'd worked with five years earlier.
That ratio — 140 cold applications versus one warm intro — is not unusual, and it's the single biggest reason founders feel like hiring is impossible. It isn't. They're fishing in the wrong pond.
Where the actual pipeline comes from, in rough order of conversion for me:
- Former colleagues of people already on your team. Your first engineer knows forty more. Ask directly, and make the referral bonus real (cash, not a Starbucks card).
- Open-source contributors. If your stack touches an open-source project, the people filing thoughtful issues and PRs are pre-vetted on exactly the skill you need.
- Specialist recruiters — expensive, occasionally worth it, usually not at seed.
- Community channels: Discord servers, Slack groups, local meetups. Slow, but the signal is high.
- Job boards. Last resort. Expect a 1 to 3 percent response quality rate.
Design a process shorter than the candidate's patience
My current loop is four steps and takes nine days end to end:
- A 30-minute call with me. Mostly me answering questions about runway and the roadmap.
- A paid take-home, capped at four hours, with a hard deadline. Paid matters — it signals you respect their time.
- A technical deep-dive with whoever owns the codebase (90 minutes, live, no whiteboard puzzles).
- A conversation with a co-founder or an advisor. This is where the candidate decides, not where you evaluate.
Notice what's missing: no culture-fit round, no panel of five, no take-home that eats a weekend. Every extra stage costs you roughly a 15% chance of losing the candidate to a faster competitor. I learned that the hard way — a strong candidate withdrew in 2023 because my loop had six stages and he'd already signed elsewhere by stage four.
What senior engineers actually check before they join
They're not primarily looking at salary. They're looking at whether the technical decisions will be made by someone competent, and whether the company will still exist in eighteen months. You need crisp answers to both.
- Who owns the architecture? If the answer is "the founder, who doesn't code," expect silence.
- How much runway? Give a number, not a vibe. "Eighteen months" is an answer; "we're well funded" is not.
- What will I own in six months? Vague answers here read as "you'll be a code monkey."
- What's the hardest technical problem on the roadmap right now? Good engineers want to hear a real one.
Hiring rules worth borrowing
Four frameworks come up constantly in founder conversations. Two of them are genuinely useful; two get misapplied. Here's my honest read on each.
What is the 70/30 rule in hiring?
It means you should hire someone who meets about 70% of the requirements today and can grow into the remaining 30% — rather than holding out for a perfect match. I use it constantly for early-stage roles, because the job description you wrote will be obsolete in six months anyway.
The catch: the 30% gap has to be learnable, not foundational. Missing a specific framework? Fine, they'll pick it up in a month. Missing the ability to design a system from scratch? That gap stays a gap, and you'll pay for it later.
What is the 80/20 rule for startups?
Roughly 80% of your output comes from 20% of your work — and the same applies to hiring. About a fifth of the candidates you interview will account for nearly all the value you extract from the process. That's an argument for going deep on a small number of strong candidates rather than running a wide funnel.
In practice, it means I now spend 80% of my hiring effort on three or four people I'm genuinely excited about, and almost none on the pile of generic applications. Counter-intuitive, but it cut my time-to-hire in half.
What are the 5 C's of recruitment?
The five C's usually cited are company, candidate, cost, culture, and communication. They're a checklist for whether a hire will actually work — not a screening template.
- Company — does this role match where the startup is right now?
- Candidate — skills, yes, but also motivation. Why this company, specifically?
- Cost — total compensation including equity and any relocation. Run the number before the offer, not during.
- Culture — not "do we like them," but "will they make decisions the way this team makes decisions."
- Communication — how do they handle disagreement? You'll find out in the deep-dive, if you design it well.
The framework's weakness is that it treats "culture" as a yes/no when it's really a fit question. Two people can be excellent and one of them simply won't work in your specific three-person team. That's not a rejection, it's a mismatch, and it's fine to say so.
Is 1% equity in a startup good?
It depends entirely on stage and role, and I'd push back on any answer that skips that. At seed stage, 1% for a senior engineering hire is on the generous side — 0.5% to 1.5% for a founding engineer is a common band. At Series A, 1% would be unusually high for anyone but a staff-level hire.
What matters more than the number is the four-year vesting schedule, the cliff (usually one year), and — critically — whether the company discloses its cap table and share price. If a founder will not tell you the total share count, treat the percentage as a nice-looking fiction. I've seen two offers where the "1%" turned out to be something closer to 0.3% after a dilution round nobody mentioned.
| Stage | Base salary band (USD) | Equity for senior engineer | Typical time-to-hire |
|---|---|---|---|
| Pre-seed | 110–150k | 1.0–2.5% | 2–3 weeks |
| Seed | 140–190k | 0.5–1.5% | 3–4 weeks |
| Series A | 180–240k | 0.2–0.6% | 4–8 weeks |
| Series B+ | 210–280k | 0.1–0.3% | 6–10 weeks |
Where founders get this wrong
The most common mistake I see — and made — is treating the hiring conversation as an interrogation. In one round of hiring in 2024 I spent forty minutes of a sixty-minute call asking technical questions. The engineer later told me he'd checked out after twenty minutes. He took another offer.
What actually converts strong candidates is specificity: a concrete problem, a real number for runway, a named owner for the technical decisions, and a clear picture of what the first ninety days look like. Vague optimism about "a great team and huge potential" does not move anyone who has seen five startups pitch the same pitch.
And if you're non-technical? Say so, and say who you've brought in to compensate. I've watched non-technical founders close excellent engineers by being candid about that gap — and by naming an advisor who would review the technical bar. The engineers respected it far more than a bluff.
The part that stays with me
Recruiting engineers at the earliest stage is not really about hiring. It's about whether you can describe what you're building in a way someone senior and skeptical will believe. The process, the compensation band, the take-home — those are just the mechanics. The candidates who turn you down aren't usually turning down the offer. They're turning down the version of the next two years you painted, because it sounded slightly too smooth.
So the question I'd leave you with: if the best engineer you know sat across from you tomorrow and asked why your company will still be worth their time in 2028, what would you actually say? If that answer is fuzzy, no amount of sourcing will fix it.
