Behavioural interview questions ask you to describe a specific situation from your past to demonstrate a skill or quality. They follow the logic that how you behaved in the past is the best predictor of how you will behave in the future. The STAR method is the most effective framework for structuring your answers.
STAR stands for: Situation, Task, Action, Result. Every strong behavioural answer does four things in order: sets the scene, explains what you were responsible for, describes what you specifically did, and states the outcome.
What Is the STAR Method?
| Letter | Meaning | What to cover |
|---|---|---|
| S | Situation | The context. Where were you, when was this, what was the background? Keep it brief — one or two sentences. |
| T | Task | Your specific role or responsibility in that situation. What were you expected to do or solve? |
| A | Action | The specific steps you took. This is the longest section. Use "I" not "we" — the interviewer wants to know what you did. |
| R | Result | The outcome. Quantify where possible. What changed, improved, or was achieved as a result of your actions? |
A well-structured STAR answer takes 90–120 seconds to deliver out loud. Shorter usually means you have skimmed the Action section. Longer usually means the Situation has run on too long.
How to Prepare STAR Answers Before Your Interview
Step 1: Build a story bank. Before any interview, prepare 8–10 STAR stories that cover different competencies. The same story can often be adapted for more than one question, but you want enough variety to avoid repeating yourself.
Step 2: Map your stories to the job description. Read the job posting and identify the competencies the employer is looking for — leadership, collaboration, analytical thinking, customer focus, etc. Make sure you have a story for each one.
Step 3: Quantify the Results. Before the interview, go back through your stories and add numbers wherever you can. "Improved the process" is weaker than "reduced processing time by 3 days." The more specific the result, the more credible the answer.
Step 4: Practise out loud. Thinking through a story in your head and saying it clearly under pressure are very different. Practise each answer aloud at least twice. Record yourself if possible — it reveals filler words and pacing problems you would not otherwise notice.
Common Behavioural Interview Questions by Competency
Interviewers typically signal the competency they are testing in the question itself. Use this list to map questions to your prepared stories.
Leadership
- "Tell me about a time you led a team through a difficult situation."
- "Describe a time when you had to make a decision without all the information you needed."
- "Give me an example of when you motivated someone who was underperforming."
Teamwork and Collaboration
- "Tell me about a time you worked successfully as part of a team."
- "Describe a situation where you had a conflict with a team member and how you resolved it."
- "Give me an example of a time you had to work with someone whose style was very different from yours."
Problem Solving
- "Tell me about a time you identified a problem and came up with a creative solution."
- "Describe a situation where you had to analyse complex information to make a decision."
- "Give me an example of a time you had to work through an obstacle to achieve a goal."
Resilience and Handling Failure
- "Tell me about a time you failed and what you learned from it."
- "Describe a time when things did not go to plan. What did you do?"
- "Tell me about the most difficult professional situation you have faced."
Initiative and Drive
- "Give me an example of a time you went above and beyond what was expected."
- "Tell me about a time you identified an opportunity that others had overlooked."
- "Describe a time you took on a project or task that was not part of your job description."
Time Management and Prioritisation
- "Tell me about a time when you had to manage multiple priorities at once."
- "Describe a situation where you had a tight deadline. How did you handle it?"
- "Give me an example of a time you had to say no to a request in order to focus on higher-priority work."
Full STAR Method Examples
Example 1 — Leadership: Managing a Team Through a Crisis
Question: "Tell me about a time you led a team through a difficult situation."
S: "In my third year as a marketing manager, our agency lost its largest client three weeks before a major campaign launch. The client represented 40% of our revenue and the news hit the team hard — morale dropped immediately."
T: "As team lead, I was responsible for managing the immediate workload disruption, keeping the team motivated, and ensuring we could still deliver outstanding work for our remaining clients."
A: "I called a team meeting within 24 hours to be transparent about what had happened and what it meant for us. Rather than downplaying the situation, I acknowledged it was serious and invited the team to help shape our response. We mapped out our active projects, redistributed the freed-up capacity to pitch three prospective clients, and I personally reached out to our existing clients to proactively reassure them. I also pushed the leadership team to fast-track a financial buffer decision so the team felt secure."
R: "Within six weeks we had signed two of the three new clients, recovering 60% of the lost revenue. More importantly, two team members later told me that how we handled the crisis was why they stayed with the agency. We retained the whole team through a period that could have seen significant turnover."
Example 2 — Teamwork: Resolving Conflict Between Team Members
Question: "Describe a situation where you had a conflict with a team member and how you resolved it."
S: "I was leading a product launch project alongside a colleague from the engineering team. We disagreed significantly on the timeline — I believed the commercial deadline was fixed; they believed the scope needed to be reduced to meet it safely."
T: "As the project lead, I needed to resolve the standoff in a way that maintained the working relationship and produced a realistic plan."
A: "Rather than escalating to our manager, I requested a one-to-one with my colleague to understand their concerns in full. In that conversation I realised I had not properly communicated the commercial consequences of missing the deadline, and they had not fully shared the technical risk. Once we both understood each other's constraints, we were able to scope a phased launch."
R: "The phased approach was accepted by both sides. The core launch happened on time, the commercial target was met, and the enhanced version launched successfully five weeks later."
Example 3 — Problem Solving: Identifying and Fixing a Process Failure
S: "In my role as operations coordinator, I noticed that our customer complaint response time had crept up from 2 days to over 5 days across a quarter without anyone flagging it formally."
T: "I was not the complaint handler — that sat in a different team — but the knock-on effect on customer renewals was in my remit."
A: "I pulled three months of complaint data, mapped where delays were occurring, and found that 70% of complaints were stalling at the handover point between first-line support and the specialist team. I built a simple escalation tracking spreadsheet, proposed a 4-hour handover SLA, and worked with the support team manager to implement it."
R: "Within 6 weeks, average complaint response time dropped from 5.2 days to 2.8 days. Customer satisfaction scores improved by 18 points in the next quarterly survey, and the escalation tracker was adopted by two other regional teams."
Example 4 — Resilience: Handling a Significant Failure
S: "Early in my career as a junior account manager, I was managing a client renewal negotiation on my own for the first time. I misread a message from my manager and offered the client a 20% discount — well below our minimum."
T: "I had committed the price verbally to the client and needed to manage both the client expectation and the internal fallout."
A: "I immediately told my manager what had happened rather than waiting to see if the client would accept it. We agreed I would go back to the client, explain there had been a miscommunication on my part, and offer a revised figure with a genuine value-add to soften it."
R: "The client accepted the revised price. My manager's trust in me actually increased because I surfaced the problem immediately rather than trying to hide it. I implemented a personal checklist for any pricing communications that I still use today."
Example 5 — Initiative: Going Beyond the Job Description
S: "I was a data analyst at a retail company and noticed that the weekly sales reports our team produced were taking each analyst 3–4 hours to compile manually."
T: "My role was to analyse data and produce insights, not to maintain reporting infrastructure, but the problem was real and nobody was solving it."
A: "On my own initiative I spent two evenings building a Power BI dashboard that automated the core data pulls and formatting. I tested it with my own weekly report, then shared it with the team and offered to help everyone migrate to it."
R: "The dashboard cut weekly reporting time from 3–4 hours to under 30 minutes per analyst — a saving of roughly 15 hours per week across the team of four. My manager formally recognised it in my annual review."
Example 6 — Time Management: Handling Competing Priorities
S: "In my second year as an HR business partner, I was simultaneously supporting a restructuring programme affecting 80 roles, managing a surge in employee relations cases, and recruiting for three senior positions — all at the same time."
T: "I had to deliver on all three workstreams without compromising any of them, and without burning out my small team."
A: "I blocked my calendar into defined focus periods for each workstream, set clear response-time expectations with stakeholders, and delegated the initial screening for two of the three recruitment campaigns to a colleague I briefed and supported. I created a daily triage list each morning and had a direct conversation with my director about capacity limits."
R: "All three workstreams were delivered on time. The restructuring completed with no legal challenges. Two of the three senior roles were filled within 8 weeks. The triage approach I documented was adopted by two other BPs in the team."
What NOT to Do in a STAR Answer
Saying "we" throughout the Action section. The interviewer wants to know what you specifically did. "We decided to..." tells them nothing about your contribution. Say "I proposed", "I led", "I built" — even when the outcome was a team achievement.
A weak or vague Result. "It went really well" is not a result. Push yourself to quantify: percentage improvements, time saved, revenue generated, problems prevented, scores improved.
Choosing a story where your role was passive. Pick examples where you made decisions, took initiative, or drove change. Avoid stories where things happened around you and you observed.
Running on too long. Most STAR answers should take 90–120 seconds. If yours regularly runs to 3 minutes, you are over-explaining the Situation.
Prepare Your Full Interview With resum8
Your STAR stories and your resume should be consistent. Use resum8's Skill Match Score to run your CV against the job description before your interview — it shows you which skills and keywords the employer is focused on, so you can select the STAR stories most likely to resonate.
Try resum8 FreeFrequently Asked Questions
What does STAR stand for in an interview?
STAR stands for Situation, Task, Action, Result. It is a framework for structuring answers to behavioural interview questions — questions that ask you to describe a specific example from your experience. Each letter prompts a different part of the answer: the context, your responsibility, what you did, and what happened as a result.
What is the difference between behavioural and situational interview questions?
Behavioural questions ask about what you have done in the past ("Tell me about a time when..."). Situational questions ask what you would do in a hypothetical scenario ("What would you do if..."). The STAR method applies directly to behavioural questions. For situational questions, use the same structure but frame it as what you would do.
How long should a STAR answer be?
90–120 seconds when spoken aloud. The Situation and Task together should take no more than 20–30 seconds. The Action section should be the longest part. The Result should be concise but specific.
Can I use the same STAR story for different questions?
Yes, but adapt it. A strong story about leading a project can serve questions about leadership, prioritisation, teamwork, and problem-solving — as long as you adjust which part of the story you emphasise. Prepare 8–10 stories to cover most competency areas.
What if I cannot think of a work example for a STAR question?
Use examples from other areas: academic projects, volunteering, running a club or society, managing a significant personal project. Be upfront that it is not a work example if you are early in your career — interviewers hiring for junior or graduate roles expect this.
How do I answer a STAR question about failure or weakness?
Choose a real failure, not a disguised success. Describe what went wrong, take clear ownership, and then focus the majority of your answer on what you learned and what you changed as a result. The result in a failure STAR story is what improved or changed because of the experience.