The STAR method: how to structure interview answers

Hypothetical questions, such as "how would you handle a difficult client?", invite ideal answers. Almost everyone knows the right thing to say. Behavioural questions, such as "tell me about a time you handled a difficult client", ask for something harder to fake: a real event, your real actions, a real outcome. Follow-up questions then test whether the story holds together.

Many organisations use structured or competency-based interviews, where each question maps to a skill in the job specification and every candidate is scored against the same criteria. In that setting, an answer that is interesting but unstructured can score poorly because the interviewer cannot find the evidence they are listening for. STAR helps you put that evidence exactly where they expect it.

Behavioural questions also arrive in disguise. "Give me an example of", "describe a situation where" and "have you ever had to" are all asking for the same thing, even without the words "tell me about a time". Recognise them and the same structure applies. It works equally well for written application questions that ask you to evidence a competency in a few hundred words.

The letters are easy to remember. The proportions are what separate strong answers from average ones. A good answer to a behavioural question usually lasts around two minutes, and the time should be distributed roughly like this:

Some candidates merge situation and task into a single sentence, which is fine. What matters is that the listener understands the context and your responsibility within about thirty seconds, so the rest of the answer can focus on what you did and what it achieved.

Take the question: "Tell me about a time you had to meet a tight deadline." A weak answer sounds like this: "We had a big client report due and the team was really stretched. There was a lot going on, the client kept changing things, and it was a stressful few weeks. We all pulled together, worked some late nights and got it done on time. The client was happy." It has a situation and a vague result, but no clear task, no individual action and nothing an interviewer can score.

A stronger version: "Two weeks before a quarterly client report was due, our lead analyst went on unexpected leave, and I was asked to take over the delivery. My task was to produce the report on time without dropping my own work. I split the report into sections and mapped which data was ready and which was not. I negotiated with the client to move one lower-priority section into a follow-up note, automated the data pull that had previously been done by hand, and set up a fifteen-minute daily check-in with the two people contributing. We delivered the full core report a day early, the client accepted the follow-up approach, and the automation now saves the team several hours each quarter."

The second answer is not longer because it is padded. It is longer because the action section is doing its job: specific choices, in order, with reasons. That is what the interviewer is scoring.

You cannot predict every question, but you can predict the competencies. Read the job description and list the five or six skills it emphasises, then prepare one or two stories for each. Many stories can be adapted to several questions, so six to eight well-prepared examples usually cover most of what a behavioural interview will ask.

Aim for a spread that covers the themes that come up most often:

The most common mistake is saying "we" throughout. Teamwork is real and worth acknowledging, but the interviewer is hiring you, not your former team. If they cannot tell which actions were yours, they cannot score them. Use "we" for context and "I" for the actions you personally took.

The second is spending half the answer on the situation. Candidates often feel they need to explain the whole organisation, the history of the project and every stakeholder before the story makes sense. It rarely needs that. If the interviewer wants more context, they will ask.

The third is ending without a result, or with a vague one such as "it went well". Every story needs an ending, and the stronger the evidence, the better: a deadline met, a figure improved, a client retained, a process still in use. If the outcome was mixed, say so honestly and explain what you learned. Interviewers generally trust a candid mixed result more than a suspiciously perfect one.

Finally, avoid choosing stories with no real difficulty in them. "Tell me about a challenge" answered with a routine task done competently shows little. Pick examples where something was genuinely at stake and where your choices made a difference.

Questions about failures, weaknesses and conflict need a slight adjustment. Many interviewers expect you to add a reflection at the end, sometimes called STARR, where the final R stands for what you learned or would do differently. For these questions, the reflection is often what is actually being assessed. They want evidence of self-awareness, not a story in which you were secretly right all along.

For a failure question, choose a real mistake with manageable consequences, own your part of it plainly, describe what you did to recover the situation, and spend a sentence or two on what you changed afterwards. For a conflict question, describe the disagreement fairly, including the other person's reasonable point of view, and focus on how you reached a working resolution rather than on who won. Speaking negatively about former colleagues rarely lands well, however justified it felt at the time.

Once you have your story bank, practise telling each story aloud, ideally to another person or on a recording. Timing yourself helps; many first attempts run twice as long as they should. What you want to memorise is the structure and the key facts, particularly the numbers and the sequence of actions, not the exact wording. A memorised script sounds recited, and it collapses the moment an interviewer interrupts with a follow-up.

Expect those follow-ups. "What would you do differently?", "How did your manager react?" and "What was the hardest part?" are all ways of testing whether the story is real and whether you understand it. If you know the event well, these questions are an opportunity rather than a threat, because they let you show depth that no prepared answer can.

It also helps to link your stories to your CV. The achievements on your CV are, in effect, the results sections of your STAR stories. If a bullet says you reduced processing time or retained a key client, be ready to tell the full story behind it, because interviewers often pick a line from your CV and ask you to walk them through it.