Behavioural Interview Questions and Sample Answers
Twenty common behavioural interview questions grouped by theme, with why each is asked, how to approach it and a sample answer you can adapt to your own experience.
Key takeaways
- Behavioural questions ask for real past examples, on the idea that past behaviour predicts future behaviour.
- Answer with the STAR structure: situation, task, action, result, spending most of the time on your actions.
- Five to seven well-prepared stories can answer most behavioural questions.
- Use real examples with honest outcomes; interviewers often ask follow-up questions to test the details.
Behavioural questions are the ones that begin "Tell me about a time when…" or "Give me an example of…". They ask what you actually did in a past situation, because employers find real examples more reliable than hypothetical answers. Many interviews, including most structured and competency-based interviews, are built largely around them.
This guide lists twenty common behavioural questions grouped by theme. For each one: why it is asked, how to approach it, and a short sample answer. The samples use fictional situations; build your own answers from your real experience.
How to answer behavioural questions
Use the STAR structure:
- Situation: the context, in one or two sentences.
- Task: what you needed to achieve or your responsibility.
- Action: what you did, step by step. This should be the longest part.
- Result: what happened, ideally with a measurable outcome, and what you learned.
Aim for about two minutes per answer. Say "I" rather than "we" when describing your actions, while giving credit to the team where it is due. Our guide to the STAR method goes into more detail.
Prepare five to seven stories before the interview: an achievement, a problem solved, a conflict, a failure, a time you led, a time under pressure, and a time you learned quickly. Most questions below can be answered with one of them.
Teamwork and collaboration
1. Tell me about a time you worked well as part of a team.
Why they ask: to see how you contribute to shared goals and work with others.
Approach: pick a project where your role was clear and the team achieved something specific. Show what you did to help others, not only your own task.
Sample answer: "Our support team had to migrate 400 help articles to a new platform in six weeks. I volunteered to organise the work: I split the articles by topic, set up a shared tracker and ran a 15-minute check-in twice a week. When two colleagues fell behind, I took over part of their review work. We finished a week early, and the tracker became our template for later projects."
2. Describe a time you had to work with someone whose style was very different from yours.
Why they ask: to test adaptability and maturity with colleagues.
Approach: describe the difference neutrally, show how you adapted, and end with a working relationship that improved.
Sample answer: "I prefer detailed written plans; a designer I worked with preferred quick sketches and calls. Early on, we frustrated each other. I suggested we start each feature with a 20-minute call to sketch ideas, and I would then write a short summary for both of us. The calls suited her, the summary suited me, and our next three features shipped without the rework we had before."
3. Tell me about a time you helped a colleague who was struggling.
Why they ask: to see whether you support the team beyond your own responsibilities.
Approach: show empathy and practical help, without making the colleague look bad.
Sample answer: "A new analyst was struggling with our reporting tool and missing deadlines. I offered three short sessions where we built one of her reports together. I also wrote a one-page guide to the queries we used most. Within a month she was producing reports on time, and the guide is now part of our onboarding."
Conflict and disagreement
4. Tell me about a time you disagreed with your manager.
Why they ask: to see whether you can raise concerns respectfully and accept decisions.
Approach: show that you disagreed with evidence, in private, and handled the outcome professionally, whichever way it went.
Sample answer: "My manager wanted to launch a feature before testing it with customers. I was worried about a confusing step in the flow, so I asked for 30 minutes to show him recordings from two quick user tests. He agreed to a one-week delay to fix that step. After launch, support tickets about the feature were lower than for our previous release."
5. Describe a conflict within your team and how you resolved it.
Why they ask: to test how you handle tension and find solutions.
Approach: focus on the process you used: listening, finding shared goals, agreeing next steps.
Sample answer: "Two colleagues disagreed about whether to prioritise new features or fixing bugs, and meetings were becoming tense. I suggested we list both sets of work with their impact on customers and agree criteria for ranking them. Seeing it laid out, we agreed to fix the three bugs affecting most customers first. The discussion became about criteria instead of opinions."
6. Tell me about a time you had to deal with a difficult customer or stakeholder.
Why they ask: to see how you stay professional under pressure and solve the underlying problem.
Approach: describe how you listened, what you did to fix the real issue, and the outcome for the relationship.
Sample answer: "A large client was angry about repeated delivery delays and threatened to cancel. I scheduled a call, let him explain everything before responding, and then went through the causes with our logistics team. We changed the carrier for his region and I sent him a weekly status update for two months. He renewed the contract that year."
Problem solving and judgement
7. Tell me about a difficult problem you solved.
Why they ask: to see how you analyse problems and decide what to do.
Approach: walk through your reasoning: how you understood the problem, the options you considered and why you chose your approach.
Sample answer: "Our weekly sales report was often wrong, and nobody knew why. I compared the report with the raw data for four weeks and found that refunds were counted twice when processed across two days. I fixed the query, added a check that flags duplicates, and documented the logic. The report has matched finance’s figures every week since."
8. Describe a time you made a decision with incomplete information.
Why they ask: real work rarely has complete information; they want to see sensible judgement.
Approach: explain what you knew, what you did not, how you limited the risk, and how you reviewed the decision later.
Sample answer: "We had to choose a new email supplier before a deadline, but only had trial data for one week. I chose the supplier with the better delivery results so far, but negotiated a monthly contract instead of an annual one and set a review after two months. The results held up, and we then moved to an annual contract at a better price."
9. Tell me about a time you improved a process.
Why they ask: to see initiative and an eye for efficiency.
Approach: describe the problem with the old way, what you changed, and the measurable improvement.
Sample answer: "Invoices were approved by email, and some sat unnoticed for weeks. I set up a simple approval board with reminders and agreed a three-day approval target with the managers involved. Late payments to suppliers dropped sharply within a quarter."
Initiative and leadership
10. Tell me about a time you took the lead without being asked.
Why they ask: to see ownership and initiative, whatever your title.
Approach: show that you saw a need, acted responsibly and involved the right people.
Sample answer: "New team members kept asking the same setup questions. Nobody owned onboarding, so I drafted a checklist and a short guide, asked two colleagues to review it, and shared it with my manager. It is now the official onboarding document, and setup questions in our chat dropped noticeably."
11. Describe a time you motivated others.
Why they ask: to understand how you influence people, with or without authority.
Approach: explain what was holding people back and what you did to change it.
Sample answer: "Our team was tired after a long product launch, and the next project started slowly. I suggested we break it into two-week goals and share progress in a short Friday update, which made the progress visible. Energy improved, and we met the first two milestones on time."
12. Tell me about a time you had to persuade someone.
Why they ask: to see how you use evidence and understand other people’s concerns.
Approach: show that you understood their view, used evidence, and adapted your proposal if needed.
Sample answer: "I wanted our sales team to use a new CRM field to track why deals were lost. They saw it as extra admin. I showed them how the data would help them spot patterns in their own deals and reduced the field to a drop-down with five options. Usage reached most of the team within a month."
Failure and learning
13. Tell me about a time you made a mistake.
Why they ask: to test honesty, ownership and learning.
Approach: choose a real but not catastrophic mistake, take responsibility, explain how you fixed it and what you changed afterwards.
Sample answer: "I once sent a client report with last month’s figures because I reused an old template. The client noticed. I apologised the same day, sent the corrected report within an hour, and created a checklist I now follow for every report. It has not happened again."
14. Describe a time you failed to meet a goal.
Why they ask: to see how you handle setbacks and what you learn.
Approach: be honest about the outcome, focus on what you learned and how you applied it.
Sample answer: "I set a goal to grow our newsletter by 50% in a quarter and reached about 20%. Looking back, I relied on one channel. The next quarter I tested three channels in small amounts first and doubled down on the one that worked, and we exceeded that quarter’s goal."
Pressure and time management
15. Tell me about a time you worked under a tight deadline.
Why they ask: to see how you prioritise and stay effective under pressure.
Approach: show how you planned, what you prioritised or dropped, and how you communicated.
Sample answer: "A client brought a launch forward by two weeks. I listed every task, agreed with the client which could wait until after launch, and told my manager which of my other work would be delayed. We launched on the new date with the essential features, and finished the rest the following week."
16. Describe a time you had too many priorities at once.
Why they ask: to see whether you can choose, not just work harder.
Approach: explain how you decided what mattered most, and how you managed expectations for the rest.
Sample answer: "During month-end close, I was also asked to prepare an audit report. I listed both with their deadlines and consequences, then asked my manager to confirm the order. We agreed to delay a non-urgent reconciliation by two days. Both critical deliverables were on time."
17. Tell me about a stressful situation and how you handled it.
Why they ask: to understand your resilience and how you cope.
Approach: describe the situation, your practical response and how you looked after the quality of the work.
Sample answer: "Our main system went down during a sales event and support requests tripled. I set up a single status update we could link to, grouped similar requests and answered them together, and kept the team updated every hour. We cleared the backlog within a day, and the status-page approach became our standard for outages."
Communication and adaptability
18. Tell me about a time you explained something complex to a non-expert.
Why they ask: to test clarity and empathy in communication.
Approach: show how you understood their level, simplified without losing accuracy, and checked understanding.
Sample answer: "Our finance director needed to understand why our cloud costs had risen. Instead of technical details, I showed a simple chart linking costs to customer usage and three options to reduce them, each with its trade-off. She chose one in the same meeting."
19. Describe a time you had to adapt to a big change at work.
Why they ask: to see flexibility and a constructive attitude.
Approach: describe the change, how you adjusted, and how you helped others or improved the transition.
Sample answer: "When our company moved to fully remote work, our team lost the quick desk conversations we relied on. I proposed a shared daily written update and a weekly call for decisions. After a month, we were sharing more information than before, and new colleagues said the written history helped them catch up."
20. Tell me about a time you learned something new quickly.
Why they ask: to see how you learn, which matters in any changing role.
Approach: show your method: how you found resources, practised and applied the skill.
Sample answer: "I joined a team that used SQL heavily, and I only knew spreadsheets. I took a short online course in the evenings, rebuilt three of my existing reports in SQL as practice, and asked a colleague to review them. Within six weeks I was writing the team’s weekly queries myself."
Mistakes to avoid
- Hypothetical answers: "I would…" instead of "I did…". Use a real example.
- Too much situation, too little action: spend most of the time on what you did.
- "We" throughout: the interviewer needs to know your part.
- No result: always end with what happened and what you learned.
- Invented or exaggerated stories: follow-up questions quickly expose them.
Follow-up questions to expect
Interviewers often dig deeper: "What would you do differently?", "How did the other person react?", "What was the measurable result?", "What did your manager say?". Prepare by thinking through each story in detail, including what did not go well.
Next steps
Write down your five to seven stories in STAR form and practise them out loud. Then read our complete guide to preparing for an interview, and prepare answers to "Tell me about yourself" and "Why should we hire you?". If you are still looking for interviews, browse current openings.