# The STAR method for interviews, with example answers > How to answer “tell me about a time” questions with the STAR method: situation, task, action, result. Four worked examples and the mistakes to avoid. Source: https://octrahire.ai/guides/star-method A simple shape for answering “tell me about a time when…” questions, with worked examples for HR, technical and graduate interviews. ## What the STAR method is STAR stands for situation, task, action and result. It is a way of shaping your answer to a behavioural question: a question about something you have actually done, rather than what you would do. “Tell me about a time you disagreed with a colleague” is a behavioural question. “What would you do if you disagreed with a colleague?” is not. Interviewers ask behavioural questions because a real example is easier to judge than a promise. STAR helps you give them one in a form they can follow: enough context to understand it, a clear account of what you did, and how it ended. ## The four parts Each part has a different job, and they are not equal in length. A spoken STAR answer usually works best at around one and a half to two minutes, most of it on the action. If you are still describing the situation after thirty seconds, move on to what you did. - Situation: one or two sentences of context. Where you were, roughly when, and what was going on. - Task: what you were responsible for, or what needed to happen. Keep it to a sentence. - Action: what you did, step by step, in the first person. This is the heart of the answer and should be the longest part. - Result: what happened in the end, with a number if you honestly have one, and what you learned or would do differently. ## Example 1: a behavioural question (HR round) Question: “Tell me about a time you handled a disagreement in your team.” Situation: “In my last role I was one of four analysts preparing a monthly sales report. Two of us disagreed about whether to change how returns were counted, and the report was due in a week.” Task: “I was responsible for the returns section, so it was my job to settle the method before the deadline.” Action: “I asked my colleague to talk it through with me rather than over chat. We each wrote down what the change would do to the last three months of figures. Mine moved the totals by under one per cent, his by four, and his was closer to how finance counted returns. I said so, agreed to use his method, and suggested we add a note to the report explaining the change so nobody was surprised.” Result: “The report went out on time, finance stopped asking us to reconcile the two figures each month, and we kept the habit of testing a change on past data before arguing about it.” ## Example 2: a technical question Question: “Tell me about a bug that was hard to track down.” Situation: “At my internship, our order page sometimes took several seconds to load, but only in the afternoons, and nobody could reproduce it on their own machine.” Task: “I was asked to find the cause before a sales event the following week.” Action: “I added timing logs around each database call and compared slow requests with normal ones. The slow ones were all waiting for a database connection. I checked what else ran in the afternoon and found a reporting job that opened connections in a loop and held them. I changed it to reuse one connection, tested it on a copy of the data, and added an alert if connections ran low.” Result: “The slow loads stopped, the page held up during the sales event, and the alert caught a similar problem in another job a month later. I learned to measure first instead of guessing.” ## Example 3: a graduate with little work experience Question: “Give me an example of when you showed leadership.” Situation: “In my final year I was on the committee for our department's technical festival. Three weeks before, the student leading sponsorship left the committee.” Task: “I offered to take over, with the job of covering the remaining budget.” Action: “I listed every company that had sponsored in the past two years, split the list between three volunteers, and wrote one short email we could all adapt. I held a ten-minute call every second day so we could see who had replied and who needed a follow-up. When two sponsors asked for stalls instead of logos, I agreed it with the committee the same day.” Result: “We covered the budget a week before the festival. Looking back, I would have shared the list on day one instead of day four.” ## Example 4: a question about a mistake Question: “Tell me about a time something went wrong.” Situation and task: “I was preparing a weekly dashboard for my manager, and one week I sent it with the wrong date filter, so the numbers covered two weeks instead of one.” Action: “A colleague noticed the next morning. I told my manager straight away, sent a corrected version within the hour, and explained what had happened. Then I added a check that shows the date range at the top of the dashboard, and a short checklist I run before sending.” Result: “It has not happened again, and my manager asked me to add the same check to two other reports. Owning it quickly mattered more than the mistake itself.” ## Common mistakes - Saying “we” all the way through. The interviewer needs to know what you did. Credit the team, then be specific about your part. - Spending most of the answer on the situation. Context is only there to make the action make sense. - Stopping before the result. If the outcome was mixed, say so and say what you learned. - Answering a “tell me about a time” question with what you would do. If you have no exact example, say so and offer the closest real one. - Choosing an example with nothing at stake. A small problem you solved well is fine, but there should be a reason it mattered. - Memorising a script word for word. It sounds rehearsed, and follow-up questions will take you off it anyway. - Inventing or stretching details. Interviewers follow up, and made-up specifics are hard to defend. ## How to prepare your stories Write down six to eight real situations from work, internships, study, projects, sport or volunteering. For each, note the four parts in a line or two, and any number you can honestly use. Then match them to the themes interviewers often ask about: teamwork, disagreement, a mistake, leadership, working under pressure, learning something quickly and persuading someone. One good story can often answer two or three different questions. Practise them out loud, not just in your head. ## How interviewers listen for STAR In a structured interview, each behavioural question usually comes with a rubric that describes a weak, solid and strong answer. A weak answer often describes only the problem. A solid one explains what the candidate did. A strong one also explains why, what they checked and what the result was. That is why interviewers ask follow-ups such as “What did you do, specifically?”, “How did you know it worked?” or “What would you do differently?” Each one is reaching for a part of STAR that was missing. Octrahire's AI interviewer works the same way. It asks the role's questions one at a time and follows up on what you actually said, so an answer without a clear action or result is likely to get a follow-up. Each score in the report shows the answer behind it, and a person makes the hiring decision. Students can practise free, by voice, in English or Arabic. ## What is the STAR method in a job interview? The STAR method is a way to answer behavioural interview questions, the ones that start “tell me about a time when”. You briefly describe the situation and your task, spend most of the answer on the actions you personally took, and finish with the result and what you learned. It keeps answers specific, in the first person and about two minutes long, which is what interviewers' rubrics usually reward. ## Questions ### How long should a STAR answer be? Around one and a half to two minutes when spoken. Keep the situation and task short and spend most of the time on what you did. ### Can I use the STAR method with no work experience? Yes. Use examples from study, projects, internships, clubs, sport, volunteering or family responsibilities. What matters is that it really happened and you can explain your part. ### Do I have to say “situation, task, action, result” out loud? No. STAR is a shape for your answer, not a script. The interviewer should simply hear a clear story with your actions and a result.