Founding engineer job description template (2026)
Hiring your first engineer is the most important hire you'll make. A bad founding engineer can set you back 12 months. This template covers what the role actually is, what to pay, what equity to offer, and how to write a JD that attracts the right candidates.
What is a founding engineer?
A founding engineer is typically employee #1–5 at a startup. They're not just a senior engineer executing tickets — they're a technical co-owner who shapes the product, architecture, and engineering culture from the ground up. The best founding engineers are comfortable with: building 0→1 without a playbook, making irreversible architectural decisions with incomplete information, interviewing and hiring the next wave of engineers, and writing code that will be maintained for years.
Founding engineer job description template
Copy-paste this template and adapt it to your product, tech stack, and stage:
Founding Engineer — [Company Name]
Location: Remote (US timezone) / [City, State]
Compensation: $[X]–$[Y] base + [0.25%–2%] equity
Stage: [Pre-Seed / Seed / Series A]
About the role
We're looking for a founding engineer to join [Company Name] as one of our first engineers. You'll work directly with [Founder Name] to build [product description]. This is not a feature factory role — you'll co-own the technical roadmap, make architectural decisions, and help us ship the product that gets us to [Series A / $XM ARR / acquisition].
What you'll do
- Build and own [core product area] from the ground up
- Set the technical foundation: architecture, stack, CI/CD, and testing standards
- Ship production code within your first week
- Help hire and evaluate the next wave of engineers
- Participate in investor conversations and technical due diligence
- Work directly with users to understand what to build next
What we're looking for
- 5+ years of software engineering experience with at least 1 year at a startup (pre-Series B)
- Demonstrated experience building and shipping 0→1 products
- Full-stack capability with [Tech Stack] — you write backend and frontend as needed
- Strong opinions about system design, loosely held
- Comfortable making decisions under uncertainty without waiting for consensus
- Track record of mentoring engineers or leading small teams
- [Bonus] Experience with AI/LLM systems, [specific domain], or [tech]
What you won't deal with
- Long approval chains — you have autonomy over technical decisions
- Bloated sprint processes — we ship and iterate
- Death-by-meetings — async-first with intentional syncs
What equity should a founding engineer get?
| Stage | Salary adjustment | Typical equity |
|---|---|---|
| Pre-seed (#1–2) | 50–70% of market | 1.5%–3% |
| Seed (#2–4) | 70–85% of market | 0.5%–1.5% |
| Series A (#4–8) | 85–100% of market | 0.1%–0.5% |
Red flags to avoid when hiring a founding engineer
- Only experience at large tech companies (FAANG, etc.) with no startup exposure
- Can't articulate why they want to join a startup vs. a stable company
- Wants to work in a narrow specialization rather than across the stack
- No examples of making architectural decisions that they owned end-to-end
- Needs to be told what to work on — founding engineers are self-directed
How to run the technical interview
A founding engineer interview should test judgment, not algorithmic knowledge. Focus on:
- System design for your actual product — ask them to design a core component of what you're building
- Trade-off reasoning — “Why would you choose X over Y here? What would change your answer?”
- Past 0→1 work — walk through a product they built from scratch: what decisions did they make and why?
- Debugging live — give them a real bug in your codebase and watch how they approach it
- Writing — a founding engineer who can't write an architecture doc clearly is a liability
Need help hiring your first engineer?
HyperNest Labs provides fractional CTO services that include running your founding engineer hiring process — writing the JD, sourcing candidates, running technical interviews, and evaluating offers.
FAQs
What equity should a founding engineer receive?
Founding engineers typically receive 0.25%–2% equity depending on stage and salary adjustment. Pre-seed engineer #3 with below-market salary might get 1.5%–2%. At Series A with market salary, 0.25%–0.5% is more typical.
What's the difference between a founding engineer and a senior engineer?
A founding engineer is employee #1–5 who shapes technical culture, makes architectural decisions, hires the next engineers, and co-owns the product roadmap. A senior engineer executes within defined scope in an existing org.
How do I evaluate a founding engineer candidate?
Look for demonstrated ownership of 0→1 products, breadth across the stack, comfort with ambiguity, examples of making hard technical bets that paid off, and ability to articulate trade-offs clearly.