You will be able to answer a tell-me-about-a-time question by giving the situation, the task, what you did and the result.
When an interviewer starts a question with "Tell me about a time" or "Give me an example of", answer with a short story in four parts: the situation, your task, your action and the result. Keep the set-up to two or three sentences, spend most of the answer on what you did, and finish in under two minutes.
A behavioural question asks you to describe how you acted in a past situation. A typical one is "Tell me about a time you had to deal with a difficult stakeholder." These questions usually begin with "Tell me about a time" or "Give me an example of", and most interviews include several of them. They rest on the idea that past behaviour is the best guide to future behaviour. The interviewer wants to hear what you actually did when something similar came up.
The most common mistake is spending too long on the set-up. Picture a candidate who is given the stakeholder question. They start with background on the project, the team and the history with the client. Four minutes later they are still setting the scene. By then the interviewer has stopped taking notes, and the candidate never gets to what they did.
The STAR method gives you a structure for any question that starts "Tell me about a time" or "Give me an example of". The four parts are:
Situation: the context, meaning where you were and what was going on. Task: what you needed to achieve, or the problem you had to solve. Action: what you did about it. Result: what happened, and ideally what you learned.
STAR works because it follows the order the interviewer listens in. They want a little context first, then what you did and whether it worked. The structure also stops you wandering into side details.
Keep the situation and task together to two or three sentences, which takes about twenty to thirty seconds. Extra background slows the answer down, however interesting it is to you.
The action is the heart of the answer and should take roughly half the answer or more. This part shows how you think, what you do when things are unclear, and what skills you bring. Be specific about each step you took, because each separate action can count as evidence of a separate skill.
End with the result, and include a number if you have one. Only use numbers you can explain. That is the same rule as in Lesson 3.2, "Turn duties into results". If you have no exact figure, describe the result without inventing one. Then add one line on what you learned, which shows the interviewer that you reflect on your work.
Most STAR answers should run under two minutes. A short answer leaves room for the interviewer to ask a follow-up question, and the follow-up is often where the best part of the conversation happens.
Wei Ling works in an operations role. In an interview she is asked a problem-solving question, and her full answer takes about ninety seconds.
For the situation, she says that late deliveries in her operation had been rising for three months and nobody knew why. For the task, she says her manager asked her to find which routes were causing it before the quarterly review. Those two sentences are her whole set-up, and they fit well inside twenty to thirty seconds.
The action takes up most of her answer. She pulled six months of delivery data from the warehouse system into Excel. She cleaned the data, because the route codes had changed partway through the period. She built a simple dashboard showing late deliveries by route, driver and time of day, and it showed that most delays came from two routes in the afternoon. To understand why, she met the two drivers and the vendor and found that a loading bay became congested after 2pm. She proposed moving those routes to a morning slot and drafted the new schedule with the vendor.
For the result, she says that within a month late deliveries on those two routes dropped noticeably, and her manager asked her to build the same dashboard for the other depots. She doesn't have an exact percentage, so she gives none. She would only use a figure if she could explain it. Her learning is that data usually points to where the problem is, but you still need to talk to people on the ground to find out why.
Her action section covers pulling data, cleaning it, building a dashboard, spotting a pattern, talking to people and proposing a fix. An interviewer hiring an analyst hears evidence for most of the job in that one part of her answer.
Describe your actions with "I" rather than "we". People who work in close teams naturally say "we". It sounds modest and collaborative, and at work it is often the right instinct. In an interview it causes a problem. The interviewer is assessing you as an individual and can't tell who did what. Some interviewers assume that a candidate who only says "we" was a passenger.
Saying "I" can feel uncomfortable, especially if you were raised to avoid seeming boastful. It helps to think of "I" as being precise about your own part. It does not claim the whole result for yourself. If others contributed, state their part clearly and then state yours. For example: "My manager set up the meeting with the vendor. I prepared the data and proposed the new schedule." Credit the others briefly, then spend the time on your own steps.
Use the same order each time. First, recognise the question from its opening words. Give the situation and task in two or three sentences. Spend most of the answer on your own steps, said with "I". Give the result, with a number only if you can explain it. Add one line on what you learned, and stop before two minutes.
Pick a real problem you solved at work and write it out in the four parts. Then time yourself telling it aloud.
Write one STAR story about a problem you solved at work. Tell it aloud and time yourself. Aim for under two minutes.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).