Structured interviews for small teams: questions, scorecards and fair decisions
Unstructured chats feel natural but predict poorly. Here is how a small team can set up structured interviews in an afternoon: the skills to assess, questions to ask, a scorecard with anchors and how to decide.
On this page
Quick answer: A structured interview asks every candidate the same job-related questions, in the same order, and scores each answer against a rating guide you agreed in advance. Research that re-examined decades of hiring studies (Sackett and colleagues, 2022) found it to be the strongest single predictor of job performance among common selection methods. For a small team: pick the three to five skills that matter most, write two questions for each, describe what a weak, good and excellent answer sounds like, score on your own, then decide together.
Most small businesses interview the way people make conversation: a friendly chat, questions that change from one candidate to the next and a decision based on how it "felt". The trouble is that feelings are easily swayed by confidence, a shared college or a good first five minutes, and none of those tells you whether the person can do the job. A little structure fixes most of that without making the interview stiff.
Why unstructured interviews let you down
- You can't compare candidates. If each person answered different questions, you are comparing impressions, not answers.
- First impressions take over. Interviewers often decide in the first few minutes and spend the rest of the time confirming it.
- Confidence looks like competence. Fluent talkers do well in chats; quiet, capable people don't.
- Bias creeps in. Without a shared standard, "culture fit" can quietly mean "people like us".
Build a structured interview in 5 steps
- List the skills that matter. Take them from your job description: three to five things that separate a great hire from a poor one. For a customer support role, that might be problem solving, written communication, patience with difficult customers and reliability.
- Write two questions per skill. Use a mix of behavioural questions about the past ("Tell me about a time when…") and situational questions about the future ("What would you do if…"). Past behaviour is good evidence; situations work well for freshers.
- Agree a scoring guide. For each question, write a sentence describing a 1 (weak), 3 (good) and 5 (excellent) answer. This is the part that makes the interview fair.
- Run every interview the same way. Same questions, same order, similar time. You can ask follow-ups ("What did you do next?"), but don't swap questions.
- Score alone, then decide together. Each interviewer scores straight after the interview, before talking to anyone. Then compare scores and discuss the differences using the notes.
Question bank by skill
| Skill | Behavioural question | Situational question |
|---|---|---|
| Ownership | Tell me about a time something went wrong in your work. What did you do? | You realise on Friday evening that an order you handled went to the wrong customer. What do you do? |
| Problem solving | Describe a problem at work or college you solved in a new way. | A customer says the product you delivered doesn't work, but it works when you test it. How do you handle it? |
| Communication | Tell me about a time you had to explain something complicated to someone new to it. | How would you explain our product to a shop owner in two minutes? |
| Customer handling | Tell me about the most difficult customer you have dealt with. | A customer is shouting on the phone about a late delivery. What do you say first? |
| Learning ability | Tell me about something you had to learn quickly. How did you go about it? | On your first day you are given a tool you have never used. What do you do? |
| Sales | Walk me through a deal you won. What made the customer say yes? | A prospect says our price is 20% higher than a competitor's. How do you respond? |
Sample scorecard with anchors
Here is one question with its scoring guide. Write one like it for every question you ask.
Question: "Tell me about a time something went wrong in your work. What did you do?" Skill: Ownership.
| Score | What the answer sounds like |
|---|---|
| 1: Weak | No real example, or the problem was entirely someone else's fault. No action from the candidate. |
| 3: Good | A relevant example with clear steps the candidate took. The outcome is described but not measured. |
| 5: Excellent | A specific situation, actions the candidate personally took, a clear result and what they changed afterwards so it wouldn't happen again. |
Add up the scores per skill, but don't let a total hide a dealbreaker. A candidate who scores 1 on a must-have skill is usually a no, however well they did elsewhere.
Add a short work sample
Interviews tell you how someone talks about work. A short task shows you the work itself. The same 2022 research found that work samples and job knowledge tests also predict performance well. Keep it short and relevant:
- Accounts: reconcile 15 transactions in a spreadsheet (30 minutes).
- Customer support: reply in writing to three real-looking customer complaints (30 minutes).
- Sales: a five-minute role-play call with you as the customer.
- Developer: fix a small bug or add a small feature in a prepared project (60 minutes).
Pay for anything that takes more than an hour or two, and never use a candidate's work in your business unless you have paid for it and agreed to it.
Running the interview
- Open with the plan. "I'll ask you eight questions about past work and a few scenarios, then you can ask me anything." People answer better when they know what's coming.
- Take notes during the interview on what the candidate actually said, not your opinion of it.
- Ask follow-ups for detail: "What exactly did you do?", "What was the result?", "What would you do differently?"
- Leave ten minutes for their questions. Good questions are a signal too.
- Tell them when they will hear back, and keep that promise.
Interviewing in India: practical tips
- Use a phone or video first round to save candidates a long commute for a 20-minute conversation.
- Cut no-shows. Confirm the slot by email or WhatsApp the day before, share the address and a contact number, and keep the process to two or three rounds.
- Interview in the language the job needs. If the role doesn't need fluent English, let candidates answer in Hindi or the local language.
- Stay away from personal questions. Marital status, plans for children, religion, caste, family background and age have nothing to do with the job. Asking about them puts good candidates off and can lead to unfair decisions.
- Share the salary range early, so neither of you wastes time.
Make the decision fairly
- Each interviewer submits scores and notes before any discussion.
- Discuss the skills where scores differ by two or more points, using the notes as evidence.
- Check every finalist against your must-haves.
- Write down in a line or two why you chose the person you chose. It keeps the decision honest and helps the next hire.
- Tell every candidate you interviewed what you decided. A short, polite rejection protects your reputation.
Start with a clear brief using our guide on how to write a job description, see how to shortlist freshers if you are hiring entry-level, and use the first employee checklist for everything after the offer. When you are ready, post a job free on Workafy.
Sources
- Sackett, P. R., Zhang, C., Berry, C. M. and Lievens, F. (2022). Revisiting meta-analytic estimates of validity in personnel selection. Journal of Applied Psychology, 107, 2040 to 2068.
Frequently asked questions
What is a structured interview?
An interview where every candidate for a role is asked the same job-related questions, in the same order, and each answer is scored against a rating guide agreed before the interviews begin.
Are structured interviews better than normal interviews?
Yes, for predicting how someone will do the job. A 2022 review of decades of hiring research by Sackett and colleagues found structured interviews to be the strongest single predictor of job performance among the methods it compared.
How many questions should a structured interview have?
Six to ten questions fit a 45-minute interview: about two for each of the three to five skills that matter most, with time for follow-up questions and the candidate's own questions.
What should I not ask in a job interview in India?
Avoid questions about marital status, pregnancy or plans for children, religion, caste, family background and age. They are not about the job, they put candidates off, and they can lead to unfair decisions.
