Founding Engineer
A Founding Engineer builds the first version of a product with no team, no spec, and no precedent. The role requires breadth over depth: integration, debugging, and architecture at Level 3, plus enough product discovery to decide what to build when nobody tells you.
Also called: first engineer, startup generalist engineer, founding developer
What skills does a founding engineer need?
The founding engineer role is defined by ambiguity tolerance more than by stack. The failure mode is an excellent specialist who cannot function without a spec. The screen for this role is particularly broken: it selects for people who worked at recognisable startups, when the actual predictor is whether someone can decide and ship without permission.
| Skill | Level | What that means | Status |
|---|---|---|---|
| API & Systems Integration | L3 Independent | Designs for idempotency and partial failure, and makes state recoverable when the remote system misbehaves. | Required |
| Debugging & Diagnosis | L3 Independent | Diagnoses failures where the error is misleading, tests the cheapest hypothesis first, and verifies the root cause before fixing. | Required |
| LLM Application Architecture | L2 Working | Structures context deliberately, manages token budgets, and handles rate limits and timeouts. | Required |
| Product Discovery | L2 Working | Asks non-leading questions, separates what users said from what they did, and reports uncomfortable findings. | Required |
| Spec & Requirements Writing | L2 Working | Includes acceptance criteria and states scope boundaries, so the team knows when it is done. | Nice to have |
| Code Review & Judgment | L2 Working | Finds correctness bugs and explains why they are bugs. | Nice to have |
No years-of-experience row, deliberately. Seniority is the level.
Which candidates does a CV screen miss for this role?
These job titles regularly belong to people who can do this work at the required level, and regularly fail a keyword screen for it.
Who currently scores highest
Live from the scoring engine — ranked on proof, with the CV title shown so you can see what a keyword filter would have done.
How do you assess a founding engineer?
Hiring a founding engineer near you
Founding Engineer: questions people ask
- Do I need startup experience to be a founding engineer?
- No, and screening for it is the main reason these searches take so long. What predicts success is deciding and shipping under ambiguity, which agency and freelance engineers often have in abundance.
- How is breadth assessed without a long take-home?
- Through decision density rather than volume. The challenge presents an under-specified brief and scores what you chose to build first and what you deliberately left out.
- What is the most common gap?
- Product discovery at Level 2. Strong engineers often build the stated request perfectly without checking whether it was the right request.