Stop using generic interview questions and gut feel. The best founders use a structured process, starting with a hiring scorecard to define needs. They then use specific behavioral questions to test for competence, motivation, self-awareness, and team contribution, focusing on past performance as the only reliable predictor of future success.
Key takeaways
- Build a hiring scorecard before you write the job description.
- Ask behavioral questions: "Tell me about a time..." not "What would you do if..."
- Test for four signals: Can they do the job? Will they do it? Are they self-aware? Will they elevate the team?
- Design a role-specific work-sample test that mirrors the actual job.
- Never skip reference checks, and learn how to do "backchannel" references.
- The candidate should talk 80% of the time. You are there to listen and learn.
Your First 10 Hires Are Your Co-Founders
Your first ten hires determine whether your startup lives or dies. They set your company’s DNA. A great hire can change your trajectory. A bad one can cost you six months of runway, tank team morale, and kill your momentum. A mis-hire easily costs over $250,000 in salary, severance, lost productivity, and recruiting fees. For a seed-stage startup, that is a fatal blow.
The interview is your primary tool for getting this right. But most founders treat it like a casual chat, asking generic questions and hiring on "gut feel." This is a recipe for disaster. Your goal isn't to find someone to have a beer with; it's to find someone who can build a company with you.
The single most important principle of effective interviewing is that past performance is the best predictor of future performance . Your job is to systematically uncover that past performance. This playbook gives you the questions and frameworks to do just that.
The Antidote to Bad Hiring: The Scorecard
Before you even think about posting a job description, you must define what "good" looks like. The single most effective tool for this is a hiring scorecard. This document forces you to define the 3-5 essential traits, skills, and outcomes required for the role. Without it, you will be swayed by charisma, a prestigious logo on a resume, or how much a candidate reminds you of yourself. With it, you have a consistent yardstick to measure every single candidate.
Your scorecard is your operating system for hiring. It ensures every person involved in the interview process is looking for the same things. It is the best defense against bias and lazy decision-making.
The Mission: A one-sentence summary of the role’s purpose. Why does this job exist? · Key Outcomes (First 12 Months): 3-5 specific, measurable goals the person in this role must achieve. (e.g., "Launch V1 of the mobile app," "Build a repeatable sales process that generates 10 new SQLs per week," "Reduce customer support response time to under 1 hour.") · Core Competencies & Skills: The non-negotiable technical or functional expertise. Be specific (e.g., "Mastery of React and server-side rendering," "Experience building and managing a B2B content calendar"). · Behavioral Traits: The personality attributes your startup needs to succeed. Instead of "team player," write "gives and receives direct feedback gracefully." Instead of "hard worker," write "high agency and defaults to action."
1. Owner's Mentality: Takes initiative and sees projects through without hand-holding. Takes responsibility when things break.
2. Scrappiness & Speed: Can achieve ambitious goals with limited resources. Prefers shipping a good solution today over a perfect one next month.
3. Product Sense: Demonstrates a deep-seated need to understand and solve user problems, not just ship features.
4. Grit & Resilience: When they get punched in the face (metaphorically) by a production bug at 2 AM, do they get back up and fix it?
5. A "Spike" in a Key Area: Are they exceptionally good at one thing critical to the role (e.g., UI/UX, database optimization, API design)?
The Four Signals to Test For
Every question you ask must map to your scorecard. Group your questions to ensure you’re assessing the whole candidate across four key signals. You need to know if they can do the job, if they will do the job, if they are self-aware, and if they will make your team better.
Signal 1: Can They Do the Job? (Assessing Competence)
Go beyond their resume. Your goal here is to get concrete proof of their skills. The best way to do this is with behavioral questions that force them to tell specific stories about their past accomplishments.
The Best All-Around Question: "Walk me through the project you are most proud of. What was the goal, what was your specific role, what did you personally do, and what was the measurable outcome?" What to look for: Do they talk about "we" or "I"? A-players own their individual contributions. Do they use specific metrics ("increased conversion by 15%") or vague generalities ("made things better")? If they say "we," follow up: "That sounds like a great team effort. What was the part of that project that you personally drove from start to finish?" · The Problem-Solving Deep Dive: "Tell me about the hardest technical (or strategic) problem you've solved in the last year. How did you approach it, what options did you consider, and why did you choose the path you did?" What to look for: A structured, logical thought process. You want someone who analyzes problems from first principles. Great follow-up questions: "What were the trade-offs you had to make?" and "What would you do differently if you faced that problem again today?" · The 30-Day Plan: "Based on what you know, what would be the first thing you'd do in your first 30 days here? What questions would you need to ask?" What to look for: This shows if they’ve done their homework. A great answer is action-oriented and focuses on diagnosing before prescribing (e.g., "First, I'd talk to 5 existing customers and the 3 sales reps..."). A red flag is a candidate who proposes a major solution before they understand the problem space.
Signal 2: Will They Do the Job? (Assessing Drive & Ownership)
A brilliant person who isn't motivated is a net negative. These questions probe for an internal engine and a genuine interest in what you’re building.
The "Why Us?" Test: "What about our company, our mission, and this specific role stood out to you?" What to look for: A generic answer like "I'm looking for a new challenge in a fast-paced environment" is an immediate red flag. A great answer connects their specific skills and passions to your specific mission. They should have researched your company beyond the homepage and be able to articulate why your startup , not just any startup. · The Ownership Litmus Test: "Tell me about a time you had to do something that wasn't in your job description." What to look for: In a startup, everyone does the dishes. You need people who see a problem and solve it, regardless of whose "job" it is. A candidate who complains about a previous boss asking them to step outside their lane is a non-starter. · The Ambition Check: "Where do you see yourself in five years? How does this role fit into that plan?" What to look for: You aren't looking for a lifelong commitment. You want to see if they have a thoughtful career narrative. The best candidates see your role as a critical step that allows them to build specific skills and have a specific impact, helping them reach their long-term goals.
Signal 3: Are They Self-Aware? (Assessing Coachability & Growth)
You want people who are confident but humble. They must be able to learn, adapt, and handle feedback without getting defensive. Without coachability, a talented employee will quickly become a toxic one.
The Modern "Weakness" Question: "What’s some hard feedback you've received recently? How did you handle it?" What to look for: Defensiveness is the ultimate red flag. You’re looking for someone who listened, sought to understand, and made a change. Bonus points if they thank the person who gave them the feedback. If they can’t name any, ask, "What would your last manager say you need to work on?" · The Growth Mindset Question: "Tell me about a skill you've taught yourself in the past year. How did you go about it?" What to look for: This tests curiosity and the ability to learn independently, which is critical in an ever-changing startup environment. A great answer is specific and shows a process (e.g., "I wanted to get better at financial modeling, so I took a course, read these three books, and built a model for our last feature launch.").
Signal 4: Will They Elevate Our Team? (Assessing Culture Add)
Stop trying to hire for "culture fit." Fit leads to a homogenous team of people who think and act just like you. Aim for "culture add." You want people who share your company's core values while bringing unique perspectives, backgrounds, and skills.
The Values Alignment Question: "Describe the work environment where you’ve been most productive and happiest. What were the key ingredients?" What to look for: Listen for alignment with your actual operating values. If they say "structured, quiet, and predictable" and you run a chaotic, loud, and fast-changing office, it’s not going to work, no matter how talented they are. · The Collaboration Question: "Tell me about a time you had a significant disagreement with a teammate or manager. How did you resolve it?" What to look for: Disagreement is healthy; destructive conflict is not. Look for someone who addresses conflict directly and respectfully, focuses on the shared goal, and can separate the idea from the person.
Beyond Questions: Two Tools You Must Use
1. Work Sample Tests: The Ultimate Predictor
The single best predictor of job performance is a well-designed work sample test. It cuts through talk and shows you what a candidate can actually do. This should be a short (2-4 hour), real-world exercise that mirrors the actual job.
For Engineers: A small coding challenge that tests the exact skills needed for the role. No abstract brain-teasers. · For Marketers: Ask them to outline a GTM plan for a new feature or write a sample email campaign. · For Sales: A mock discovery call where you play the role of the customer.
Pay them for their time. It shows you respect them and value their work. The signal you get from this is worth 100x the small cost.
2. Reference Checks: The Truth Serum
Never skip reference checks. They are not a formality. Ask the candidate for 2-3 references, including their most recent direct manager. But don't stop there. The best insights often come from "backchannel" references—people you find through your own network who have worked with the candidate.
When you call, don't ask generic questions. Be direct and specific. Your script should be:
"Hi [Name], I'm [Your Name], founder of [Company]. We're seriously considering hiring [Candidate] for a [Role Title] role, and I was hoping you could give me your candid perspective on working with them. I want to be clear: anything you share will be held in the strictest confidence."
"In what context did you work with [Candidate]?" · "What was [Candidate]'s single biggest strength? What did they deliver that you remember?" · "What was their biggest area for growth? What feedback did you give them?" (This is the most important question). · "On a scale of 1-10, how would you rate their performance in that role?" (Anything less than an 8 is a no). · "The role here requires [Key Trait from Scorecard, e.g., high-agency problem solving]. How have you seen them demonstrate that?" · The Magic Question: "Would you enthusiastically re-hire them?" (Listen for a pause. Any hesitation is a huge red flag).
Common Founder Mistakes in Interviews
Talking More Than Listening: The ideal interview has the candidate talking 80% of the time. You are there to gather data. You sell them on the job after you’ve decided you want them. · Asking Only Hypotheticals: "What would you do if..." invites speculation. "Tell me about a time you did..." provides proof. Stick to the past. · Ignoring Red Flags: If a candidate is late, condescending to the receptionist, or gives vague, rambling answers, don't ignore it. That’s data. · Hiring for "Potential" Over "Proof": At an early-stage startup, you need people who can deliver value on day one. Hire people who have already done what you need them to do. · Asking Illegal Questions: Never ask about age, race, ethnicity, gender, religion, marital status, family plans, or disability. It's illegal and irrelevant.
How to Apply This Playbook This Week
Pick Your Most Critical Open Role. Pull up the job description. · Build a Scorecard. Write down the mission, 3-5 key outcomes, and the essential behavioral traits. Be brutally honest about what you need. · Upgrade Your Question List. Map every question to an attribute on the scorecard. Replace at least three of your generic questions with the behavioral questions in this guide. · Design a 2-Hour Work Sample Test. What’s a small, self-contained project that mirrors the core work of the role? · Schedule and Divide. Ensure every interviewer is assigned a specific set of scorecard attributes to test. No one should be asking the same questions. Everyone must write down their feedback against the scorecard after each conversation.
Hiring is the highest-leverage activity for a founder. By moving from a generic chat to a structured, evidence-based process, you dramatically increase your odds of building a legendary company.
Frequently asked questions
- What's the most common mistake founders make in interviews?
- Relying on "gut feel" instead of a structured scorecard and behavioral questions. This leads to biased, inconsistent hiring that optimizes for people who are like you, not people who are good for the role.
- How long should a good interview process be?
- For early-stage startups, it should be fast and intense: 1-2 weeks from first contact to offer. A typical process includes a phone screen, 2-3 focused interviews (including a work sample), and a final offer call.
- What is a "work-sample test" and should I use one?
- It's a short, real-world exercise that mimics the job (e.g., code a small feature, outline a marketing campaign). Yes, you should absolutely use one; it's the single best predictor of job performance.
- How do I handle a candidate who gives vague answers?
- Politely interrupt and ask for specifics. Use phrases like, "Can you give me a concrete example of that?" or "Walk me through the actual steps you took." If they can't provide specifics, that's a major red flag.