Variants and Common Mistakes

Variants of the structure

Several variations exist. STAR-L (sometimes STARL) adds Learning: what you took away and what you now do differently, which is especially useful for failure and conflict questions. CAR (Context, Action, Result) merges Situation and Task for shorter answers. Some people use SOAR (Situation, Obstacle, Action, Result) to emphasise the difficulty. The labels matter less than the habit: brief context, your specific actions with reasoning, a concrete outcome and reflection. Common mistakes: spending half the answer on background, describing only team actions, stopping without a result, choosing a story that does not answer the question, and drowning the listener in technical detail.

Mistake checklist for a draft answer

Review each story against this list.

[ ] Situation + Task take under ~30 seconds
[ ] The answer matches the question asked (not a favourite story forced in)
[ ] I can point to at least three actions that were mine
[ ] Technical detail is enough to be credible, not a lecture
[ ] There is a clear result (outcome, metric or honest qualitative effect)
[ ] For failure / conflict: there is a learning and a changed behaviour
[ ] No blame directed at named colleagues
[ ] Nothing exaggerated that I could not defend under follow-up

A good pull request description

A strong answer reads like a good PR description: one line of context, what changed and why, and how you verified it. Nobody wants three paragraphs of history before the diff.

Quick check: What does the L in STAR-L add?

• A list of tools used
• Leadership titles held
• Length of the project
• Learning: what you took away and do differently now