“Tell me about a time when…”
That opening can make even an experienced candidate forget every useful thing they have done.
Behavioural questions are difficult because you must search your memory, choose a relevant example and organise it while someone waits. The solution is not to predict every possible question. Build a small bank of versatile stories before the interview.
What the interviewer is asking for
Behavioural questions ask for evidence from a past situation. A structured interviewer may use them to explore job-related competencies such as teamwork, judgment, communication or planning.
A general statement is rarely enough:
“I handle pressure well.”
The interviewer needs to understand what pressure looked like, what you personally did and what happened next.
The U.S. Office of Personnel Management describes behavioural interviews as a way of gathering information about actual past behaviour related to the competencies required for a job. South Africa’s Department of Employment and Labour similarly includes challenge and conflict questions in its interview-preparation guidance.
Create eight useful stories
Write down one genuine example for each area:
- A difficult problem you solved.
- A deadline or competing priorities.
- A disagreement or difficult interaction.
- A mistake and your response.
- A time you took initiative.
- A time you supported a team.
- A process you improved.
- Something difficult you learned.
One event can answer several questions. A delayed supplier delivery might show planning, customer communication, teamwork or decision-making, depending on which part you emphasise.
Give each story a short memory label such as “Saturday stock shortage” or “student event venue change.” Those labels are easier to recall than full scripts.
Use STAR, but keep the star of the story visible
STAR stands for Situation, Task, Action and Result.
- Situation: What was happening?
- Task: What were you responsible for?
- Action: What did you do?
- Result: What changed, and what did you learn?
Candidates often spend too long setting the scene. Aim to make the action the largest part of your answer.
Imagine you are asked about an unhappy customer:
Situation: During a busy shift, a customer arrived to collect an order that had not been prepared.
Task: I needed to confirm the problem and find a realistic solution without making promises I could not keep.
Action: I checked the order record, spoke to the packing team and gave the customer two options with accurate timeframes. I also updated the collection note so the next shift understood the arrangement.
Result: The customer chose the later collection, received the order that afternoon and did not need to explain the issue again.
The answer is effective because the candidate’s decisions are visible. It does not claim to have transformed the entire company.
You have stories even without formal employment
Evidence can come from:
- A university or TVET assignment.
- Volunteering.
- A sports team or student society.
- Freelance or informal work.
- Caring responsibilities.
- A personal project with a clear goal.
- Community or faith-based activities.
Name the context honestly. Do not turn helping at a family business into managing a national operation. Employers can still recognise planning, service and responsibility in a small example.
For an entry-level candidate, organising transport and attendance for a community event may demonstrate coordination. Resolving a disagreement during a group assignment may demonstrate communication. The value comes from what you did, not from making the setting sound corporate.
Build a competency map
Next to every story, list the abilities it could demonstrate.
“Saturday stock shortage” might connect to:
- Prioritisation.
- Communication.
- Customer care.
- Problem-solving.
- Remaining calm under pressure.
Before each interview, compare this map with the job advert. Move the most relevant stories to the top of your preparation page.
Do not force an unrelated story into a question. If you need a moment, say, “Let me think of the most relevant example.” A brief pause is better than an answer that never reaches the point.
Prepare for the follow-up
An interviewer may ask:
- What was your personal contribution?
- What would you do differently?
- How did you know the solution worked?
- What did your manager or teammate say?
- What was the final result?
Add truthful details during preparation. If no percentage or formal measurement exists, describe an observable result: the order was delivered, the deadline was met, the complaint was closed or the new checklist was adopted.
Never invent a metric to make the story sound impressive.
Practise flexible recall
Tell each story in 45, 90 and 120 seconds. Change the competency you emphasise each time.
Do not memorise every sentence. Memorise the sequence: setting, responsibility, decisions, result and lesson. This keeps the answer conversational and lets you adapt when a panel asks a follow-up.
A story bank cannot predict an interview. It can make your best evidence easier to retrieve when nerves would otherwise hide it.
Sources and limits
This article synthesises the underlying ideas in original language and examples. It does not reproduce the source transcript or promise a particular interview result.