Stop Trying to Use STAR in Interviews

STAR is probably the most common piece of interview advice in existence. If you have ever Googled how to answer a competency-based interview question, you will have been told to structure your answer using Situation, Task, Action and Result.

It is not bad advice. The problem is that people become so focused on remembering STAR that they forget they are supposed to be having a conversation with another human being.

You can almost see it happening. Someone starts answering a question reasonably naturally, then they begin mentally checking where they are in the framework. Have I explained the situation? Was that the task or the action? Have I talked enough about the result? By the time they have worked out which letter comes next, they have lost their train of thought, started repeating themselves and turned a perfectly good example into a confusing mess.

They are not struggling because they lack experience. They are struggling because they are trying to perform a framework from memory while also remembering the example, reading the interviewer’s reaction and working out whether they have answered the actual question. That is a lot to hold in your head at once.

STAR is an editing tool, not a performance technique

STAR is useful when you are preparing for an interview because it helps you spot the gaps in an example. Is there enough context for the story to make sense? Is it clear what you were responsible for? Have you explained what you actually did rather than hiding behind “we”? Is there a result?

That is what the framework is for. It gives you a way to check that your example is complete before the interview. It should not feel like four separate boxes you have to visibly work through while you are speaking. When you are actually in the interview, you are just telling a story: what was happening, what did you need to do, what did you do and what happened as a result?

That is STAR, obviously, but it sounds much less intimidating when you stop treating it like a formula you need to recite perfectly. Most of us tell stories every day without needing a four-letter acronym to get through them. We give someone enough background to understand what happened, explain the interesting bit and tell them how it ended. An interview answer is no different; it just needs to be a little more focused.

The question is rarely the real problem

People often prepare for interviews by writing answers to a huge list of possible questions. They rehearse an answer for conflict, another for leadership, another for a mistake, another for working under pressure and another for dealing with a difficult stakeholder.

Then the interviewer asks something they have not prepared word for word and the whole thing falls apart.

The mistake is preparing answers instead of preparing stories. Interviewers can ask hundreds of different questions, but you do not need hundreds of different examples. A strong story about rescuing a failing project might demonstrate problem-solving, communication, influence, resilience, prioritisation or leadership depending on which parts you emphasise. That is much easier than trying to memorise a separate script for every question you might possibly be asked. You are not attempting to predict the interview. You are building a bank of evidence that you can adapt when you hear the question.

You are probably skipping the most important part

The weakest part of most interview answers is not the situation or the task. Candidates usually give far too much context, if anything. The weakness is normally the action.

Someone will spend two minutes explaining the company, the team, the project and everything that had gone wrong before saying, “So we worked together and managed to deliver it on time.” The interviewer still has no idea what that person actually did.

Your actions are where the evidence lives. What decision did you make? What did you say? What did you change? How did you approach it? Why did you choose that option? What resistance did you face? If somebody else on the team could tell exactly the same story, you have probably not made your own contribution clear enough.

The result matters too, but it does not always need to be a dramatic revenue figure or a 47 per cent improvement. Sometimes the result is that the customer stayed, the deadline was met, the problem did not happen again or you learnt something that changed how you worked afterwards. A credible result is better than forcing an impressive-sounding number into every answer.

Do not memorise the wording

Writing out a polished answer can be helpful. Trying to memorise that answer word for word usually is not.

The moment you forget one sentence, you start searching your memory for the script instead of listening to the interviewer. Even when you remember it perfectly, it can sound like you are reading from an invisible autocue. That becomes even more obvious when the prepared answer only partly fits the question you were asked.

Prepare the shape of the story instead. Keep a few prompts: the problem, your responsibility, the two or three most important actions and the outcome. You should know the story well enough to tell it in slightly different ways, because it actually happened to you.

This also makes follow-up questions much easier. If the interviewer asks why you made that decision or what you would do differently now, you are not being dragged away from a memorised answer. You are simply talking about an experience you understand.

Build a story bank

Before your next interview, stop trying to write the perfect answer to 30 different questions. Instead, choose a smaller number of real examples from your career that show different sides of you. Include times when you solved a problem, handled conflict, influenced someone, made a mistake, improved something, worked under pressure and dealt with a difficult decision.

For each one, use STAR privately to make sure the story works. Cut any background that the interviewer does not need. Make your own actions specific. Check that there is a clear ending. Then practise telling it aloud like a story rather than delivering it like a presentation.

You will still be using STAR. You just will not be trying to remember which letter you are on while somebody watches you panic.

That is the approach behind my Job Interview Playbook. It is designed to help you understand what interviewers are really looking for, build the right bank of examples and turn your experience into answers that sound like you rather than something generated for you. If interviews are where your job search keeps falling apart, you can find the Playbook here.

The framework is not the answer. Your story is.