Behavioural rounds ("Tell me about a time when...") decide many offers at top companies. The STAR structure keeps answers concrete.
- Situation (1-2 lines): the context - team, product, constraint.
- Task (1 line): what you were responsible for.
- Action (most of the answer): what you did, step by step, and why - "I", not "we".
- Result: the measurable outcome, and what you learned.
Example
"Tell me about a time you disagreed with your manager."
S: Our team planned to launch a payments feature in two weeks. T: I owned the release and saw that refund flows hadn't been load-tested. A: I pulled last quarter's peak refund data, showed my manager we'd likely exceed the provider's rate limit on sale days, and proposed a one-week delay with a staged rollout. When she worried about the marketing date, I offered to launch to 10% of users on time. R: We launched on time to 10%, caught a rate-limit bug on day two that would have affected ~40,000 refunds, and went to 100% a week later. I learned to bring data and an alternative, not just a concern.
What companies look for
- Amazon: stories mapped to the Leadership Principles - Customer Obsession, Ownership, Dive Deep, Bias for Action, Disagree and Commit, Deliver Results. Expect follow-ups that go two or three levels deep.
- Google: "Googleyness and leadership" - collaboration, comfort with ambiguity, doing the right thing, learning.
- Meta: conflict, ownership, growth, driving results in a fast environment.
Build a story bank
Prepare 8-10 stories from your last few roles, each tagged with the themes it covers (conflict, failure, leadership, ambiguity, customer, deadline). One good story can answer several questions.
Mistakes
- "We did..." with no clear personal role.
- No numbers in the result.
- Stories older than 4-5 years for experienced roles.
- Rambling situation; short action.
Practise with a live mock interview - answers built from your resume, then scored follow-ups.