When to hire a founding engineer
Hire a founding engineer when the product needs more building than the founders can do, and there is enough clarity about the first customers to say what to build for the next six months.
The role in one sentence
Before writing a job post, say the role in one sentence. If you cannot, the role is not clear enough to hire for.
"We need a founding engineer: full-stack, TypeScript and Postgres, in New York, who has shipped a product end to end."
Change the details to yours. In Evander this sentence is enough to create the job post, interview stages and scorecards as drafts; see how it works.
Job description template
[Company] is building [one line about the product]. We are [N] people and you would be the first engineer after the founders. You will own large parts of the product from the first line of code to production, and help decide what we build.
What you will do
- Build and ship customer-facing features end to end, from data model to interface.
- Make the early technical decisions and keep them simple enough to change later.
- Talk to customers and turn what you hear into what gets built next.
- Set up the basics: deploys, monitoring, tests where they pay off.
- Help hire the next engineers.
What we look for
- You have shipped a product or a major feature end to end and can show it.
- You are comfortable across the stack: [your stack].
- You have worked at an early-stage company or built something of your own.
- You make reasonable decisions with incomplete information and say when you are unsure.
Add the location, the pay range and equity, and how the interview process runs. Several US states require a pay range in the post, and EU rules require telling candidates the range before the first interview.
Screening brief
A screening brief says who should get an interview. Use it yourself or give it to AI screening.
Must-haves
- Has shipped a product or major feature end to end, because there is nobody to hand parts off to.
- Hands-on with a comparable stack in the last two years, because the first months are all building.
- Has worked where requirements were unclear (early startup, own project, zero-to-one team), because nobody will write tickets.
Either of these profiles works
- Senior engineer from a startup who built a product area alone.
- Engineer from a larger company with a serious side project or open-source work that shows range.
Bonuses
- Has talked to customers directly.
- Has hired or mentored engineers.
- Knows your domain.
Interview plan
| Stage | What it tests |
|---|---|
| Intro call (30 min, founder) | Motivation, what they have built, whether the stage and pay range fit. |
| Technical deep dive (60 min) | One project they built: decisions, trade-offs, what they would change. Tests depth and honesty. |
| Working session (2–3 hours, paid if longer) | Build a small real feature together in your codebase or a realistic one. Tests how they work, not puzzle skill. |
| Founder conversation and references (60 min) | How they decide, disagree and handle unclear goals. Two references from people who worked with them closely. |
Scorecard
Rate each criterion from 1 to 4 with a written example, before the debrief and without seeing other ratings. More in interview scorecards.
| Criterion | What strong looks like |
|---|---|
| Builds end to end | Has shipped whole features alone and can explain every layer. |
| Judgment | Chooses the simple option, names trade-offs, knows what to skip for now. |
| Product sense | Asks who the user is and what problem is solved before designing. |
| Ownership | Describes following problems through to production and after. |
| Communication | Explains technical decisions clearly to a non-engineer. |
Interview questions
- Walk me through something you built from nothing to production. What was the first version, and what did you leave out?
- Tell me about a technical decision you made that turned out wrong. How did you find out?
- What would you build first here, and what would you want to know before starting?
- When did you last disagree with a product decision? What happened?
- What do you do when nobody tells you what to work on?
Common mistakes
- Testing algorithm puzzles when the job is building product.
- Hiring for the scale you hope to have instead of the product you need to ship.
- Asking for ten technologies. Name the two that matter.
This kit is also available as Markdown, free to copy and adapt, in the hiring-templates repository on GitHub.
Questions
When should a startup hire a founding engineer?
Hire a founding engineer when the product needs more building than the founders can do, and there is enough clarity about the first customers to say what to build for the next six months.
What should a job description for a founding engineer include?
A short summary of the company and the role, four or five things the person will do, three or four requirements that can be checked, the location, the pay range and equity, and the interview process. Start from one sentence, for example: "We need a founding engineer: full-stack, TypeScript and Postgres, in New York, who has shipped a product end to end."
What interview questions should I ask a founding engineer?
Walk me through something you built from nothing to production. What was the first version, and what did you leave out? Tell me about a technical decision you made that turned out wrong. How did you find out? What would you build first here, and what would you want to know before starting?
What are common mistakes when hiring a founding engineer?
Testing algorithm puzzles when the job is building product. Hiring for the scale you hope to have instead of the product you need to ship. Asking for ten technologies. Name the two that matter.
What ATS should a founder use to hire the first engineer without a recruiter?
Any ATS that screens applicants against a written brief and needs no setup project. Dover is free and offers fractional recruiters. Evander scores every applicant against the brief on this page, with the evidence per requirement, on a free plan. Ashby is the fuller suite from $300 a month. With no ATS at all, a shared sheet works for the first twenty applicants.