Structured Interview Questions: How to Write Them, With Examples by Role
How to write job-related questions every candidate answers the same way, with examples for sales, support, engineering and operations.
IntelliHire Team8 min read
Structured interview questions are a fixed set of job-related questions that every candidate for a role answers in the same order, each rated on the same scale. Because everyone gets the same prompts, you compare candidates on the evidence in their answers rather than on how well a conversation happened to flow.
Structured interview questions are a fixed set of job-related questions that every candidate for a role answers in the same order, with each answer rated on the same scale. Because everyone gets the same prompts, you compare candidates on the evidence in their answers rather than on how well a conversation happened to flow.
This guide covers how to write them, which question types work best, how to plan follow-up probes, and example questions for sales, support, engineering and operations roles, each paired with what a strong answer shows.
Key takeaways
- Write one main question for each competency on your scoring rubric.
- Use behavioral questions about past work and situational questions built from real scenarios in the role.
- Plan two or three follow-up probes per question and use the same ones with every candidate.
- Decide what a strong answer shows before the first interview, so scoring is about evidence, not impressions.
What Makes an Interview Structured
A good question on its own does not make an interview structured. The structure is the process around the questions. The US Office of Personnel Management's guide to structured interviews describes three features:
- Every candidate is asked the same questions in the same order.
- Every candidate is evaluated on a common rating scale.
- Interviewers agree in advance on what an acceptable answer looks like.
The same guide notes that structured interviews have demonstrated a high degree of reliability and validity, while unstructured interviews typically show low rating consistency among interviewers. In practice, structure is what lets you put two candidates side by side and explain why one moved forward.
How to Write Structured Interview Questions
Start with your rubric. If you do not have one yet, our guide to building an interview scoring rubric walks through choosing competencies and writing the rating scale. Then work through these steps:
- 1List four to six competencies the interview needs to test, written as observable behavior.
- 2Write one main question per competency. Each question should be about one thing, so the answer can be scored against one set of anchors.
- 3Use the language of the job. Build scenarios from situations people in the role actually face, not abstract puzzles.
- 4Write down what a strong answer shows before anyone is interviewed. This becomes the top of your rating scale.
- 5Plan two or three follow-up probes for each question.
- 6Pilot the questions on a colleague in a similar role. If they cannot give a clear answer, rewrite the question.
Behavioral and situational questions
Behavioral interview questions ask about the past: "Tell me about a time you…". They work well for experienced candidates because the answer is anchored in something that happened. Situational questions ask what the candidate would do in a realistic scenario: "A customer calls about…". They suit candidates with less directly relevant experience. Most structured interviews mix both, and both are scored against the same anchors.
Questions to leave out
Drop brainteasers, "what kind of animal would you be" questions and anything else you cannot connect to the work. Avoid questions that touch on age, family plans, religion, health or other personal characteristics. Your HR or legal team can confirm the rules where you hire.
Plan Follow-Up Probes in Advance
First answers are often short or general. Probes draw out the detail you need to score. The OPM guide advises using very similar probes with every candidate, so each person gets the same chance to give a complete answer. You can adjust the wording to fit what someone said, but not the meaning.
| Probe | What it draws out |
|---|---|
| "What was your part, specifically?" | Their own actions, separate from the team's |
| "What did you do next?" | How they responded when the first plan did not work |
| "How did you know it worked?" | Whether they checked or measured the result |
| "What would you do differently now?" | Reflection and what they learned |
Structured Interview Examples by Role
These structured interview examples each target one competency. The right-hand column describes what a strong answer shows; use it as the starting point for the top anchor on your rating scale. Swap in details from your own product, customers and tools.
Sales
| Competency | Question | A strong answer shows |
|---|---|---|
| Prospecting | Tell me about a deal you sourced yourself. How did you find it and get the first meeting? | A clear method, specific outreach steps and a reason that account was worth pursuing |
| Discovery | Walk me through how you found out what a recent prospect actually needed. | The questions they asked, what they learned and how it changed their pitch |
| Handling objections | Describe a time a buyer pushed back on price. What happened? | They explored the reason behind the objection before offering a discount, and can say how it ended |
| Pipeline discipline | How do you decide which deals to spend your time on at the start of a week? | A repeatable way to prioritize, and honesty about deals they chose to drop |
Customer support
| Competency | Question | A strong answer shows |
|---|---|---|
| Clear explanation | Tell me about a time you explained a complicated issue to a frustrated customer. | Plain language, a check that the customer understood and a stated outcome |
| Ownership | Describe a ticket you could not solve alone. What did you do? | Escalated with full context, kept the customer updated and followed it to the end |
| Prioritization (situational) | You have a long queue and a customer threatening to cancel. What do you handle first, and why? | Clear triage logic, honest timelines for the customer and knowing when to ask for help |
| Product feedback | Tell me about a recurring customer problem you reported to another team. | Spotted the pattern, gathered examples and followed up on what happened next |
Engineering
| Competency | Question | A strong answer shows |
|---|---|---|
| Debugging | Tell me about the hardest production bug you have tracked down. | A systematic approach, hypotheses tested in order and a change made to prevent a repeat |
| Technical trade-offs | Describe a design decision where you chose between two reasonable options. | Both options named, the criteria used, what they gave up and whether they would choose the same again |
| Estimating and scope (situational) | A feature you estimated at two weeks is half done at week three. What do you do? | Raises it early, offers scope options and tells stakeholders what changes |
| Collaboration | Tell me about a code review where you disagreed with a colleague. | Reasons given on both sides, real listening and a decision that kept the working relationship intact |
Operations
| Competency | Question | A strong answer shows |
|---|---|---|
| Process improvement | Tell me about a process you changed. How did you know it needed changing? | Evidence of the problem, input from the people doing the work and a before-and-after comparison |
| Planning | Walk me through how you planned for a busy period, such as a seasonal peak or a large rollout. | What the plan was based on, a backup plan and what they adjusted on the day |
| Supplier problems (situational) | A key supplier tells you a delivery will be a week late. What do you do? | Assesses the impact, considers alternatives and tells stakeholders early, with options |
| Problem response | Describe a time something went wrong on a shift or in a project you ran. | Quick containment, clear communication, then a root cause and a fix that stuck |
Running the Interview So the Structure Holds
Well-written questions can still drift in the room. A few habits keep every interview comparable:
- Tell the candidate how the interview works: how many questions, that you will take notes and that you may ask follow-ups.
- Ask each question as written, in the same order, and use only the planned probes.
- Note what the candidate said, not your impression of them.
- Score each answer as soon as the interview ends, before you talk to other interviewers.
- Leave time for the candidate's own questions, and do not score that part unless it is on the rubric.
Structured Questions in First-Round AI Interviews
The same principles apply when the first round is automated. Questions should map to the rubric, answers should be recorded, and a person should review the evidence. In IntelliHire, first-round AI voice interviews run around the clock with natural turn-taking, and each scorecard cites the transcript, so your team can read the candidate's actual answers before deciding who moves forward. See how AI interview software handles the first round.
For more on scoring and interview design, read our guide to building an interview scoring rubric or browse all posts on the blog.
Frequently asked questions
How many structured interview questions should I ask?
Plan one main question for each competency you are testing, which usually means four to six questions for an interview of about an hour. That leaves time for two or three follow-up probes per question and for the candidate's own questions at the end. More questions usually means shorter answers and less evidence for each one.
Can interviewers ask follow-up questions in a structured interview?
Yes. Planned follow-up probes are part of a good structured interview. The key is to agree on them in advance and use similar probes with every candidate, so each person has the same chance to give a complete answer. Probes should ask for more detail, not hint at the answer you want to hear.
Are behavioral or situational questions better?
Neither is better in every case. Behavioral questions ask what someone did in the past, which works well when candidates have relevant experience. Situational questions ask what they would do in a realistic scenario, which suits earlier-career candidates or career changers. Many teams use a mix and score both against the same rubric.
Should we share interview questions with candidates in advance?
Sharing the topics or competencies you will cover is a reasonable middle ground. It helps candidates prepare relevant examples and can make the interview less stressful, while your follow-up probes still test real depth. Whatever you decide, give every candidate for the role the same information at the same stage.
Sources
- 1.Structured Interviews: A Practical GuideU.S. Office of Personnel Management · accessed October 27, 2026
