The STAR Framework — Structure Your Stories

Every behavioural interview answer follows the same skeleton. Master it once, use it everywhere.

Why STAR Works

Interviewers evaluate structure, not stories. A well-structured average story beats a rambling great one.

• Situation — 2-3 sentences of context (project, team, timeline)
• Task — What was YOUR specific responsibility or challenge?
• Action — The meat of your answer — what YOU did, decided, built
• Result — Quantified impact, business outcome, lessons learned

Good vs Bad STAR Answers

| Element | Bad Answer | Good Answer | |---------|-----------|-------------| | Situation | "So our team was working on this project for a while and there were some problems..." | "On a 6-person team building our payments microservice, we hit 500ms p99 latency — 3x our SLA." | | Task | "I had to fix things." | "As the tech lead, I owned reducing latency to under 200ms within 2 sprints." | | Action | "We tried some stuff and it worked." | "I profiled the hot path, identified N+1 queries, introduced Redis caching, and ran A/B tests." | | Result | "It got better." | "Latency dropped to 120ms (76% reduction), saving an estimated £200K/year in SLA penalties." |

Template for 5 Common Questions

1. "Tell me about a time you led a project"

• S: Project scope, team size, business context
• T: Your leadership role and the target outcome
• A: How you planned, delegated, unblocked, and communicated
• R: Delivery metrics, team growth, business impact

2. "Describe a technical challenge you solved"

• S: System, scale, symptoms of the problem
• T: The specific technical goal you owned
• A: Investigation steps, tools used, solution designed
• R: Performance numbers, reliability improvement, cost savings

3. "Tell me about a time you disagreed with your team"

• S: The decision point and conflicting viewpoints
• T: What you needed to resolve and why it mattered
• A: How you listened, presented data, found compromise
• R: The outcome and what you learned about collaboration

4. "Describe a failure and what you learned"

• S: The project and what went wrong
• T: Your role in the failure
• A: How you identified the root cause and responded
• R: The recovery, the lesson, and what you changed going forward

5. "Tell me about a time you built or evaluated an AI solution"

• S: The business problem and why AI was considered
• T: Your role in evaluation, design, or implementation
• A: How you assessed feasibility, chose the approach, handled data/ethics
• R: Model performance, business value, lessons about AI in production

Build Your Story Bank

Don't improvise in interviews. Prepare 6-8 stories that cover the major categories.

How to Build Your Bank

1. List your last 3-4 projects — each should yield 2-3 stories
2. Map each story to categories — one story can cover multiple themes
3. Write bullet-point STAR outlines — not full scripts, just key points
4. Quantify every Result — if you can't measure it, estimate it
5. Practice out loud — aim for 2-3 minutes per story

Practice Checklist

• [ ] I have at least 6 stories mapped to the 5 categories
• [ ] Each story has quantified results (numbers, percentages, £/$ values)
• [ ] I use "I" more than "we" in the Action section
• [ ] Each story fits within 2-3 minutes when spoken aloud
• [ ] I have at least 1 AI-related story prepared
• [ ] I've practised with a timer and a friend or recording