Founder Interview Checklist for Investors
Use this checklist when interviewing startup founders. The goal is to assess founder-market fit, execution ability, and ambition in 45-60 minutes.
Opening (5 min): Warm up. Ask about their background and why they started the company. Listen for passion and domain expertise.
Problem and market (15 min): What problem are they solving? Who has this problem? How big is the market? Why now? Listen for specificity and customer insight.
Product and traction (15 min): What have they built? What's the traction? (GitDealFlow signal for engineering velocity.) What are the next 3 milestones?
Team and hiring (10 min): Who's on the team? What roles are they hiring? How do they plan to scale the team?
Fundraising and terms (10 min): How much are they raising? At what terms? Use of funds? Listen for realism and alignment.
How to Use This Checklist
A checklist earns its place when every line maps to evidence you can obtain. The items above follow the same public-data discipline behind GitDealFlow: 350+ startup GitHub organizations tracked across 15 sectors, refreshed weekly, with breakouts identified 21 to 47 days before the round. Where a line asks about engineering execution, the evidence is usually public: commit velocity, contributor concentration, and repository expansion, all confirmable from the repository itself rather than from a pitch deck.
Related Checklists
A practical read-through of Founder Interview Checklist for Investors: the dataset behind this page refreshes weekly across 350+ organizations and 15 sectors, and every figure shown traces to a public GitHub REST API pull. That matters for two reasons. Reproducibility: any number here can be re-derived from primary sources, which is the standard the published methodology sets for itself. Timeliness: engineering acceleration precedes announcements, so this page follows the data cadence rather than the news cycle, and the freshness endpoint always reports the exact pull date.
If Founder Interview Checklist for Investors is your entry point, the fastest next steps are fixed: skim the glossary for the three or four terms that anchor the topic, open the research dataset to see the raw weekly snapshots behind the summary numbers, and run one live query against the free momentum checker with a company you already know well. Seeing the signal fire on a familiar name is the quickest way to judge whether code-side sourcing belongs in your own workflow.
One caveat worth stating plainly on Founder Interview Checklist for Investors: momentum is a leading indicator, not a verdict. A repository can accelerate for reasons that never become a fundraise, and a quiet quarter does not mean a team is failing. The disciplined use of this page is as one input in a stack, a way to rank where scarce diligence time goes, and a way to notice change early. The methodology page documents every limitation, including the bot filter, the two-period confirmation rule, and the sectors where coverage is thinnest.
FAQ
How long should a founder interview be?
45-60 minutes for first meetings. Shorter and you can't assess depth; longer and founders get guarded. Schedule 90 minutes for finalists.
What's the most important question to ask?
'What's the hardest thing about what you're building?' Strong founders light up and get specific. Weak founders give generic answers.
Should I take notes during the interview?
Yes, but sparingly. Maintain eye contact. Jot key quotes and red flags. Full notes immediately after the meeting while it's fresh.