Most founders wing interviews. They pull up the resume five minutes before the call, ask a few questions that feel right in the moment, and then make a gut-call hiring decision. Sometimes it works. More often, it leads to bad hires that cost you months of salary, onboarding time, and lost momentum.
If you're making 1–5 hires a year, each one matters enormously. A structured interview doesn't mean a stiff, corporate process — it means you show up with a plan, ask the same core questions to every candidate, and walk away with data you can actually compare.
Here's the framework I'd recommend for any founder or operator at a small company.
Why structure matters more at small companies
At a 200-person company, a bad hire is painful. At a 10-person company, it can set you back six months. You don't have the HR infrastructure to manage performance issues slowly, and you don't have deep enough bench strength to absorb the gap.
Structured interviews — where every candidate gets the same questions, in the same order, evaluated against the same criteria — consistently outperform unstructured ones at predicting job performance. That's not opinion; it's what decades of hiring research shows. But beyond the data, it also just makes decision-making faster. When you've asked the same five questions to four candidates, the comparison almost makes itself.
The four-part interview framework
This is designed for a 45–60 minute interview. You can compress it to 30 minutes by trimming the work history section, but don't skip the structured questions or the close.
Part 1: Set the stage (5 minutes)
Start by briefly explaining what the next 45 minutes will look like. This sounds small, but it matters. Candidates who know what's coming are less anxious, give better answers, and — importantly — form a better impression of your company.
Say something like: "We'll spend a few minutes on your background, then I'll ask you some specific questions about how you've handled certain situations. After that, I'll tell you more about the role, and we'll leave time for your questions."
That's it. One paragraph. It signals that you're organized and that you respect their time — both things that matter to good candidates who have options.
Part 2: Work history snapshot (10 minutes)
Don't read the resume out loud. Instead, ask one open-ended question that gives you a narrative:
"Walk me through your last two or three roles — what you were hired to do, what you actually ended up focused on, and why you made each move."
Listen for: clarity of thought, self-awareness, whether their trajectory makes sense, and any gaps or pivots worth exploring. You're not making judgments yet — you're building context for the structured questions that follow.
Follow-up prompts if things get vague:
- "What did success actually look like in that role — what were you measured on?"
- "Why did you leave?" (simple, direct, tells you a lot)
- "What were you most proud of there?"
Keep this section to 10 minutes. It's context-setting, not the main event.
Part 3: Structured behavioral questions (20–25 minutes)
This is the core of the interview. Behavioral questions — ones that ask candidates to describe specific past situations — are significantly better predictors of future performance than hypothetical questions.
"What would you do if..." questions are easy to answer well without ever having done the thing. "Tell me about a time when..." questions require real experience.
Pick 4–5 questions that map directly to the competencies the role requires. Here are examples by role type:
For operations or generalist roles:
- "Tell me about a time you had to build a process from scratch. What did you do, and what would you change in hindsight?"
- "Describe a situation where you had to push back on a decision from a manager or founder. How did you handle it?"
For sales roles:
- "Walk me through a deal you lost. What happened, and what did you learn?"
- "Tell me about a time you had to build a pipeline with little to no support. What worked?"
For customer-facing or support roles:
- "Describe the most difficult customer situation you've dealt with. What did you do?"
- "Tell me about a time you had to deliver bad news to a customer. How did you handle it?"
Universal questions that work for almost any role:
- "Tell me about a time things went sideways on a project you owned. What did you do?"
- "Describe a time you had to figure something out with very little guidance."
For each question, use the STAR format as a listening guide — you want to hear the Situation, Task, Action they took, and Result. If they give you vague answers, probe: "What specifically did you do?" or "What was the actual outcome?"
Ask every candidate the same questions. It sounds rigid, but it's the only way to make a fair comparison. Document their answers immediately after — memory degrades fast.
Part 4: Role preview and candidate questions (10–15 minutes)
This half of the interview is often neglected, especially at small companies that are excited to "sell" the role without being honest about it. Don't do that.
Spend 5 minutes giving an honest preview of the role:
- What does the first 90 days look like?
- What's hard about this job?
- What does success look like at 6 months?
- What's the team dynamic right now — size, how you communicate, what's working and what isn't?
Being candid here does two things: it filters out candidates who aren't actually a fit, and it builds trust with the ones who are. The best candidates appreciate honesty more than a polished pitch.
Then open it up for their questions. How they use this time is revealing. Candidates who ask sharp, specific questions about the business, the metrics, or the team structure are usually more serious and more capable than ones who ask about PTO on the first interview.
Scoring and comparison: the part most people skip
After every interview, score each structured question on a simple 1–3 scale:
- 1 = weak answer, vague or concerning
- 2 = acceptable, showed competence but nothing notable
- 3 = strong, specific, showed real skill or judgment
Total the scores across all questions. When you're comparing four candidates, having actual numbers — even rough ones — cuts through the bias that comes from "who did I like more."
Create a simple shared doc or spreadsheet with candidate names across the top and questions down the side. Fill it in within an hour of each interview while it's fresh. If you're involving a second interviewer (recommended), have them score independently before you talk.
How many interview rounds do you actually need?
For most roles at companies under 50 people: two rounds, maybe three.
- Round 1 (30 min): Screening call. Confirm basic fit, logistics, compensation alignment. Most candidates get filtered here.
- Round 2 (45–60 min): Structured interview using the framework above.
- Round 3 (optional, 30 min): For senior hires or roles with high stakes — a practical exercise, a panel conversation, or a call with a key stakeholder.
Don't drag it to four or five rounds unless you're hiring a VP or a role with significant equity. You'll lose good candidates to faster-moving companies.
Common mistakes to fix
Talking too much. Aim for 20–25% of the airtime. You're gathering data, not pitching.
Asking hypotheticals. "What would you do if a customer was angry?" tells you almost nothing. Ask what they actually did.
Ignoring red flags because you like someone. Likability is not a job qualification. Document the red flags and address them explicitly before making an offer.
Not preparing the questions in advance. Takes 15 minutes. Makes a huge difference. No excuses.
Making decisions in the room. Decide after you've slept on it and scored your notes. In-the-moment decisions are dominated by whoever gave the best first impression.
Where Penroll fits
Penroll helps small business founders move faster on hiring without the chaos — from writing the job post to organizing candidates. If you're running a structured interview process like this one and want to make sure the right candidates are showing up in the first place, starting with a sharp job description makes a real difference. Once your process is dialed in, Penroll keeps everything in one place so nothing falls through the cracks.