Most interview questions are a waste of everyone's time. "Tell me about yourself." "Where do you see yourself in five years?" "What's your biggest weakness?" These questions have been rehearsed so many times that the answers are basically costumes — polished, practiced, and completely disconnected from how someone actually works.
If you're a founder or operator making one to five hires a year, you can't afford a bad hire. You also can't afford to spend 10 hours per candidate only to trust your gut at the end anyway. The fix isn't a longer interview process. It's better questions.
Here's how to write interview questions that actually surface what you need to know.
Start with the job, not a question bank
Before you write a single question, get specific about what this person actually needs to do in the first 90 days. Not the job description version — the real version.
Ask yourself:
- What are the three most important things this person needs to accomplish in their first quarter?
- What's the hardest part of this role that most candidates won't expect?
- What does "bad" look like in this seat six months in?
If you're hiring a customer success manager, maybe the hardest part is handling a churned account from a frustrated customer who was misled during sales. That's your question prompt — not "describe your communication style."
Write down 3–5 specific job challenges before you write any questions. Every question you write should connect back to at least one of them.
The three types of questions that actually work
1. Behavioral questions (past behavior predicts future behavior)
These ask candidates to describe something they've actually done. The logic is simple: what someone did in a real situation is a better signal than what they say they'd do in a hypothetical.
The formula is: "Tell me about a time when [specific situation relevant to the role]..."
Examples that work:
- "Tell me about a time you had to deliver bad news to a customer. What happened, and how did you handle the follow-up?"
- "Walk me through a project that fell behind schedule because of something outside your control. What did you do?"
- "Tell me about a time you disagreed with your manager's decision. How did you handle it?"
What you're listening for: specificity, ownership, and what they learned. Vague, general answers ("I always try to communicate proactively...") are a red flag. Good answers name the situation, what they did, what the result was, and — ideally — what they'd do differently.
2. Work sample prompts
These ask candidates to demonstrate the actual skill the job requires. For some roles, this is a take-home assignment. But you can also build it into the conversation.
Examples:
- For a marketer: "Here's a real campaign we ran last year. Revenue was flat despite decent click-through rates. What would you look at first?"
- For an ops hire: "We're currently handling vendor invoices manually in a spreadsheet. Walk me through how you'd think about building a better process."
- For a sales rep: "Here's our product in one paragraph. Pitch it to me like I'm a skeptical procurement manager."
This doesn't need to be a 4-hour homework assignment. A 10-minute in-interview exercise often tells you more than 45 minutes of back-and-forth.
3. Pressure-test questions
These poke at the edges of what a candidate is claiming. They're not gotcha questions — they're follow-ups that separate people who actually did something from people who were adjacent to it.
Examples:
- After any behavioral answer: "What specifically did you do versus the team?"
- "What would your manager at that job say was your biggest area for improvement?"
- "If I called your last manager right now, what would they say about how you handle [X]?"
- "What's something you tried in that role that didn't work?"
The goal isn't to trip anyone up. It's to get past the rehearsed version and see how someone thinks when they're not working from a script.
How to structure a 45-minute interview
Here's a structure that works well for a first-round interview when you're a small team:
0–5 min: Context-setting. Explain what you're covering and give a 2-minute overview of the company and role. This isn't the time for a 20-minute pitch — candidates have done their research.
5–20 min: Two to three behavioral questions. Pick the ones most relevant to the hardest parts of the role. Let them talk. Don't interrupt. Take notes.
20–35 min: Work sample or role-specific scenario. Either something you've prepared or a real problem you're working on (with context removed if needed).
35–42 min: Pressure-test follow-ups and candidate questions. Let them ask you things — how candidates use their questions is also signal.
42–45 min: Close. What are next steps, timeline, and any logistical things to cover.
Fifteen minutes of behavioral questions is enough if you ask the right ones and actually follow up. The mistake most founders make is asking six questions shallowly instead of two questions deeply.
The questions to cut immediately
Stop asking these:
- "Where do you see yourself in five years?" — Everyone knows the acceptable answer. It tells you nothing.
- "What's your biggest weakness?" — You'll get "I work too hard" or "I care too much about quality." Useless.
- "Why do you want to work here?" — Most candidates will say something flattering about your company. Ask instead: "What are you trying to learn or accomplish in your next role?" That's the real question underneath.
- "Are you a team player?" — No one says no. Replace it with: "Tell me about a time a team project went sideways. What was your role in fixing it?"
Write questions before you talk to candidates — then actually use them
This sounds obvious but almost no one does it consistently. Write your questions before the first interview. Use the same core set for every candidate in the same role. This matters for two reasons.
First, it lets you compare candidates on the same dimensions instead of comparing whoever you liked more in the moment. Second, it protects you legally — inconsistent interviewing can create discrimination exposure even when that's not your intent.
Keep a simple interview scorecard: list the four or five things you're evaluating (technical skill, ownership, communication, whatever matters for this role), score each candidate 1–5 on each dimension right after the interview while it's fresh, and note specific evidence. "Strong communicator" isn't evidence. "Explained a complex process to a non-technical stakeholder and broke it into three clear steps" is.
Penroll helps you build role-specific interview question sets alongside your job post, so you're not starting from scratch every time you make a hire.
A few question frameworks that hold up across most roles
If you're not sure where to start, these tend to surface real signal in almost any hire:
On learning: "Tell me about something you got genuinely good at in the last two years. How did you go from okay to strong at it?"
On hard decisions: "Walk me through a decision you made with incomplete information. What did you do, and how did it turn out?"
On feedback: "Tell me about a piece of feedback that was hard to hear but turned out to be right."
On ownership: "Tell me about a time something went wrong on a project or goal you were responsible for. What was your role in what happened?"
On independence vs. collaboration: "How do you prefer to receive direction on a new project — more context and freedom, or more structure and check-ins? Tell me about a situation where you got the opposite of what you preferred."
These aren't magic. They work because they ask about real events, require specificity, and reveal how candidates think about their own work — not how they want to be perceived.
Where Penroll fits
Penroll is an AI hiring copilot built for small business founders who don't have an HR team. Once you define the role, Penroll helps you generate interview question sets tailored to what the job actually requires — not generic templates from a job board. It's a faster way to show up to interviews prepared, with questions tied to the specific skills and scenarios that matter for your hire.