5 exercises — structuring stories with Situation, Task, Action, Result for tech interview questions.
0 / 5 completed
STAR time allocation
Situation (10%) — orient the listener: when, where, what was at stake
Task (10%) — your specific responsibility or challenge
Action (60–70%) — what you specifically did, step by step, using "I"
Result (20%) — quantified outcome + business impact
1 / 5
In a STAR answer, how long should the Situation step ideally be?
The Situation step should consume roughly 10% of your answer — typically 1–2 sentences. Its only job is to orient the listener: when, where, what was at stake. Spending too long on context feels like stalling. The interviewer is waiting for what you did (Action) and what changed because of it (Result). Allocating your time: Situation 10% → Task 10% → Action 60–70% → Result 20%.
2 / 5
Which sentence is the best STAR story opener?
An effective STAR opener immediately signals: role (leading the backend chapter), context (Acme, Q3 2023), and the problem/stake (45-minute deployment windows). The word "While" is a strong opener — it places you inside the situation immediately. Options A and C are vague and informal. Option D wastes time on meta-commentary before you've said anything. Start in the scene, not before it.
3 / 5
In the Action step, which pronoun should you use when describing what you personally did?
The entire point of the Action step is to demonstrate your contribution. Use "I": "I identified the bottleneck", "I proposed the solution", "I led the migration". If you say "we" throughout, the interviewer cannot assess what you specifically did versus what your team did. You can acknowledge team effort briefly — "I coordinated with two other engineers" — but the agency must be yours. Interviewers train themselves to ask follow-up prompts like "What was your specific role?" to extract this.
4 / 5
Which Result statement is the most compelling in a STAR answer?
Strong Results have three elements: (1) specific action reference (parallelising, caching), (2) quantified before/after (45 → 8 min, 6×), (3) business impact (unblocked 3 teams). Numbers are powerful — they make abstract improvements concrete and memorable. Option A is vague ("people were happy"). Option B lacks numbers. Option D is technically true but tells the interviewer nothing specific. Rule: if you don't have numbers, name a concrete business outcome.
5 / 5
Choose the best phrase to bridge from Action to Result: "I rewrote the database queries to use indexed columns _____ query times fell from 800ms to 90ms."
"as a result of which" is a formal, precise connective that links cause directly to effect — ideal for STAR answers because it signals a logical consequence rather than just a sequence of events. Other strong alternatives: "which reduced query times to 90ms", "resulting in a 90ms response time", "cutting query times from 800ms to 90ms". Avoid "and then" (too informal, implies sequence not causation) and "so therefore" (redundant — use one or the other).