Most small business hiring goes something like this: a founder chats with a candidate for 30 minutes, likes their energy, and offers them the job. Two weeks later, the second candidate gets a completely different conversation, a different set of questions, and somehow still gets compared to the first. This is how good people get missed and bad hires slip through.
Structured interviews fix this without adding bureaucracy. They give small teams a repeatable way to ask better questions, judge answers fairly, and make decisions based on evidence rather than gut feel. This playbook walks through exactly how to set one up, even if you have never run a formal hiring process before.
Why structured interviews matter more when you're small
Large companies can absorb a bad hire. They have layers of management, formal performance improvement processes, and enough headcount that one weak team member doesn't sink a department. Small teams don't have that cushion. One wrong hire can drag down morale, blow a budget, or leave a critical gap for months while you start the search again.
Structured interviews reduce that risk in three concrete ways. First, they force you to decide in advance what actually matters for the role, instead of discovering it mid-conversation. Second, they make it possible to compare candidates on the same criteria, which is nearly impossible if every interview is a free-flowing chat. Third, they leave a paper trail of notes and scores, which is useful if you ever need to explain a hiring decision or defend it against a claim of unfair treatment.
None of this requires an HR team or expensive software. It requires a short amount of upfront planning and the discipline to stick to it once the conversation gets going.
What "structured" actually means
A structured interview has three ingredients: the same core questions for every candidate applying for the same role, a scoring method decided before the interview starts, and interviewers who write down their evaluation independently before discussing it as a group.
This sits at one end of a spectrum. At the other end is the fully unstructured interview, which is really just a friendly conversation with no fixed questions and no scoring at all. In the middle sits the semi-structured interview, where you have a core set of questions but allow some natural follow-up and improvisation around them.
For most small teams, semi-structured is the sweet spot. You keep a consistent backbone of questions so you can compare candidates fairly, but you still get to follow interesting threads and let the conversation breathe. Full rigidity, reading questions off a script with zero deviation, tends to feel robotic and can put candidates off, especially for smaller companies where the personal touch is part of the appeal.
Step 1: Define the role before you write a single question
You cannot write good interview questions until you know exactly what success looks like in the role. This is the step most small teams skip, and it is the reason so many interviews end up being vague personality checks rather than useful evaluations.
Sit down and answer three questions honestly:
- What will this person actually be doing day to day, in specific terms, not just a job title?
- What does a great first six months look like, with one or two concrete outcomes?
- What skills, behaviours, or experience are truly non-negotiable, versus nice to have?
From this, build a short list of four to six core competencies for the role. For a customer support hire, that might be clear written communication, patience under pressure, comfort with ambiguity, and basic technical troubleshooting. For a sales role, it might be resilience after rejection, listening skills, and the ability to structure a pitch. Every question you write later should map back to one of these competencies.
Step 2: Build your question set
With your competencies defined, write two to three questions per competency. The most reliable format for small teams is the behavioural or situational question, because it asks for real evidence rather than opinions about how the candidate would behave in theory.
Behavioural questions ask about the past:
Tell me about a time you had to deal with an angry customer or client. What did you do, and how did it end?
Situational questions ask about a hypothetical, useful when the candidate has no directly relevant experience yet:
Imagine a client emails you furious about a late delivery that wasn't your fault. Walk me through exactly how you would respond.
Both formats work well because they push candidates past rehearsed talking points and into specifics. If someone answers vaguely, that itself is useful information. A simple follow-up like "what exactly did you say" or "what was the outcome" usually surfaces the truth quickly.
Avoid trick questions, riddles, or brainteasers unless the role genuinely involves that kind of problem solving. They mostly measure how comfortable someone is with the specific puzzle, not whether they can do the job.
A simple question bank to start from
- Describe a time you disagreed with a manager or teammate. What happened?
- Tell me about a project that failed or went badly. What did you learn?
- Give an example of when you had to learn something new very quickly for a job.
- Describe how you prioritise when you have three urgent tasks at once.
- Tell me about a time you had to give someone difficult feedback.
Step 3: Create a simple scoring rubric
A rubric is just a shared definition of what a good answer, an average answer, and a weak answer look like for each competency. Without one, two interviewers can hear the exact same response and walk away with opposite impressions.
Keep it simple. A three or four point scale works better than a ten point scale for small teams, because it forces clearer decisions and takes less time to fill in.
Communication skills:4 - Answer was clear, structured, and specific with concrete detail.3 - Answer was reasonably clear but missing some detail or structure.2 - Answer was vague, rambling, or hard to follow.1 - Candidate struggled to answer or gave an irrelevant response.
Write a one line description like this for each competency before the interviews start, not while you are sitting across from the candidate. Deciding what "good" looks like in the moment is exactly how bias creeps back in, because you unconsciously adjust the bar for candidates you already like.
Step 4: Run the interview consistently
Once your questions and rubric exist, running the interview itself becomes far easier. Open with a short, warm introduction so the candidate isn't thrown straight into evaluation mode. Explain roughly how long the conversation will take and what to expect.
Then move through your core questions in the same order for every candidate, at least as a starting point. It is fine to skip a question if the candidate has already answered it naturally elsewhere, and it is fine to ask a genuine follow-up if something interesting comes up. The goal is consistency of substance, not a robotic script.
Leave time at the end for the candidate to ask their own questions. How someone questions you is often as revealing as how they answer your questions, and it is a basic courtesy that improves your reputation as an employer regardless of the outcome.
If more than one person is interviewing across separate rounds, make sure everyone is asking from the same shared question set rather than improvising their own. Duplicated or wildly inconsistent questions across rounds is one of the most common complaints candidates have about small company hiring processes.
Step 5: Score independently, then compare notes
Immediately after each interview, and before talking to any other interviewer, write down your scores against the rubric along with brief notes on why. This single habit does more to reduce bias than almost anything else in this playbook.
When interviewers discuss a candidate before scoring independently, the most confident or senior voice in the room tends to anchor everyone else's opinion, even unconsciously. Independent scoring first protects against that and gives you a genuine second and third opinion rather than one opinion repeated three times.
Once everyone has scored independently, compare notes and talk through any big gaps. If one interviewer scored a candidate a 4 on communication and another scored a 2, that gap is worth discussing properly rather than just averaging it away.
If you are managing multiple roles or a higher volume of applicants, this is also where the right tools save real time. A platform like Hyrewell can automatically screen incoming applicants into a ranked shortlist, let candidates self-book interview slots without the usual back and forth emails, and handle e-signed offers once you've made your decision, which frees up your time to focus on the actual conversations rather than the admin around them.
Common mistakes to avoid
- Changing the questions mid-search. If you swap out core questions halfway through interviewing candidates for the same role, you lose the ability to compare fairly. Finalise your question set before the first interview.
- Letting the conversation drift entirely off script. A little natural follow-up is good. An interview that turns into an unstructured chat about hobbies for 40 minutes tells you almost nothing useful about job performance.
- Scoring after group discussion instead of before. This is the single most common way structured interviews quietly become unstructured again.
- Using the same three questions for every role in the company. Questions should map to the specific competencies of the specific role, not be a generic set reused everywhere.
- Ignoring your own rubric when a candidate is likeable. Likeability matters for team fit, but it should be scored as its own competency, not allowed to inflate every other score.
- Skipping notes because the team is small and everyone talks anyway. Verbal-only decisions fade fast and are hard to defend later if a hiring decision is ever questioned.
A simple template you can copy today
You do not need software to start. A shared document with the following sections is enough for most small teams:
- Role title and the three to five outcomes that define success in the first six months.
- Four to six core competencies for the role.
- Two to three questions per competency, written out in full.
- A one to four point rubric description for each competency.
- A scorecard for each interviewer to fill in independently, with a space for notes and a total score.
Reuse this document for every candidate applying to that specific role, and build a fresh one whenever you open a genuinely different type of role. Over time you will build a small library of question sets and rubrics that make every future hire for that role faster to run.
Adapting the playbook as you grow
As your team grows past a handful of people, you may want to add a short work sample or task alongside the interview, since real work is often more predictive of performance than conversation alone. You might also add a second interview round focused specifically on team fit and values, separate from the skills-based first round, so you are not trying to evaluate everything in one conversation.
Whatever you add, keep the core discipline intact: decide your criteria before you meet the candidate, ask the same core questions to everyone in the same round, and score independently before comparing notes as a group. That discipline is what actually makes an interview process fair, and fairness is what protects both your business and your candidates.
Labour laws around interview questions, record keeping, and candidate rights vary significantly between countries and regions. Before finalising your process, check your local employment regulations and official government guidance to make sure your questions and record keeping practices are compliant where you operate.