Behavioural Interviews and the STAR Method with Example Answers

What behavioural interviews are

Behavioural questions ask about past situations: "Tell me about a time you…". The idea is that how you acted before predicts how you will act in the job. These questions appear in almost every kind of interview, and large employers such as Amazon build their whole evaluation around them (Amazon process). Freshers can use college projects, internships, clubs, hackathons or part-time work as examples.

The STAR method

STAR gives your answer structure so it stays clear and complete:

• S: Situation. Set the scene briefly: where, when, what was happening (one or two sentences).
• T: Task. What was your responsibility or goal?
• A: Action. What you did, step by step. This is the longest part.
• R: Result. The outcome, with numbers if you can, and what you learnt.

Aim for about two minutes. Spend roughly 15% on situation and task, 60% on action and 25% on result and learning.

Build a story bank (do this first)

Prepare six to eight stories that you can adapt to many questions. Write short notes for each (a few bullet points, not a script). Choose stories about:

1. A time you led or took ownership of something
2. A failure or mistake and what you changed afterwards
3. A conflict or disagreement in a team and how you resolved it
4. Working under a tight deadline or pressure
5. Learning something new and difficult quickly
6. Going beyond what was asked, or improving a process
7. Helping or mentoring someone
8. A decision with incomplete information

For each story, write down: the context, your exact actions, the result with a number, and the lesson.

Example 1: a fresher answer

Question: Tell me about a time you faced a difficult challenge in a team.

"In my final-year project, four of us were building a student attendance app. (S) Two weeks before the demo, we discovered the login module kept failing, and my teammate responsible for it was ill. (T) I volunteered to take it over, even though I had never worked with authentication. (A) I spent two evenings reading the framework documentation, wrote a small test version first, and asked a senior student to review my approach. I then split the remaining work with the others so we could still finish on time. (R) The login worked by the demo, we presented without issues and got the highest grade in our class. I learned to ask for help early and to test risky parts first."

Example 2: an experienced answer

Question: Describe a time you disagreed with a colleague.

"A senior engineer and I disagreed about whether to rewrite a slow reporting service. (S) The service was timing out for large customers. (T) My task was to fix it before the quarter end. I believed a targeted fix would be safer than a rewrite. (A) Instead of arguing, I measured the problem: I profiled the queries, showed that two of them caused over 80% of the delay, and prototyped an index and a query change in a day. I then walked through the data with him, listened to his concerns about long-term maintainability and we agreed to fix the queries now and schedule a refactor later. (R) Response time fell from about 40 seconds to 3 seconds, the customer escalation closed within a week, and we still did the refactor the next quarter."

Make your answers stronger

• Say "I" for your actions, and "we" only for the team result. Interviewers cannot evaluate what you personally did if you always say "we".
• Add numbers: time saved, users, percentage improvement, size of the team.
• Include what you learnt, especially for failure questions.
• Keep the story true. Follow-up questions quickly reveal exaggeration.
• Do not blame others; describe problems neutrally.

Questions to practise with

• Tell me about a time you failed
• Tell me about a time you had to learn something quickly
• Describe a situation where you went beyond your responsibilities
• Tell me about a time you handled a tight deadline
• Give an example of feedback you received and how you acted on it
• Tell me about a time you made a mistake at work or in a project
• Describe a time you persuaded someone

Common mistakes

• Rambling without a clear result
• Describing what the team did instead of your own part
• Choosing a story where nothing went wrong, so there is nothing to learn
• Memorising word for word, so the answer sounds unnatural
• Ending without a result

Practise

Say each story aloud with a timer. Then ask a friend to interrupt with a follow-up such as "What would you do differently?" Combine this with the HR interview answers and the technical checklist.