How to Run Structured Interviews

A structured interview means every candidate for the same role gets asked the same questions, in the same order, and is evaluated using the same scoring criteria.

Compare this to an unstructured interview, where the interviewer asks whatever comes to mind, follows tangents, and makes a gut-feel decision at the end. Research consistently shows that unstructured interviews are only slightly better than random chance at predicting job performance.

Structured interviews are 2x more predictive of job performance than unstructured ones. Here is why:

• Fair comparison — When every candidate answers the same questions, you are comparing apples to apples instead of apples to oranges
• Reduced bias — Consistent questions and scoring reduce the influence of first impressions, personal similarity, and interviewer mood
• Better data — Scorecards create a record you can discuss objectively, rather than relying on vague impressions
• Legal protection — Standardized processes are easier to defend if a hiring decision is ever questioned
• Interviewer calibration — When everyone uses the same rubric, you can identify interviewers who consistently rate too high or too low

Despite these benefits, most small companies still wing it. The investment to switch is small — a few hours upfront — and the improvement in hiring quality is dramatic.

Good structured questions are tied to specific competencies required for the role. Start by identifying 4-6 competencies, then write 1-2 questions per competency.

Types of Questions

• Behavioral questions — Ask candidates to describe past situations. "Tell me about a time when..." These predict future behavior based on past behavior
• Situational questions — Present hypothetical scenarios. "What would you do if..." These test judgment and problem-solving approach
• Technical questions — Evaluate specific skills or knowledge. Best used for roles with clear technical requirements

Writing Effective Behavioral Questions

Use the STAR format as a guide (Situation, Task, Action, Result):

• Bad: "Are you good at teamwork?"
• Good: "Describe a project where you had to collaborate with someone you disagreed with. What was the situation, what did you do, and what was the outcome?"

Example Questions by Competency

Competency	Example Question
Problem-solving	Tell me about a time you faced a problem with no obvious solution. How did you approach it?
Communication	Describe a situation where you had to explain something complex to a non-technical audience. How did you do it?
Leadership	Tell me about a time you had to lead a team through an uncertain or changing situation. What happened?
Adaptability	Give me an example of when priorities shifted suddenly. How did you handle it?
Initiative	Describe a time you identified an opportunity or problem before anyone else did. What action did you take?

Write questions in advance and share them with all interviewers so everyone evaluates the same competencies.

A scorecard turns subjective impressions into structured data. Without one, debriefs devolve into "I liked them" versus "I did not get a good feeling" — neither of which is useful.

Scorecard Structure

For each competency, the scorecard should include:

• The competency name (e.g., "Problem-Solving")
• The question asked
• A rating scale (1-5 is standard)
• Rating definitions so everyone interprets the scale the same way
• Evidence field — Specific examples from the candidate's answer that justify the rating

Rating Scale Example

Rating	Definition
5 — Exceptional	Response demonstrates clear mastery. Gave specific, detailed examples with measurable outcomes
4 — Strong	Solid response with good examples. Clearly meets the bar for this role
3 — Adequate	Meets minimum expectations. Examples were relevant but lacked depth or specificity
2 — Below expectations	Response showed gaps. Examples were vague, incomplete, or only partially relevant
1 — Significant concern	Unable to provide relevant examples or demonstrated poor judgment

The Evidence Rule

Require interviewers to write at least one specific observation for every rating. "Scored 4 on communication" means nothing. "Scored 4 — clearly explained their data migration strategy to a non-technical stakeholder, confirmed understanding, and adapted when questions came up" — that is useful in a debrief.

Here is how to run a structured interview that feels natural to the candidate while giving you the data you need:

Before the Interview (5 minutes)

• Review the candidate's resume and any screening notes
• Have your questions and scorecard ready (printed or on screen)
• Clear your mind of the previous candidate's interview — each person gets a fresh evaluation

Opening (5 minutes)

• Greet the candidate warmly. Introduce yourself and your role
• Explain the interview structure: "I have [X] questions I will ask, and I will leave time for your questions at the end"
• Let them know you will be taking notes — it is a sign of thoroughness, not disinterest

Core Questions (30-40 minutes)

• Ask each question as written. Do not rephrase or skip based on how the conversation is going
• Listen actively. Use follow-up probes if needed: "Can you be more specific?" or "What was the result?"
• Take notes on specific examples and behaviors, not your impressions
• Do not evaluate while interviewing — just collect data. Score the candidate after they leave

Candidate Questions (10 minutes)

• Leave genuine time for the candidate to ask questions. This is part of the candidate experience
• Answer honestly. Candidates can tell when you are selling versus being real

After the Interview (10 minutes)

• Complete your scorecard immediately. Memory fades fast, and you want accurate ratings
• Do not discuss your evaluation with other interviewers until everyone has submitted their scores independently

The debrief is where structured interviews pay off. Instead of a free-for-all debate, you have data to work with.

Debrief Format

1. Ensure all scorecards are submitted before the meeting starts. This prevents anchoring — where one person's opinion influences everyone else
2. Review scores by competency, not by interviewer. Look at how each candidate scored on problem-solving, then communication, etc.
3. Discuss disagreements. If one interviewer gave a 2 and another gave a 5, explore the evidence behind each rating
4. Focus on evidence, not feelings. Redirect comments like "I just did not click with them" to "What specific answer concerned you?"
5. Make a decision. Use a clear framework: candidates who score above your threshold on all competencies get an offer. Below threshold on any critical competency means no offer

Common Debrief Pitfalls

• Halo effect — One strong answer makes the interviewer rate everything higher. The scorecard by competency format prevents this
• Recency bias — The last candidate interviewed gets an unfair advantage because they are freshest in memory. Scorecards filled out immediately after each interview fix this
• Consensus pressure — Junior team members defer to senior ones. Collect scores independently to get honest assessments

You do not need to overhaul your entire process overnight. Here is a practical rollout plan:

Week 1: Define Competencies

For each open role, identify 4-6 competencies that predict success. Involve the hiring manager and one team member. Keep it simple — these do not need to be perfect on the first try.

Week 2: Write Questions and Scorecards

Write 1-2 questions per competency. Define your rating scale. Create a scorecard template that interviewers will use. This can be a Google Doc, a form, or a feature in your ATS.

Week 3: Train Your Interviewers

Run a 30-minute training session covering:

• Why structured interviews matter (share the research)
• How to ask questions consistently without sounding robotic
• How to take notes and score candidates
• How the debrief will work

Week 4: Run Your First Structured Interviews

Apply the new process to your next round of candidates. Collect feedback from interviewers on what worked and what felt awkward. Iterate.

Ongoing: Review and Improve

After every 5-10 hires, review your questions and scorecards. Are certain questions not producing useful signal? Replace them. Are interviewers calibrated? Compare their ratings to actual hire performance.

BorovaHR supports structured interviews with built-in scorecards, team feedback collection, and debrief tools — so your interviewers can focus on the conversation while the system handles the process.

Do structured interviews feel robotic to candidates?

Only if you run them badly. The structure is for your benefit — the candidate should experience a natural conversation. You can still build rapport, respond to their answers, and ask follow-up questions. The structure just ensures you cover the same ground with every candidate.

How many questions should a structured interview have?

6-10 questions for a 45-60 minute interview. This gives enough time for candidates to provide detailed answers and for you to ask follow-ups. Rushing through 20 questions produces shallow responses.

Can I adapt questions based on the candidate's background?

Your core questions should stay the same for fair comparison. But you can add 1-2 follow-up questions that are specific to the candidate's experience. Just make sure the core questions are always asked.

What if the candidate's answer does not fit the STAR format?

Prompt them gently: "Can you walk me through a specific example?" or "What was the outcome of that?" Most candidates need a nudge to provide structured responses, and that is fine.

How do I handle interviewers who resist structured interviews?

Share the data: structured interviews are 2x more predictive of job performance. Frame it as a tool that helps them make better decisions, not a constraint on their judgment. Once they see the debrief quality improve, resistance usually fades.

Should every role use the same questions?

No. Questions should be tied to role-specific competencies. A sales role and an engineering role need different questions. But the format — behavioral questions, consistent scoring, evidence-based ratings — stays the same across all roles.