How to structure a behavioural interview answer
Behavioural questions ask you to describe something you have done: a time you worked in a team, handled a mistake or persuaded someone. Interviewers use your past behaviour as evidence of how you might act in the job. A good answer is short, specific and honest, and it takes preparation. This guide covers how to choose stories, how to structure them and how to survive the follow-up questions.
Which stories should I prepare?
Prepare five or six real stories rather than twenty answers. Each story should be flexible enough to answer several questions. Good sources are university projects, internships, jobs, student funds, sport, volunteering and anything with stakes and other people. Try to cover:
- a time you led or took ownership
- a time you worked with someone difficult or disagreed
- a mistake or failure and what you changed
- a time you worked under pressure or a tight deadline
- a time you learned something quickly
- a time you showed attention to detail
Write each in a few bullet points, not a script. A memorised speech sounds like one.
What structure should I use?
A common frame is situation, action, result, and many people add a final step for reflection. The idea is the same under any name.
- Situation (one or two sentences). The context and what was at stake. Only enough to make the story clear.
- Task, if useful. What you specifically were responsible for.
- Action (the longest part). What you personally did, in order, and why. Say "I", not "we", where you did it. Name the decision you made at the hard point.
- Result. What happened, with a number if you have one, and what you learned or would do differently.
Aim for about ninety seconds to two minutes. Spend roughly half of it on the action.
How do I quantify without exaggerating?
Numbers make a result concrete, but they must be real. Use what you actually know: a deadline, a count, a percentage, a size of team. If you do not know a figure, describe the outcome plainly.
Weak: "I improved the process and the team was very happy."
Better: "I rebuilt the monthly reporting file so that it reconciled automatically. It took the analyst about two hours instead of a day, and the errors we had been finding each month stopped."
If the number is an estimate, say so: "roughly", "as far as I could tell".
What does a good answer sound like? Three examples
Each example is invented.
Corporate finance internship (pressure). "In my second week, a client presentation was brought forward by a day. I was responsible for the comparable-companies page. I listed what the page had to show, checked with the associate which three metrics mattered most, and did those first. I sent a draft at six that evening with the open points marked, and finished the rest the next morning. The page went in on time, and the associate later asked me to take the same section on the next deal. What I took from it was to confirm priorities before starting."
Student fund (disagreement). "Our team disagreed about whether to buy a retailer. I thought its debt was too high. Rather than argue, I put together a one-page table showing interest cover under three sales scenarios. Two of the three looked fine, and one did not. We agreed to buy half the position we first planned. The stock was flat over the term, so the decision cost us nothing, but I would also say we did not have enough data to know I was right."
Audit job (mistake). "I once used last year's exchange rate in a working paper. A reviewer spotted it. I fixed it that afternoon, told my manager what happened, and then added a check of the rate source to my own review list. It did not recur."
How do I handle the follow-up questions?
The first answer is not the real test. Interviewers often probe: "What exactly did you do?", "What did the other person say?", "What would you do differently?" or "Why that decision?" Be ready to go deeper into any detail you mention. If you cannot discuss it for two more minutes, do not include it.
Three habits help:
- Pause before answering. A two-second pause reads as thought.
- Answer the question asked. If they ask about a failure, do not slide into a success.
- When you do not know or do not remember, say so. "I do not remember the exact figure, but it was around that size" is better than inventing one.
How honest should I be?
Entirely. The stories must be true, the credit should be fairly shared, and the mistakes should be real ones. Interviewers talk to references and to people at your previous employers, and they can often tell when a story has been polished into something it was not. A modest, accurate story with a clear lesson is stronger than an impressive one that falls apart on the second question. Do not blame others to look better, and do not breach confidentiality about a previous employer or client in order to tell the story. Describe the situation in general terms.
What mistakes should I avoid?
- Answering with "we" for the whole story so that your part is unclear.
- A story with no result, or a result that is not connected to your action.
- A "weakness" that is really a strength in disguise.
- Spending most of the time on the situation.
- Using the same story for every question.
- Reading from notes or sounding rehearsed.
What to do this week
- List six real experiences and match each to at least two question types.
- Write each as bullets: situation, your actions, result, lesson.
- Add one honest number or fact to each result.
- Say each aloud and time it. Cut anything over two minutes.
- Ask a friend to ask three follow-up questions on each story, and note where you hesitate.
About this guide: it is original to Charta Learning and has not yet been reviewed by an experienced practitioner. Names and examples are invented. Interviewers differ in the frameworks they like, so treat this structure as a tool and adapt it. Spoken practice can help you rehearse.