A founding engineer is one of the first 1-5 technical hires at a startup, joining before product-market fit and taking on scope that spans code.
A founding engineer is one of the first technical hires — typically employees 1 through 5 on the engineering side — who joins before product-market fit and often before the product's shape is clear. The scope is unusually broad: writing production code, making architecture decisions, interviewing the next hires, defining the deployment stack, and shaping the culture of everyone who comes after. The role is different in kind from a senior engineer at a series B; the compensation, expectations, and hiring process should reflect that.
Founding engineers are hired for range, not depth. The technical bar matters, but so does: comfort with ambiguity, willingness to work across the full stack (including infrastructure and ops), ability to ship code that will be rewritten in six months without becoming precious about it, judgment about when to build vs. buy, and interest in the business — not just the technology. A brilliant specialist who needs a spec is a worse founding engineer than a solid generalist who can talk to customers and ship.
Founding engineer compensation typically runs 1-3% equity (with cliff and vesting) plus below-market cash — often $150-200K vs. the $250K+ they could earn at a big tech company. The equity delta is the deal: you're asking someone to accept 30-50% less cash for 3-5 years in exchange for a lottery ticket. Be transparent about the math: strike price, fully-diluted share count, current 409A, what a $500M outcome looks like for their stake. Founding engineers who don't understand their equity end up feeling cheated even when the numbers are fair.
Your network first — people you've worked with, people who've worked with people you trust. Cold outreach at this stage rarely produces founding engineers; the risk profile is too specific. Look for signals: engineers who've been at 1-2 early-stage startups before, engineers with side projects that shipped, engineers who blog thoughtfully about technical decisions. Avoid: senior engineers from big tech who've never operated without infrastructure, tooling, and clear specs — the adjustment is often painful for both sides.
Founding engineer interviews should probe range, not depth. A useful loop: (1) Technical conversation about their most complex prior project — what tradeoffs, what they'd do differently. (2) Small paid trial project (4-8 hours, paid at consultant rate) — shows how they actually work, communicate, and make decisions under real ambiguity. (3) Customer-conversation simulation — can they hold a real conversation with a non-technical user without condescending. (4) Founder-fit conversation — this person will be in the room for every hard decision for 3+ years; the fit either works or doesn't.
First 30 days: they should be shipping code by day 5, talking to customers by day 10, and part of hiring decisions by day 30. Give them real ownership of a meaningful surface — not 'help out with X' but 'you own X.' Include them in board and investor updates so they have full context, not just the technical slice. Do not put them under a VP of Engineering hired later without an explicit renegotiation of scope and compensation; nothing burns a founding engineer faster than being managed by someone they helped hire.
Investor directory · Fundraising library · Articles A–Z · Company funding database