Behavioural Interviews
Behavioural interviews predict how you will work with others. Prepare stories, not scripts.
The STAR method
| Letter | Meaning | Share of answer |
|---|---|---|
| Situation | Brief context | 10-15% |
| Task | Your responsibility or goal | 10-15% |
| Action | What you did, step by step | 50-60% |
| Result | Outcome, ideally measured, plus what you learned | 15-20% |
Build a story bank
Prepare 5 to 6 stories from projects, internships, college or hackathons. Each should map to several themes.
Story: "Group project deadline slipped"
Themes: conflict, leadership, ownership, ambiguity
S: 4-person capstone, backend 2 weeks behind
T: I owned the API layer
A: Re-scoped features, split tasks, paired with a teammate, daily 10-min sync
R: Shipped on time; the demo won best project; I now write weekly plans
Common questions by theme
| Theme | Example questions |
|---|---|
| Conflict | Tell me about a disagreement with a teammate. |
| Failure | Describe a time you failed. What did you change? |
| Leadership | When did you lead without authority? |
| Ownership | Tell me about a time you went beyond your role. |
| Ambiguity | Describe a project with unclear requirements. |
| Learning | What is the hardest thing you learned recently? |
| Motivation | Why this company? Why this role? |
Example answer (failure)
Situation: In my second-year project our app crashed during the demo. Task: I was responsible for deployment. Action: I had tested only locally and skipped load testing. After the demo I wrote a deployment checklist, added a staging environment and ran a load test with 50 users. Result: The next demo ran without incidents, and I now always test in a production-like environment first.
Do and don't
- Do use "I" for your actions and give credit to teammates.
- Do be honest; interviewers probe details.
- Don't blame others or pick a "weakness" that is really a strength.
- Don't ramble: keep answers to about 2 minutes.
Questions to ask at the end
- What does success look like in the first 6 months?
- How does the team handle code review and on-call?
- What is the most challenging problem the team is working on?
Loading Comments...