Amanda Datchens

09/28/2026

“Tell me about” behavioural interview questions: stop using STAR.

Stop memorising STAR answers. Behavioural interview questions need more than an over rehearsed robotic script.

More...

Key Takeaways

  • STAR was designed to help interviewers score answers, not to help candidates stand out.
  • Over-rehearsed STAR responses can sound scripted, waste time on background and hide how you actually think.
  • Use SSS instead: explain your Stance, outline your repeatable Steps, then provide a real Setting as evidence.
  • Build a bank of two or three authentic stories you understand deeply rather than memorising an answer for every possible question.
  • Use AI to uncover, organise and pressure-test your experiences, but never let it invent or write your answers for you.
  • She did her interview prep and had a document full of STAR answers. Twelve stories, neatly formatted, each one rehearsed until she could deliver it in her sleep.

    Come interview day, she felt confident going in. But it didn't work. She knew she sounded competent, but she also knew that her answers just didn’t land.

    The follow-up questions started getting shorter, and the interviewer stopped writing things down.

    Worse, she noticed them visibly switching off halfway through her best answer, the one she felt would surely land her the job.

    This is a story I hear from candidates all the time. Everyone tells them to use the STAR method, so they put in the work, only to have it backfire on them when faced with a real live interview.

    Perhaps this has happened to you too?

    In the past I also advised people to use the STAR method to prepare for behavioural interview questions.  

    Today I don’t.

    Times have changed, and so should your interview prep.

    Let’s dive in.

    What is the STAR method?

    The STAR method was created in 1974 by Dr. William C. Byham in partnership with the HR consulting firm Development Dimensions International (DDI).

    The acronym stands for:

    • Situation: Outline the background or situation where you faced a problem or were given a responsibility.
    • Task: Clarify your specific role or objective in that situation.
    • Action: Detail the steps you took to address the issue or fulfil your responsibility.
    • Result: Describe what happened as a result of your actions, including any impact or lessons learned.

    The relationship between behavioural interview questions and STAR

    Behavioural interview questions originated in the mid-1970s to 1980s and were pioneered by industrial organisational psychologists like Dr. Tom Janz, who helped formalise the concept through research and books like Behavior Description Interviewing.

    These questions allow employers to target specific job competencies like problem-solving, teamwork, or leadership by looking at verified history rather than assumed guesswork.

    Their premise is that past behaviour is the best predictor of future performance.

    These are usually mixed in with other common interview questions like "tell me about yourself' and "what is your greatest strength" and typically start with:

    • Tell me about a time when …
    • Give me an example when …
    • When have you had to …
    • Describe a situation in which...

    These open-ended questions are pure gold for the interviewer because they let a candidate show how they really think, but they're also a nightmare to compare. Ask six people the same open question and you get six answers on six different subjects and tangents.

    STAR was the fix. Give every candidate a shared structure and you can compare ‘like with like’. This is why it's been taught in HR courses and baked into interview scorecards for fifty years. If you're hiring, it's undeniably an excellent tool.

    But that is exactly the thing you need to remember.

    STAR was never designed to help you win the interview. It was designed to help your interviewers record it.

    How STAR ended up in candidate coaching

    Once it was known that interviewers were scoring against situation, task, action and result, candidates understandably started preparing answers in that shape.

    Over the years it hardened into standard advice, repeated in careers articles, university careers services and interview prep guides until it became the default answer to "how should I prepare?"

    On the face of it this was reasonable advice but, unfortunately, it was built on entirely the wrong assumption.  The framework itself isn’t the thing being scored. What they're actually scoring is the four or five competencies on their sheet, and your STAR answer is just the raw material they're reading those from.

    Why STAR is not the best method for interview preparation

    Whilst STAR is a robust framework, and certainly better than going into an interview totally unprepared, there are serious flaws that could cost you the job.

    Rewards memorisation over authenticity

    The moment you start building STAR answers, you're building a set of scripts. And scripts have a problem because they only sound right when the conversation goes exactly where you expected. If things deviate you could find yourself lost and floundering.

    More importantly, STAR rewards one particular way of speaking. It assumes you can isolate a clean situation, name a task, narrate a sequence of actions in order, and land a tidy result. That's one communication style, and it's far from the only good one.

    Plenty of capable people don't think in tidy linear narratives. That includes neurodivergent candidates, who may communicate with more context, more tangents or more precision than the format allows.

    It includes people from culturally or linguistically diverse backgrounds, where the expected level of scene-setting or self-promotion may be very different.

    It includes professionals who've spent a career in operational or technical roles, where the habit is to explain the mechanism rather than to sell the story.

    These candidates are often just as qualified, and sometimes more so, but STAR can screen them out without anyone intending it because the framework confuses polish with substance.

    If the interview process only rewards the most confident storytellers, organisations are probably missing out on dynamic, adaptable thinkers who simply express themselves differently.

    STAR was built to reduce bias by standardising the comparison. Applied to a room full of different communicators, it just produces a different one.

    Takes too long

    STAR is a heavy preparation commitment, and it scales badly.

    Because you can't predict which story they'll ask for, you end up trying to cover every angle they might pursue. So, you build a story for conflict, a story for failure, a story for influence, a story for pressure, a story for leadership, and on it goes. Then you do the same for the second job on your resume, and the third.

    The logic sounds sensible. Cover everything and you can't be caught out. In practice, you end up with a document of fifteen or twenty answers, none of which you know well, and a prep process that swallows your evenings.

    Worse, all that effort is pointed at the wrong problem. You're trying to predict the question. What you should be doing is making sure that whatever the question, you have something worth saying and a way to say it. Those are different jobs, and only one of them is finite.

    Produces wrongly weighted answers

    Situation and task are context, and context is the part interviewers score least. Let's face it, nobody has ever been hired for setting the scene yet, using STAR, those are the two stages candidates spend 50% of their answer on.

    It's an understandable instinct. Context feels safe, and it feels like it's doing work. You're establishing credibility, showing the scale of what you were dealing with. But while you're doing that, the interviewer is waiting for the part they can actually score, and the clock is running.

    Worse, it's often the least interesting thing about you. The circumstances of a problem are usually the part anyone could have guessed. What they can't guess is how you approached it. That's the bit that gets squeezed when you've spent half your answer on background.

    No slot for lessons learned

    Which is precisely why STAR falls apart on the questions you're most afraid of. Tell me about a failure, tell me about a time you were criticised, tell me about a mistake. You can force a lesson into the Result stage, but the framework is fighting you the whole way, and it shows.

    STAR's four stages are built for success stories. They assume a situation you resolved, a task you completed, actions that worked and a result you're proud of. There's no natural home for "and here's what I'd do differently," which is the entire point of a failure question.

    So, candidates either bolt a lesson onto the end, where it reads as an afterthought, or they skip it, which is worse. An interviewer asking about failure is looking for self-awareness, and self-awareness is exactly what STAR has nowhere to put.

    Doesn't go deep enough

    It's built for a one-time win, not your normal operating behaviour. A story about the day you saved the project tells an interviewer about your ceiling. What they're trying to work out is your floor. That is, what you're like on an unremarkable Tuesday when the project is going fine and nobody's watching.

    Anyone can be impressive in a crisis. Crises are motivating, they're visible, and there's a clear right answer. The real signal is how you operate when there's nothing dramatic happening, when the work is routine and the pressure is low.

    STAR can't reach that, because it's structurally built around incidents. Ask a candidate about a time something went wrong, and you'll get a story about a time something went wrong. You won't learn what they're like the other 350 days of the year.

    There's a good chance you will choose the wrong story

    You pick the story before you know what's being tested. This is the big one. STAR asks you to arrive with answers prepared, which means you've committed to your story before you've heard the question. So, when they ask about a conflict, and your conflict story is thin, you reach for it anyway because it's what you rehearsed. Your brain says “this is my conflict story” so let’s do it. Box ticked. Phew, got that one out of the way.

    Research on this has found that a well-told story still scores badly if the competence named is not the one interviewers are looking for.

     Interviewers sit there nodding, taking notes, even smiling, while quietly writing that they can't see how what you just described connects to their job. Which means you can execute STAR perfectly and still lose the room, because you delivered on structure it on relevance.

    Alternatives to the STAR method

    So now you know the shortcomings of the STAR method you might be tempted to just wing it at your next interview and see what happens. Don’t. I know what will happen and it will be a mess.

    In addition, I know of instances where candidates have been told prior to interview to use STAR and others who have strayed during an interview and been told to revert to STAR to keep on track.

    When you are given a behavioural question at your next interview it's important for you to know that you don’t have to stick strictly to STAR, but you do need to give structured answers that interviewers can score.

    This means that over the years, many alternative frameworks have been suggested to combat the potential issues associated with using STAR.

    Here are a few.

    • PAR – Problem, action, result.
    • PARLA – Problem, action, result, learning.
    • SOAR – Situation, obstacles, actions, results.
    • SAO – Situation, action, outcome.
    • SHARE – Situation, hindrance, action, result, education.
    • DARE – Describe, action, result, evaluate.
    • CAPS – Context, action, problem, solution.
    • CARL – Context, action, result, learning.


    Whilst some have their merits over STAR, they all start at the same point which still means if you pick the wrong story you could be in trouble.

    Forget STAR, use SSS.

    You need to stop leading with specific examples and start leading with how you think. That’s what they really want to know.

    This is how you do it.

    STANCE

    This is your general approach to a class of problem. Not a story, where you stand and what you believe in. How do you handle disagreement, or pressure, or a decision where you don't have all the information? Say it plainly, in two or three sentences, and say it like you mean it.

    STEPS

    This is where you lay out your actions in order. It’s also what makes you sound like someone with a method rather than someone with a good anecdote. "First I do this, then I do that, then I do that" tells an interviewer your approach is repeatable.

    SETTING

    This is the specific time it played out, and here's the thing. By the time you get here, the work is already done. The story is now just evidence for an argument you've already won.

    Did you feel the shift just then?

    It’s what sets your answer apart from generic typical responses to one that is uniquely about you and the value you have to offer.

    Let me show you what that looks like in practice.

    Say you're interviewing for a Site Supervisor role and they ask about conflict, which in your world usually means a subcontractor doing something safely adjacent to what everyone agreed.

    Stance: "I don't think of a disagreement as a problem to be won. On a site, everyone arguing about something is usually looking at a different part of the same risk, so my starting point is that they've seen something I haven't."

    Steps: "So I do three things, in order. I stop and actually listen to the whole case before I respond, because the useful information is usually in the last thing someone says. Then I ask what outcome they're trying to protect, which shifts it from me versus them into us versus the problem. Then I look for the version neither of us walked in with, because if we've both got a piece of it, there's usually a better answer than either."

    Situation: "The last time this mattered, we had a subcontractor refusing to follow the agreed approach on a large civil project, and it was heading for a formal escalation. I sat down with their supervisor, and it turned out he'd flagged a near-miss on a similar job three years earlier that nobody had recorded anywhere. He wasn't being difficult, he was trying to stop something repeating. We combined his method with ours, the site stayed compliant, and it became the standard approach across the program."


    Notice what just happened.

    The interviewer asked about conflict and heard about safety, judgement, communication and influence, all inside one answer. And notice where the risk sits. If they didn't like your specific example, they still heard a philosophy they can agree with and a process they can trust.

    The story is no longer carrying the answer on its own. That's your insurance for your next interview.

    STAR gives you one shot. If you tell the wrong story, there's nothing holding you up.

    But, if you lead with how you think, you've already scored before the example begins.

    One story, multiple answers

    This will save you so much time and so much stress at your next interview, but it does involve you thinking differently if you have been used to the standard STAR approach.

    If you lead with your stance, you don't need a pile of different stories. You need two or three truly strong, genuine, authentic ones, plus the ability to view them from different angles depending on what's being asked.

    Most candidates do this backwards. They build thirty prepared answers and then panic trying to find the right one under pressure.

    You want the opposite. Fewer stories, understood deeply, so you can pivot on the spot in the interview.

    Let me show you what this looks like.

    Here's the same story we used above, angled five different ways:

    Questions and angles chart

    One story. Five angles. The same setting sits at the end of all five when you need it, or doesn't, if the question doesn't call for it.

    This is why depth beats breadth. Three stories you understand deeply will serve you better than fifteen you've half-memorised. You can enter a good story from five directions, but you can only enter a shallow one from one.

    And it points back to something I said earlier. A story about the day you saved the project tells an interviewer about your ceiling. What they're trying to work out is your floor. What you're like on an ordinary Tuesday when nobody's watching. Leading with your stance answers the floor question. The story answers the ceiling.

    Stop rehearsing answers. Build a story bank instead.

    Forget the document of finished answers. What you actually need is a small number of stories you genuinely care about.

    Not fifteen. Two or three. Maybe four if you've had a long career.

    And they have to be real. That's the part that matters more than anything else in this article, because the whole method collapses without it.

    The test for a story worth keeping

    Here's how you know you've found a good one. It's a time that made you take stock for a minute. Something that shifted how you saw a situation, or changed your mind about a person, or forced you to rethink what you thought was the right answer.

    You can still feel it when you tell it and underneath it, there's a certainty that you did a good job. Not that you were necessarily praised for it, and not that it looked impressive on paper, but you know it was good work.

    That's the marker. If a story passes that test, it will hold up in any interview, in any industry, at any level, because it's about something you actually did and actually believe. If you've been in your field a while, you already know which ones they are. You probably thought of one reading this paragraph didn't you?

    Why authenticity is everything

    You can tell when a candidate is performing. Everyone can. The story is too clean, the lesson is too neat, and the numbers arrive suspiciously well-rounded.

    That happens because people build stories to fit a framework rather than to reflect what happened. They start with "what would sound impressive" and work backwards.

    A story that passes the test above doesn't have that problem. If it mattered to you at the time, the details will be specific without you having to dress them up, and the reasoning will be yours rather than borrowed. That's what authenticity actually means in an interview. Not a false sincerity of tone, but evidence of a real decision you really made.

    It also makes you far less likely to be caught out. An interviewer can ask a follow-up question about a performed story and watch it come apart. They can dig all day into a real one, and the result will be a two-way conversation about something that actually matters.

    If nothing comes to mind

    Then it's worth taking a beat to process this.

    If you've been working for years and can't name two or three times you were genuinely proud of your work, the issue probably isn't your interview prep. It might be that the work hasn't given you much to be proud of, or that you've been in a role that's been slowly flattening you, or that you're heading in a direction you don't actually want to go in.

    That's a very different and much bigger conversation you need to have with yourself. Those missing stories are telling you something about where you are and where you're going.

    The angles come after

    Once you've got your two or three, the rest is easy. You're not writing new answers, you're finding new to talk about them.

    Each story can usually be entered from four or five directions depending on what's being asked. The same experience might answer a question about conflict, one about influence, one about leadership and one about failure, just by starting in a different place.

    Stuck? Let AI interview you

    The hardest part of this isn't the structuring, it's the recall. You lived your career once, at speed with many other commitments, and now you're trying to reconstruct the good bits from memory, under pressure, weeks or years later. That can be tough for a human, but it’s easy for a machine.

    Just to be clear here, don’t make the mistake most people make by asking AI to write their answers. Instead, ask it to interview you. It has infinite patience, it will ask the follow-up question you'd rather it didn't, and crucially, it will keep digging until you produce a specific moment rather than a vague summary.

    Here's a prompt to start with:

    Marc Stanley

    You are an experienced interviewer helping me prepare for a job interview. I have uploaded my resume for you to read. Your job is to interview ME about my career, one question at a time. Do not write answers for me, and do not move on until my answer contains a specific situation, what I actually did, and a concrete result with a number in it. If my answer is vague, push back and ask for the detail. If I say "we", ask what I personally did. Start by asking me which role on my resume I want to start with.

    Then answer it honestly. This is the part that takes effort, and it's where the value is. You'll be surprised how much you'd forgotten.

    Once you've worked through two or three roles, follow up with this:

    Marc Stanley

    Now you are helping me build an interview story bank. Read through our conversation and pull out every story I've told you that shows genuine pride or a real change in my thinking. For each one, give me: a one-line summary, the specific situation, what I personally did, the result with numbers, and the interview topics it could answer, such as conflict, leadership, influencing others, failure, or working under pressure. Put it in a table.

    What comes back is a draft story bank, built entirely from your actual experience, in a fraction of the time it would take to reconstruct alone. Edit it yourself, because the specifics matter and you'll want them in your own words.

    Then, once you have it, pressure test it:

    Here is the job description and here is my story bank. For each competency in the job description, tell me which of my stories proves it, and how strongly. Then tell me which of my stories proves nothing this role needs.

    Marc Stanley

    Marc Stanley

    Don’t skip that second question because it really matters. You don’t want to make the mistake of settling on two or three stories that are impressive but have nothing to do with the job you're interviewing for.

    The perfect prep for behavioural interview questions

    The prep happens in two moves, and you've already done the hard one.

    Most interview advice starts with the job ad. That's backwards. If you start with the ad, you end up building stories to fit it, and that's how you end up with performative answers. Instead, start with what you've actually done, then go looking for the angles.

    Step One: Revisit your story bank

    Pull out your two or three stories. Read them properly, not just the one-line summaries.

    For each one, ask yourself:

    • What did I actually do that made the difference here?
    • What did I think about that a less experienced version of me wouldn't have seen?
    • What did I protect, or prioritise, or refuse to compromise on?
    • Where was the moment it could have gone the other way?

    That last question is the useful one. The turning point in a story is usually where the stance lives, and it's rarely the part people lead with.

    Then write the stance for each. Two or three sentences on how you approach that class of problem, in your own words. Then say it out loud. If it sounds like something you'd never say, it isn't yours yet.

    One thing to check while you're here. Do your stories pass the test from earlier? If any of them feels flat when you reread it, it'll feel flat when you tell it too. Better to notice now.

    Step Two: Find the angles

    Now turn your attention to the job ad or position description and read it twice. Once for the duties, once for the traits behind them.

    "Managing a small team" means leadership. "Working with minimal supervision" means self-direction. "Liaising with external stakeholders" means influence. Underline those phrases and write the competency next to each.

    You'll end up with six or eight things they're actually going to test. That's your target list.

    Then take each competency and ask which of your stories proves it, and which angle you'd enter from.

    Some competencies won't have a story behind them, and that's fine.

    You just need to know which ones they are, so you're not caught flat-footed if one of them comes up. Where the gap is real, the honest move is to talk about something adjacent you've done and be straightforward about the boundary.

    Two or three stories, six or eight competencies, and by the end of this you'll have a map of which angle to take for whatever they ask.

    Doing both at once with AI

    If you'd rather not work through that by hand, there's a much faster route. Give your AI of choice these three things:

    • Your story bank
    • Your resume
    • The job ad or description

    Then ask it to do the matching for you.

    Here’s the prompt:

    I'm preparing for an interview. I've attached three things: my story bank, my resume, and the job description. First, read the job description and list every competency the employer is testing for, including the ones implied rather than stated. Use the language a hiring manager would use on their scoring sheet. Then, for each competency, tell me which of my stories proves it and how strongly, and name the angle I should enter that story from. Be specific about the opening line I should use. Then tell me the three competencies where I'm weakest, and for each one, tell me honestly whether I have anything in my resume that covers it or whether I don't. Finally, tell me which of my stories proves nothing this role needs, so I can stop rehearsing it.

    That last instruction is the one that saves you the most time.

    What comes back is a map you'd have spent an evening building by hand. Read it critically, because the AI has no idea what your workplace was actually like, and it will occasionally pair a story with a competency you'd never claim in real life. Cut anything that feels wrong. If a pairing makes you wince, trust the wince.

    Then do the human part it can't do. Take the two or three competencies you're strongest on, and practice those answers out loud until the stance comes without thinking.

    And if you want a rehearsal partner

    Once the map is built, you can use the same AI to test whether it actually works under pressure.

    Here’s the prompt:

    Act as an interviewer for the role in the job description. Ask me behavioural interview questions one at a time, in a random order, drawing from the competencies you identified. After each answer, tell me whether my stance was clear within the first three sentences, whether my steps sounded repeatable or improvised, and whether I got to the story too early or too late. Do not be encouraging. Be specific about what didn't work. Don't move to the next question until you've given me that feedback.

    The instruction not to be encouraging matters. A rehearsal partner who tells you it sounded great is no use to you.

    One more thing before you close the laptop

    Have a look at the company itself, not to find a fact to impress them with, but to work out what they're likely hiring you to fix. Recent news, what they say publicly, the people on the team and what their backgrounds suggest.

    Then ask yourself: what would they need someone like me to build or sort out in the first year?

    That question tells you which story to lead with, and it turns a rehearsed answer into a considered one.

    Here’s a prompt if you want help:

    Research this company's website [add link] and find recent news about them. Based on what you can find, what are the biggest challenges this company is likely to face in the next 12 months, and what would they most need from a new hire in my role?

    The night before

    Close the document. Do something else. You've done the work, and cramming on the last night only makes you more likely to recite instead of listen.

    And one last thing. Know that every time you work through one of these stories, you remind yourself of what you've actually achieved, and why you're the right person for the job. By the time you walk in, you’ll know exactly why you deserve it.

    Conclusion

    STAR is outdated, but the need for structure isn't. Both you and the interviewer need it to stay on track, and that's not going to change. An unstructured interview is just a conversation, and a conversation is impossible to score fairly. 

    STAR was built so interviewers could compare multiple candidates against the same rubric. Fifty years later, candidates are still using it as a method, and it's costing them roles they should have won. It rewards memorisation over authenticity. It takes weeks of prep to cover angles you'll never be asked about. It spends half your answer on the part nobody scores. It has nowhere to put a lesson. It can't show what you're like on an ordinary day. And it locks you into a story before you've heard the question.

    SSS fixes all six. You lead with your stance, which answers the question about your default behaviour. You give your steps, which proves your approach is repeatable rather than improvised. And you finish with the setting, where the story arrives as evidence rather than as the whole answer.

    The best part is what it does to your risk. With STAR, one wrong story choice can sink the answer, because the story is the answer. With SSS, even if they don't love your example, they've already heard how you think, and that's the thing they were really testing for.

    But the deeper shift is in what you're preparing. You're not building a bank of impressive anecdotes. You're choosing two or three times you genuinely did good work, the ones you'd tell a friend about, and learning to enter them from wherever the conversation goes. That's a much smaller job than the one STAR gave you, and it produces something far harder to fake.

    This matters, because authenticity isn't a technique. It's the byproduct of talking about work you actually cared about.

    So, stop memorising STAR answers for behavioural interview questions. Start with how you think, prove it with how you work, and let your experience be the evidence.

    That's the interview you'll walk out of knowing you nailed it.

    FAQ

    What should I do if the interviewer specifically asks me to use STAR?

    Respectfully acknowledge their request but carry on with the SSS method. They will still get the structured answer they need to be able to assess your suitability. The main reason they ask for a STAR response is for clarity and organisation so that candidates keep the interview on track.

    Should I use an example where things went wrong?

    Yes. A credible mistake followed by genuine reflection and changed behaviour can reveal more about you than another perfectly polished success story.

    How recent should my interview examples be?

    Recent examples are usually stronger, but an older story can still be powerful if it is highly relevant and accurately reflects how you work today.

    What if the interviewer interrupts my answer?

    Stop and listen. An interruption usually means they need clarification or already have enough information, so answer the follow-up directly rather than forcing your prepared response to the end.

    Can I ask what competency the question is testing?

    You can ask for clarification if the question is vague, but it is better to confirm what aspect they want you to focus on rather than asking what they are scoring.


    Written by Amanda Datchens

    Half Irish, half English, now Australian, I am a hands-on recruiter & the joint founder of URHIRED. I’ve grown an agency to a c$25m turnover, successfully headhunted top talent across the world, vastly improved many companies’ talent acquisition strategies, and coached people one on one so they can get the jobs they deserve. When I’m not doing this, you’ll find me down the beach being walked by my large labradoodle Betty.


    Related Posts

    • 04/10/2026
    • Interviews

    Follow up after an interview with confidence. Learn what to send, when to send it and when it is finally time to move on.

    Read More
    • 16/09/2026
    • Interviews

    Yes, there’s a big difference. Here’s how to tell confidence from narcissism, whether you’re hiring or being interviewed.

    Read More
    • 02/09/2026
    • Interviews

    “Overqualified” is code for something the employer won’t say out loud. Knowing these seven main reasons will change your next interview.

    Read More

    {"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

    Follow us

    >