A behavioural interview question asks you to describe something you have actually done, and the reliable way to answer one is the STAR method: set the Situation, state the Task you owned, walk through the Action you personally took, and close with a concrete Result. Prepare five to seven core stories from real work, keep each answer to roughly 90 seconds to two minutes, and say "I" rather than "we".
Why Behavioural Questions Matter
Employers believe past behaviour predicts future performance, and behavioural questions are how they collect the evidence. Prompts like "tell me about a challenge you overcame" are requests for a documented example, and the interviewer is listening for proof of problem-solving, resilience, ownership and teamwork.
It helps to know what happens on the other side of the table. In a structured process the interviewer is not simply forming an impression; they are filling in a scorecard with a rating per competency and a box for supporting evidence, and those notes get compared across candidates afterwards. That is why a warm, articulate answer with no specifics scores badly: there is nothing to write in the evidence box. You remember the rapport; the scorecard remembers only that you never said what you did.
The STAR Method, Component by Component
- Situation: Set the scene — the team, the constraint, the point in time. Two or three sentences, no more.
- Task: Explain what your responsibility was. Candidates skip this most often, and it is what separates you from the team around you.
- Action: Describe the specific steps you took, in sequence. Use "I", not "we".
- Result: Give the outcome and quantify it where you honestly can — a number, a timeframe, a decision that stuck, a process still in use.
The most common structural error is a lopsided answer: ninety seconds of situation, fifteen seconds of action. Use these proportions as a check.
| Component | Recommended share | What the interviewer is scoring | Most common failure |
|---|---|---|---|
| Situation | Around 15% | Whether you can frame context for someone with no background | A long preamble before anything happens |
| Task | Around 10% | What you personally were accountable for | Giving the team's goal instead of your own remit |
| Action | Around 55% | Your judgement, decisions and trade-offs | Weak verbs — coordinated, supported, was involved in |
| Result | Around 20% | Whether you changed something that can be verified | Ending on "and it went well" |
A Weak Answer and a STAR Answer
Take the prompt "tell me about a time you delivered under an unrealistic deadline". A weak answer sounds like this: "We had a demanding client and things got chaotic, but the team pulled together and got it over the line. I work well under pressure." Nothing there is scoreable — no context, no personal contribution, no outcome.
Here it is rebuilt as an illustrative STAR answer. Situation: the client moved a launch forward by three weeks, and the approval loop between design, legal and the client was taking about nine days per asset. Task: I owned the delivery schedule and had to hit the new date without cutting the legal review. Action: I mapped where each asset sat idle, found most of the delay was waiting on one reviewer, and proposed batching submissions twice a week rather than singly. I agreed a fixed 48-hour turnaround with legal in exchange for a guaranteed submission window. Result: the loop dropped from about nine days to three, we shipped on the earlier date, and the batching process was still in use when I left. Every sentence of that action is a decision you can be questioned about, and the result is a change in how the work happened.
Build a Story Bank, Not a Script
Prepare five to seven core stories that adapt to different questions, and practise delivering each in under two minutes. Do not write scripts — write skeletons of four or five bullets you can reshape around whatever is asked. Cover distinct competencies rather than seven versions of one strength, and use this grid to audit coverage.
| Competency | How it usually gets asked | What your story has to prove |
|---|---|---|
| Ownership | Tell me about a time you took responsibility outside your remit. | You spotted a problem nobody assigned to you and closed it out. |
| Conflict and influence | Describe a disagreement with a colleague or manager. | You held a position on evidence and kept the relationship intact. |
| Failure and learning | Tell me about a time you got something badly wrong. | You named it, contained the damage and changed a process after. |
| Ambiguity | When have you decided without complete information? | You framed the decision, took a reversible first step, set a review point. |
| Delivery under pressure | What is the tightest deadline you have worked to? | You resequenced scope deliberately rather than just working longer. |
| Remote collaboration | How do you work with people you rarely see in person? | You made progress visible in writing, without being in the room. |
Your story bank should match the evidence on your CV. If an interviewer can see an achievement on page one and you cannot expand it into a two-minute story, that is a credibility problem — and a strong story appearing nowhere on your CV means the document undersells you. An expert resume review tells you which achievements can carry an interview answer and which are still too vague to defend.
Remote and Hybrid Interviews: What Changes
Distributed teams have added two things to the standard behavioural set. The first is content: interviewers now probe explicitly for evidence that you can operate without an office. Expect questions about working across time zones, handing over work asynchronously, or untangling a misunderstanding that started in a written message. Keep at least one story where the collaboration was remote, and let the result show that the work moved forward in writing.
The second is delivery. On a video call you lose the cues that tell you when to stop talking, so pause deliberately after your result and let the interviewer come in.
Prepare for the Follow-Up, Not Just the Question
A good interviewer will not accept your first pass. The probes that follow are predictable:
- "What was your specific contribution?" — asked when you leaned on "we". Know which parts you did, decided or wrote.
- "How did other people react?" — they are testing whether the influence was real. Be ready to describe the pushback.
- "What would you do differently?" — have one honest answer per story; a candidate who cannot critique their own work reads as inexperienced.
- "What did you try that did not work?" — invented stories have no failed first attempt.
- "How did you know it worked?" — your result needs a source: a report, a stakeholder, a process that survived you.
This is why you should use only real experiences: a fabricated story collapses on the second follow-up.
Mistakes That Sink Otherwise Strong Candidates
The "we" problem
Team language is a habit from performance reviews and it is fatal here: if your answer contains only "we", the panel can only score your former team. Say "we agreed the approach; I built the model and presented it to the board."
A result nobody can check
"Everyone was really happy" is not a result. With no metric, use a durable consequence: the process was adopted permanently, the client renewed, the error stopped recurring. Never invent a percentage — an interviewer in your field will ask how it was measured.
Stories that are too old or too small
An example from six years ago suggests your recent work is unremarkable, so favour your last two roles and situations with real stakes — a scheduling clash between teammates is not a conflict story.
Polishing the wording instead of closing the gap
If the same hole keeps appearing — no data story, nothing recent involving a tool the role requires — better phrasing will not fix it. Generate the missing evidence: volunteer for the work internally, or take a certifiable targeted career course and build something you can genuinely talk about.
A Two-Week Practice Plan
- Days 1 to 8: List every project from your last two roles, pick seven with a clear beginning, a decision and an end, and write each as five bullets. Fill in the numbers while you can still check them, then map the seven against the competency grid above — any empty row is a gap.
- Days 9 to 11: Say each one aloud and time it. Anything over two minutes gets cut from the situation, never the action.
- Days 12 to 14: Record yourself on video, or run a mock with someone who will interrupt you using the five probes above. Recording is the highest-return step: it is where you find the filler words, the long preamble, and the result you thought you said but did not.
FAQ
How long should a STAR answer be?
Between 90 seconds and two minutes. Under a minute usually means you skipped the action detail; past two and a half you are narrating context. Time yourself out loud — spoken delivery is slower than reading.
What if I do not have a relevant example?
Adapt the closest real experience and say so: "I have not managed a full team, but I led a three-person workstream for six months — can I use that?" Interviewers accept an adjacent example offered honestly. They will not forgive a fabricated one that unravels under follow-up.
Can I use the same story twice?
Yes, if you genuinely reframe it — one project can evidence prioritisation, influence and recovery from a mistake, provided each retelling has a different task, actions and result. Telling it identically twice signals thin experience.
Should I use STAR for "tell me about yourself"?
No. That is a positioning question — give a short career arc, your current expertise, and why this role is the next logical step. Save STAR for anything starting with "tell me about a time" or "give me an example".
Is it acceptable to bring notes?
A single card of story titles and key figures is fine, and on a video call it is invisible beside the camera. Say at the start that you have notes. What you must not do is read a prepared answer aloud — it is obvious, and it undoes the credibility the story was meant to earn.
Turn Your Evidence Into Interviews
Behavioural interviews reward the same thing a strong application does — specific, defensible evidence of what you did and what changed because of it. If your stories are stronger than the document meant to get you into the room, fix the document first. See Resumere pricing for the review, rewrite and upskilling options that get your evidence in front of a hiring panel, and read our guide to common interview mistakes to avoid for what loses interviews outside the STAR answer.
Put this into practice. Check your resume with the Free ATS Resume Checker, then follow our MBA resume guide for role-specific bullets.
