Structured Behavioral Interview Questions: Examples by Competency

How to use this list

Structured behavioral interview questions only generate signal when paired with two things: (1) a small set of competencies you actually want to measure, and (2) behaviorally anchored rating scales for scoring. The questions below are templates, not a shopping list — pick one per competency for your role and design the rubric before you interview anyone.

For background on what "structured" really means and why it doubles predictive validity, see our design guide and the research summary.

Ownership / driving results

Question. "Tell me about a time you owned a project end-to-end. Walk me through how it started, what you actually did, and how it ended."

Probes.

• "Whose idea was the project originally?"
• "What did you decide to deprioritize to make it happen?"
• "What did the outcome look like, and what was your part in that outcome?"
• "What would you do differently if you ran it again?"

Strong answer signals. Specific decisions made, specific tradeoffs named, owns both successes and gaps in outcome.

Weak answer signals. Describes the team's outcome without their own contribution. Cannot name a specific tradeoff. "We" instead of "I" throughout.

Collaboration and conflict

Question. "Tell me about a time you disagreed with a peer about an important decision. How did it play out?"

Probes.

• "What was the disagreement specifically?"
• "What did the other person argue?"
• "How did you decide? Did your view prevail?"
• "Looking back, who was right?"

Strong answer signals. Can steelman the other side. Distinguishes between getting their way and being right. Names what they learned.

Weak answer signals. Vague conflict; everyone agreed in the end; cannot articulate the other person's position; positions the story as "I was obviously right."

Dealing with ambiguity

Question. "Tell me about a time you had to make progress on something with no clear requirements or no clear path forward."

Probes.

• "What was unclear specifically?"
• "What was the first concrete action you took?"
• "What did you decide to not do yet?"
• "How did you know when you had enough clarity to commit?"

Strong answer signals. Names the specific unknowns. Describes a hypothesis-driven approach. Distinguishes between exploration and execution phases.

Weak answer signals. Skips ahead to the outcome. "I just figured it out." No reflection on the ambiguity itself.

Mentorship and growing others

Question. "Tell me about someone whose career you have meaningfully influenced. What did you actually do, and where are they now?"

Probes.

• "How did you decide what they needed?"
• "Walk me through a specific moment of feedback or coaching you gave."
• "What did they push back on?"
• "What has their progression looked like since?"

Strong answer signals. Specific person, specific moment of feedback, can describe what the mentee actually needed (not what the candidate liked giving). Knows where the mentee is today.

Weak answer signals. Vague "I always try to mentor." No named person. Confuses mentorship with delegation.

Handling a high-stakes failure

Question. "Tell me about a project or decision that did not go well, and what you did about it."

Probes.

• "What went wrong specifically?"
• "When did you first notice things were off?"
• "What did you do once you noticed?"
• "What did you take away from it?"

Strong answer signals. Owns their part of the failure without spreading it across the team. Distinguishes what they would do differently from what was outside their control. Has a real lesson — not a "weakness as a strength" framing.

Weak answer signals. The failure was actually a success. Blames external factors entirely. Cannot name a specific takeaway.

Influencing without authority

Question. "Tell me about a time you needed to get something done that required convincing people outside your direct team or chain of command."

Probes.

• "Who specifically did you need to convince?"
• "What was their incentive to help (or not)?"
• "What did you try first? What did you try when that didn't work?"
• "What was the outcome for them, not just for your project?"

Strong answer signals. Thinks in terms of other people's incentives. Has more than one tactic. Describes a non-zero-sum outcome.

Weak answer signals. Just persistence ("I kept asking"). No model of the other person's motivations. Frames it as overcoming opposition rather than building alignment.

Rating each answer

For every question, write three anchored levels — 1, 3, 5 — before you interview the first candidate. The anchors should describe observable behavior in the answer, not abstract traits. A useful template:

• 1. Answer is vague, hypothetical, or about someone else's work. Cannot name specifics under probing.
• 3. Specific real situation. Owns their actions. Outcome is clear. Some reflection.
• 5. All of the above, plus: names a tradeoff, names what they would do differently, shows that the lesson influenced later behavior.

Score each dimension separately. Resist the urge to give one global "this candidate was good" rating — that is exactly the unstructured failure mode.

How ClarityHire helps

The platform ships role-specific question banks with built-in probes and anchored rubrics, and locks each interviewer's score before the debrief to prevent groupthink. The scorecard template is the same backbone for every interviewer, every candidate — which is the whole point of the format.