"Tell me about a time you..." and then the room goes quiet#
You know the question is coming. Somewhere between the small talk and the salary chat, the interviewer glances at their notes and says: "Tell me about a time you dealt with a conflict in a team." You've prepared for this exact moment. You have a story. And yet what comes out sounds like you're reading your own CV back to a stranger.
That's the odd paradox of the competency interview. Over-preparation, done badly, produces answers that sound written rather than remembered. Winging it produces rambling that misses the point. The answer that actually works sits between the two: structured enough to be clear, loose enough to sound like something that really happened to you.
What a competency interview is really testing#
A competency-based interview, sometimes called a behavioural interview, asks you to describe specific past situations rather than hypothetical ones. Instead of "how would you handle a difficult client," you get "tell me about a time a client was difficult, and what you did." The logic, borrowed from occupational psychology, is that how you behaved under pressure once predicts how you'll behave again better than how you imagine you'd behave.
The approach traces back to psychologist Tom Janz, whose 1982 study in the Journal of Applied Psychology found interviews built around real past behaviour outperformed free-flowing conversational ones. It held up: a widely cited 1998 meta-analysis by Frank Schmidt and John Hunter in Psychological Bulletin found structured interviews considerably more predictive of job performance than unstructured ones, and a 2014 Personnel Psychology review by Levashina and colleagues reached the same conclusion.
STAR is the framework most UK career services teach for answering these questions: Situation (the context), Task (what you were responsible for), Action (what you did), and Result (what happened). Prospects and TARGETjobs both recommend it for the same reason: it stops answers drifting into vague self-praise and forces you to show, not tell. The trouble starts once students learn the acronym and turn it into a script rather than a shape. Interviewers, who sit through dozens of these a week, can tell the difference instantly.
Picking a story before you worry about structure#
Most rehearsed-sounding answers go wrong before the candidate says a word, at the point they chose which story to tell. A common mistake is reaching for the biggest, most impressive-sounding achievement regardless of what's being asked. Force a deadline story to answer a conflict question and you'll spend the answer awkwardly bending it into the wrong shape, which is exactly what produces that stilted delivery.
Build a small bank of five or six genuine experiences, drawn from part-time jobs, society committees, group coursework, sport, or volunteering, and know each well enough to answer several competencies from it. A single messy group project can usually supply a teamwork story, a conflict story, and a time-management story, depending which part you emphasise. The Institute of Student Employers, which represents most major UK graduate recruiters, notes that competency questions remain core to graduate assessment because they generalise across roles. Choosing a story that genuinely fits the question, rather than the most flattering one you have, is the single biggest lever most students never pull.
Why rehearsed answers sound rehearsed, and how to loosen yours up#
Rehearsed answers have a particular texture: evenly paced, oddly formal, built with mechanical precision, "the situation was... the task was... the action I took was..." Real memories don't come out like that. They arrive slightly out of order, with an unnecessary detail or two, in language that sounds like speech rather than a report.
The fix isn't to prepare less, it's to prepare differently. Memorise the shape of the story, not the sentences: what was going on, what you were meant to do, the two or three things you actually did, and what came of it. Say it out loud in different words each time, ideally to different people, so no single phrasing sets like concrete. Tell it slightly differently to a flatmate on Tuesday and a careers adviser on Thursday, and it comes out naturally in the interview too.
It also helps to let some genuine texture back in: a moment of doubt, a decision that didn't quite work at first, someone else's reaction. Interviewers listen for specifics because they're hard to fabricate on the spot. A messy, particular detail convinces an assessor you're recalling a real event far more than a polished sentence does.
The same story, told two ways#
Take an ordinary example: a coursework group where one member goes quiet two weeks before a deadline. Told mechanically: "The situation was a group project with an unequal workload. The task was to complete the deliverable on time. The action I took was messaging the team and reallocating tasks. The result was we submitted on time and got a good mark." Technically STAR-shaped, and forgettable. It could belong to anyone.
Told as something that actually happened: "We were three weeks into a five-person project when one of the team stopped replying, no messages, missed calls. I gave it a couple of days assuming he was ill, then messaged him directly rather than in the group chat, partly so it didn't feel like a pile-on. He'd fallen behind on another module and panicked. Two of us split his section between us, I took the data slides, and I checked in with him again before submission so he still felt part of it. We got a 68, and he came back for the next group project, which mattered more to me than the mark did."
Both cover the same Situation, Task, Action and Result. The second has a specific number, a decision explained rather than stated (messaging him directly, not the group chat), and an ending that isn't the mark. Those are the details a script never includes, because they weren't in the script.
What each competency question is really testing#
Different question categories map onto different things an assessor is scoring, even when they sound similar. Knowing what's being measured helps you choose the right emphasis.
| Question type | What's being tested | Emphasise in Action/Result |
|---|---|---|
| Working in a team | Collaboration, sharing credit | Your specific contribution, not "we" |
| Handling conflict | Tact, emotional control | How you resolved it directly |
| A mistake you made | Self-awareness, accountability | What changed afterwards |
| Leading something | Initiative, delegation | Choices you made, titled or not |
| Working under pressure | Prioritisation, composure | How you decided what mattered |
| Influencing someone | Persuasion, resilience | The specific approach that worked |
Notice the pattern: weak answers stay in "we" language with vague outcomes, strong ones narrow to "I" and a concrete result. Recruiters can't score a team's behaviour, only yours.
When you don't have an obvious story for the question#
Students often freeze because they assume every competency question needs a dramatic, high-stakes example. It doesn't. A "time you managed conflicting priorities" can be juggling a lab report deadline against a part-time shift, not a crisis at a Fortune 500 internship. Assessors calibrate to your stage of life; a first-year interviewing for a spring insight scheme isn't expected to produce boardroom stories.
If nothing comes to mind, work backwards from your existing bank rather than hunting for a new story under pressure. Ask which experience contains even a partial match, then be honest about scaling the framing: "It wasn't a formal leadership role, but on this project I ended up coordinating..." is a credible opening. TARGETjobs' guidance on competency interviews makes the same point: assessors want evidence of the underlying skill, not the scale of the achievement. If you truly have nothing, say so and pivot to the closest example. Interviewers who hear dozens of these a week are usually better at spotting invention than candidates assume.
Handling the follow-up questions that catch people out#
Well-prepared candidates often stumble not on the original question but on what comes after it. "What would you do differently?" exists to check whether a story is real or recited. A rehearsed answer has no more depth to give; push a scripted candidate one layer deeper and it collapses into repetition.
The way through this is to think about the honest answer to those follow-ups before the interview, not just the headline story. What would you genuinely do differently? What's the awkward bit you're tempted to leave out? CIPD's research on selection practice notes that skilled interviewers deliberately probe past the first answer, because a polished, one-pass response is the easiest thing to fake. Treat the follow-up as the real test, and the STAR answer as just the setup.
Common questions about STAR interviews#
Do I need a completely different story for every competency?#
No. Most strong candidates rely on five or six well-understood experiences, each covering two or three competencies depending on the angle. Depth in a small set beats a shallow answer for every possible question.
How long should a STAR answer be?#
Roughly ninety seconds to two minutes, with Situation and Task kept brief and most of the time spent on Action and Result. Still setting the scene after a minute means you've over-explained the context.
What if my best example is from university, not a job?#
That's normal, especially for first and second-years. Group coursework, societies, sport captaincy, and part-time retail or hospitality work all generate valid evidence. Assessors weigh examples against your career stage, not a graduate's five years of work history.
Should I write out and memorise my answers word for word?#
Memorise the structure and key facts, not the sentences. Word-for-word scripts produce exactly the flat, recited tone interviewers notice immediately. Practise telling the same story slightly differently each time instead.
Does STAR still apply in AI-scored or recorded video interviews?#
Yes, arguably more so. One-way video interview platforms, now used by a good share of UK graduate recruiters according to Institute of Student Employers surveys, tend to score for structure and specificity even more literally than a human panel.
Sounding like yourself is the real skill#
The STAR framework was never meant to be a script. It's scaffolding, there to stop you rambling, not to replace your own voice. The students who come across best in competency interviews aren't the ones with the most polished paragraphs, but the ones who know their own stories well enough to tell them slightly differently every time, including under pressure. Build the bank of stories now, before you need them, and the interview stops being a memory test and starts being a conversation you're equipped to have.
