Structured interview questions: examples, templates and how to write them

In a structured interview, every candidate for a role gets the same questions in the same order. Every answer is scored on the same rubric. The interviewer does not make things up as they go. The scoring rules are set before the first interview, not after.

This sounds obvious, but most interviews are still unstructured. The interviewer looks at the resume five minutes before the call and asks whatever comes to mind. Afterwards they write a vague note like "good communicator, seems smart." Hiring decisions then rest on gut feel and the interviewer's mood. They can even rest on whether the candidate went to the same college as the interviewer.

Structured interviews do not have to feel stiff. The questions are fixed, but the interviewer (or the AI) can ask follow-up questions based on the candidate's answers. The structure lives in the rubric and the question list. The conversation itself can stay natural.

Research keeps showing that structured interviews predict job performance 2-3 times better than unstructured ones. The reason is simple. When every candidate answers the same questions on the same rubric, you compare like with like. When every interview is different, you are comparing feelings.

Structured interviews also reduce bias. In an unstructured interview, the interviewer's first impression shapes every question that follows. That impression often comes from looks, accent, or which college someone went to. In a structured interview, the rubric makes the interviewer score what the candidate actually said.

For high-volume hiring teams, structure fixes the problem of different interviewers using different standards. Say 5 interviewers run phone screens for the same role. Unstructured interviews give very different results. One interviewer's "strong yes" is another's "maybe." A shared rubric and question list puts everyone on the same page.

Start with the job, not the questions. List the 4-6 skills or traits that really predict success in the role. For a sales role, these might be handling objections, asking good discovery questions, keeping a tidy pipeline, product knowledge, and resilience. For a support role, they might be empathy, fast troubleshooting, clear writing, and following the process.

For each skill, write 1-2 questions that make the candidate show it. Use behavioral questions ("Tell me about a time when...") for roles that need experience. Use situational questions ("What would you do if...") for entry-level roles, where candidates may not have direct experience. Avoid yes/no questions. Also avoid made-up scenarios that invite textbook answers.

Then build the rubric. For each question, describe what a 1, 3, and 5 answer looks like on a 5-point scale. A "5" on handling objections might be: "The candidate describes a real objection, explains how they handled it, and shares the result with numbers." A "1" might be: "The candidate cannot recall a real example or gives a generic answer." Write these examples before the first interview, not after.

A rubric without example answers is useless. "Rate communication skills 1-5" tells the interviewer nothing, so they fall back on gut feel. Instead, describe each score. For example: "1 = the candidate struggles to form clear sentences. 3 = the candidate speaks clearly but is vague. 5 = the candidate is clear and brief, and backs up points with real examples."

Keep the rubric in front of the interviewer during the interview. They should score as the candidate answers, not try to remember everything at the end. Memory after an interview favors the last few minutes and the most emotional moments.

Make sure all interviewers score the same way. Before a hiring drive, hold a practice session. Have every interviewer score the same 2-3 sample answers, then talk through where they disagree. This takes 30 minutes and saves weeks of uneven scoring.

Sales (relationship-based): "Walk me through a deal you lost. What happened, what did you learn, and what would you do differently?" Follow-up: "How did you talk to the prospect once you saw the deal was slipping?" This tests resilience, self-awareness, and how well they communicate under pressure.

Engineering: "Describe a technical decision you later regretted. What was the situation, what did you decide, and what happened as a result?" Follow-up: "How did you tell your team once you realized the mistake?" This tests judgment, ownership, and teamwork.

Customer support: "Tell me about a time a customer was upset and you could not give them what they wanted. What did you do?" Follow-up: "How did the customer respond, and what would you change if you could do it again?" This tests empathy, calming people down, and following a process.

The hardest part of structured interviewing is sticking to it. Human interviewers drift. They skip questions, forget the rubric, go off topic, or run out of time. An AI interviewer does not drift. It asks every question and follows up on what the candidate actually said. It scores every answer on the same rubric.

With Goodfit, you set the skills and the rubric once. The AI writes the questions and runs the interview in the candidate's preferred language, from 14 languages. You get a scorecard that quotes the transcript for each score. Every candidate gets the same questions and rubric, whether they interview at 9 AM or midnight.

This does not replace human interviews for final rounds. It replaces the unplanned phone screen. That is the stage where structure matters most and is most often missing. When the hiring manager gets on a call, they already have a scorecard. They can spend the time on the deeper questions that need a person.