Free Tool — No Signup
Behavioural questions that get past rehearsed answers
Pick the competencies you want to assess. Get STAR-format questions, follow-up probes, and red flags to listen for — in seconds.
Built by an organisational psychologist. Not a question dump — a structured interview guide for one candidate.
Pick competencies
Choose 1–6 competencies you want to assess in this interview.
Get a complete guide
Three angled questions per competency, STAR follow-up probes, red flags, and a calibration note.
Print, copy, or save
Take a clean printout to the interview, copy to your notes app, or save it for next time.
Why STAR?
STAR — Situation, Task, Action, Result — is the gold standard for behavioural interviewing because it forces specificity. Candidates can't get away with hypotheticals or rehearsed soundbites; they have to describe a real event, what they actually did, and what happened.
The decades of research on structured behavioural interviewing show it predicts job performance roughly twice as well as an unstructured chat. The catch is that most interviewers ask the question, get a vague answer, and move on. The probes are where the value sits.
This tool gives you the question and the probes and the red flags. Use them.
Common questions
How many competencies should I assess in one interview? ›
Three to five. Fewer than three and you don't have enough signal; more than five and the interview gets shallow because you're racing the clock. A good 60-minute interview probes 4 competencies in real depth.
What if the candidate gives a hypothetical answer instead of a real one? ›
Politely redirect. "I'd like to hear about a specific time this actually happened to you." If they still can't give one, that itself is data — they may not have the experience they're claiming.
Should every interviewer ask the same questions? ›
Yes — for the same competency. If two interviewers are both assessing communication, they should ask comparable questions. Otherwise you're rating different things and pretending you're not.
Can I edit the generated questions? ›
Of course. Treat the generated set as a strong starting point — adapt the wording to your role, industry, and seniority level. The probes and red flags are competency-general, so they should hold up.
How does this tool work with the Scorecard Builder? ›
They share the same competency vocabulary. Build a scorecard with your panel, generate STAR questions for the same competencies here, and you have a complete structured-interview kit. The Scorecard Builder is one click away.
What are you assessing?
Pick the competencies you want to probe in this interview. We recommend 3–5 for a 60-minute conversation.
Click to toggle. 0 selected
Custom competency
Need something not on the list? Add a custom competency and we'll generate templated STAR questions for it.
Pick at least 1 competency to continue
Your interview guide
Edit the fields below — they'll appear at the top of your printout.
Saved guides
What is the STAR interview technique?
STAR stands for Situation, Task, Action, Result. It's a structured way of asking — and answering — behavioural interview questions. Instead of "are you a good leader?" (which produces useless self-assessment), STAR asks "tell me about a specific time you had to lead a team through a setback. What was the situation? What was your task? What did you personally do? What was the result?"
The premise is simple and well-evidenced: past behaviour is the best available predictor of future behaviour. People can rehearse generic answers about how they like to work. They struggle to fabricate the specifics of a situation that didn't happen — the names, the timeline, the unexpected obstacle, the thing they'd do differently next time. Done properly, STAR makes interview answers verifiable rather than performative.
How to use STAR questions in an interview
1. Ask for a specific incident, not a general approach
"How do you handle conflict?" gets you a politician's answer. "Tell me about a specific time in the last year when you had a serious disagreement with a colleague — what happened?" gets you the truth. Anchor every behavioural question to a real past event.
2. Probe for the four elements explicitly
Most candidates skip straight from situation to result. Slow them down. If they don't tell you what their specific task was, you don't know what they were responsible for. If they don't tell you what they personally did (rather than "we"), you don't know what they actually contributed. The probes built into this tool are designed to surface exactly that.
3. Listen for red flags as carefully as you listen for strengths
The most useful information in a STAR answer is often what the candidate didn't say. No mention of consulting anyone? Lone-wolf risk. Result described entirely in terms of their own promotion? Possible self-orientation. Couldn't name what they'd do differently? Limited self-awareness. Each question in this tool comes with a list of common red flags so you know what to listen out for.
4. Score against the scorecard, not against your gut
Behavioural answers should be scored against the rating descriptors in your interview scorecard, not against how much you liked the candidate. The whole point of a structured behavioural interview is to force the evidence to do the deciding.
STAR vs unstructured interviews — what the evidence actually says
Decades of selection research (Schmidt & Hunter, McDaniel, Huffcutt) consistently find that structured behavioural interviews predict job performance roughly twice as accurately as unstructured interviews — and reduce the influence of irrelevant factors like physical attractiveness, charisma, and similarity-to-interviewer bias. The cost is one of preparation: you have to know what you're looking for before the candidate walks in. This tool removes most of that preparation cost.
Common STAR interview mistakes
- Letting "we" answers slide. If a candidate describes a team success without ever using the word "I", you don't know what they did. Ask: "what was your specific contribution?"
- Asking too many questions. Three or four well-probed STAR questions per interview produces more signal than a dozen surface-level ones. Depth beats breadth.
- Asking hypothetical questions and calling them STAR. "What would you do if…" is not behavioural. It tests reasoning, not behaviour. Useful for some things, but not a substitute.
- Accepting an old example for a current competency. If the only example a candidate can give of "leading change" happened 12 years ago, that tells you something about the last 12 years.
- Not writing the answer down. Score and capture the evidence during the interview, not from memory afterwards.
How this fits with the rest of the suite
This generator is the third step in an evidence-based hiring workflow. Start with the JD Analyser — paste in your job description and it'll extract the competencies that actually matter. Then build a structured interview scorecard for those competencies. Finally, come here to generate the STAR questions, follow-up probes, and red flags you'll use in the interview itself. Three free tools, one workflow.
FAQ
How many STAR questions should I ask in one interview?
Three to five, fully probed, in a 45–60 minute interview. More than that and you're rushing the probes — which is where the actual evidence lives. Pick the competencies that matter most for the role and go deep on those.
Are these questions suitable for senior hires?
Yes. The competency framework covers individual contributors through to senior leadership. For executive roles, the same questions apply but expect — and probe for — answers that demonstrate strategic-level scope and accountability rather than tactical execution.
Can I customise the questions?
Yes. Use the generated questions as a starting point and adapt them to your role and company context. The probes and red flags are deliberately competency-level so they translate across industries.
Is my data sent anywhere?
No. Everything runs in your browser. No signup, no server, no cookies. Anonymous page-view analytics via Plausible — GDPR-compliant by design.