Behavioural questions — the ones that start 'tell me about a time…' — are the backbone of most UK interviews, and STAR (Situation, Task, Action, Result) is the shape trained interviewers listen for when they score your answer. If you want the structure itself explained one letter at a time, our STAR structure guide covers that in depth. This page is the other half of the preparation: the question bank.
Below are nine behavioural questions employers actually ask, five of them with a fully worked example answer and marking guidance against four criteria. The working pattern: read the answer, read the marking, then rebuild the answer from your own experience using the same skeleton. An example you merely admire does nothing for you in the room.
The marking lens is deliberately consistent across all five answers — structure, composure under follow-up, connection to the role, and concreteness of evidence. Those are the four things an interviewer is actually weighing while you talk, whether or not their scorecard names them.
Practise these questions out loud with a live AI interviewer — free. Start with Try Me
How the marking guidance works
Each model answer below is marked against the four criteria a live aurate session scores:
See how a full session is scored
aurate is a practice tool. Marking guidance describes what strong practice answers show — it isn't an employability assessment.
Why it's asked: The most common behavioural opener in graduate and early-career interviews. The trap is narrating the team’s achievement instead of your contribution to it — interviewers can only score what you personally did.
In my final year, five of us were building a group project — a demand forecast for a local food bank — and two weeks in, our data collection had stalled because everyone was waiting for everyone else.
Nobody was leading, so I proposed we each own one strand and that I coordinate: my job became keeping five strands compatible rather than doing all five. I set up a shared tracker with three columns — done, stuck, next — and a 20-minute Monday call where the only agenda item was 'stuck'. When our survey strand fell behind because the venue cancelled, I paired its owner with our strongest analyst for a week and moved my own strand's deadline to cover the gap.
We submitted on time with all five strands integrated, the food bank used the forecast to plan its December stock, and the group asked me to coordinate the follow-on project the next term.
Marking guide
Why it's asked: Interviewers are testing how you create time — re-scoping, sequencing, negotiating — rather than how much of your evening you are willing to donate. An answer built on working harder scores lower than an answer built on deciding better.
Our client moved a product launch forward by three weeks, which pulled the compliance review I owned from six weeks to three. I had to deliver a review the sign-off committee would accept first time — a rejected review would have killed the new date entirely.
I re-scoped before I re-planned. I mapped the 14 review areas against the last two years of findings, took the six areas with clean histories down to sampling checks, and kept full depth on the eight with past issues. I told the committee chair exactly what I had descoped and why — in writing, before starting — so the risk decision was made early and made by the right person, not discovered at sign-off. Then I blocked the three weeks into review sprints with a buffer day in each.
The review went to committee two days early and passed first time, with the descoping note attached as an annex. The launch made its new date.
Marking guide
Two marked answers in — here is the gap
Reading a marked answer and delivering one are different skills. A live aurate session asks you questions like these out loud, pushes back on the weak beats, and marks you on the same four criteria used above. Two free sessions. No credit card.
Try it freeWhy it's asked: A composure-and-diagnosis question. Weak answers make the other person the villain; strong answers find the system behind the behaviour and fix that. Interviewers also quietly note how you talk about difficult people — you are describing a future colleague’s experience of you.
An account I managed had a client lead who escalated over my head roughly weekly — usually before I had a chance to respond at all. My job was to keep the relationship working, and to stop my director's inbox being the service desk.
Rather than matching the escalations, I asked her for 30 minutes and opened with a question instead of a defence: what would she need to see to trust the process? It turned out a previous supplier had quietly sat on two failures, and the escalations were her insurance policy. We agreed a weekly one-page status note — everything amber or red at the top, in her format, every Friday — and a commitment from me that she would hear bad news from me before she heard it from anyone else.
Escalations stopped within a month. Eight months later she was the reference client our sales team used in two new pitches.
Marking guide
Why it's asked: Failure questions test ownership under mild shame — interviewers probe for deflection and score its absence. The strongest answers name the real mistake (including the uncomfortable part), fix the harm fast, and change the system rather than promising vigilance.
I once shipped a pricing update that was wrong for one customer segment — students on a legacy tariff — because I had tested against the current tariff table and did not know the legacy one existed.
When support tickets flagged it, I owned it in my first message to my manager, no cushioning, and we reversed the update within the hour. I wrote the refund script myself and stayed until all 212 affected accounts were credited that evening. The part I am least proud of: a colleague had mentioned legacy tariffs in passing a month earlier, and I had not followed it up. So I built the fix around that failure specifically — a pre-release checklist item that names every tariff table in production, generated from the database rather than from anyone's memory.
The refunds completed same-day with an explanation to every affected student, and the checklist caught a similar gap on someone else's release four months later.
Marking guide
Why it's asked: An influence-without-authority question, common for mid-level and stepping-up candidates. Interviewers listen for the method — evidence, framing, timing — and for respect: answers that quietly humiliate the senior person fail a test the candidate did not know was running.
Our head of operations planned to fix a missed-appointment problem by doubling reminder messages, and I believed the plan would spend money making the problem worse. As the analyst on the service, I wanted the decision made on evidence — which meant changing a senior manager's mind with no authority over the decision.
I did not argue in the meeting. I asked for two weeks and ran the numbers: missed appointments clustered in one clinic, where the booking line took most of an hour to answer — people were not forgetting, they were failing to rebook. I put a one-page note in front of him that led with his goal rather than my objection — 'the fastest route to fewer missed appointments' — showing that reminders addressed the smaller driver and answering the booking line inside five minutes addressed the larger one, at lower cost. Then I offered a two-clinic trial, so the idea could lose safely.
He ran the trial, the booking-line clinic improved most, and the reminder budget went to staffing the line instead. He later asked me to pressure-test two other plans the same way.
Marking guide
Why it's asked: Interviewers want your learning method, not your enthusiasm for learning: how you found the shortest path (a person, not a manual), how you tested your new understanding before relying on it, and what you produced with it under time pressure.
Why it's asked: A working-relationships question wearing conflict clothing. Strong answers disagree about the work (not the person), show you understood their position well enough to state it fairly, and end with the relationship intact — whichever side turned out to be right.
Why it's asked: Increasingly common for both graduate schemes and internal promotions. Leadership here means someone followed you voluntarily: you saw a gap, proposed a direction, and others adopted it. Answers about being put in charge miss the point of the question.
Why it's asked: The test is whether you prioritised deliberately or just worked faster. Name the criterion you used to rank the work, the thing you consciously deprioritised, and how you told whoever was affected — that last beat is the one most answers are missing.
Six to eight, chosen so that between them they cover the competency families most interviews draw from: teamwork, pressure, conflict, failure, influence and initiative. Match them to the competencies in the job advert first — that list is the closest thing to seeing the questions in advance.
Yes, if you re-angle it honestly — the same project can evidence teamwork in one answer and decision-making in another, provided the Action section changes to match what was asked. Avoid reusing a story twice in the same interview: panels notice, and it reads as a thin evidence base.
STARR adds a final Reflection beat — what you learned and what you would do differently. Some public-sector and NHS interviews explicitly listen for it. A one-sentence reflection strengthens most answers even where it is not required; just do not let it soften a strong result into an apology.
Around two minutes spoken. As a rough internal budget: two sentences of Situation, one of Task, the majority on Action, and a closing Result with something checkable in it. If your answers keep running long, the Situation section is almost always where the time is leaking.
Use it — with the ending it actually had. Interviewers rate honest accounts of imperfect outcomes above suspiciously frictionless wins, because the judgement and the recovery are the evidence. Close with what changed as a result, which is a real Result even when the project itself fell short.
Two free sessions. No credit card.