Interview a former founder against the responsibilities of the job you are filling. Founding experience may contain useful evidence of initiative, selling, building, or hiring, but the title does not establish depth in each of those areas.
The central question is whether the candidate wants and can perform this particular mandate within your team.
Break the founder experience into work
Ask the candidate to map what they personally did, what a cofounder or team did, and what external partners provided. Let them discuss non-confidential examples without identifying former customers or investors.
| Your hiring need | Evidence to explore |
|---|---|
| Hands-on engineering | A technical decision, implementation, and operational follow-through |
| Commercial execution | A sales conversation they owned and how it progressed |
| People leadership | Expectations, feedback, delegation, and a difficult management decision |
| Product judgment | A customer problem, a scope choice, and the resulting learning |
Treat these as separate lines of inquiry. Raising money, running a company, and building production software are different activities.
Explore a decision that did not work
Ask: “Tell us about an important assumption that turned out to be wrong. How did you notice, and what did you do next?”
Useful follow-ups include who disagreed, what evidence changed the decision, and which responsibility the candidate accepts. Avoid demanding private financial history or personal explanations for a company's closure.
A failed venture is not a hiring verdict. A successful venture is not proof that the candidate personally performed the work you need.
Make decision boundaries explicit
Illustrative situation: A former founder joins a fictional startup as a senior engineer. They can propose product changes, but the product lead owns prioritization.
Discuss how the candidate would raise a concern, contribute evidence, and proceed after a decision. Ask for a past example of influencing someone who had final authority.
The point is not to screen out independent thinkers. It is to determine whether independent judgment and shared decision-making can work together.
Check what the candidate wants next
Ask which parts of founding they want to keep doing and which they want to stop doing. Compare those answers with the actual calendar of the role.
Clarify hands-on work, management expectations, reporting relationships, and future scope. Do not imply a near-term executive role unless that is part of an approved plan.
Write the decision in ordinary terms
“Strong experience defining early customer problems; engineering depth still needs assessment” is more useful than “founder energy.”
Use the same anchored interview scorecard as for other candidates. Add follow-up questions to understand their context, while keeping the job requirements consistent.