STAR in one pictureCore idea
%%{init: {"look":"handDrawn","handDrawnSeed":7,"theme":"base","fontFamily":"Virgil, \"Segoe Print\", \"Comic Sans MS\", cursive","themeVariables":{"fontFamily":"Virgil, \"Segoe Print\", \"Comic Sans MS\", cursive","fontSize":"16px","primaryColor":"#fff4e6","primaryBorderColor":"#1e1e1e","primaryTextColor":"#1e1e1e","secondaryColor":"#e7f5ff","tertiaryColor":"#ebfbee","lineColor":"#1e1e1e","textColor":"#1e1e1e","mainBkg":"#fff4e6","nodeBorder":"#1e1e1e","clusterBkg":"#f8f9fa","edgeLabelBackground":"#ffffff","actorBkg":"#e7f5ff","actorBorder":"#1e1e1e","noteBkgColor":"#fff9db","noteBorderColor":"#1e1e1e"}}}%%
graph LR
S["S · Situation<br/>set the scene"] --> T["T · Task<br/>your responsibility"]
T --> A["A · Action<br/>what YOU did"]
A --> R["R · Result<br/>the outcome, in numbers"]
class S blue
class T violet
class A orange
class R green
classDef orange fill:#ffd8a8,stroke:#1e1e1e,color:#1e1e1e
classDef blue fill:#a5d8ff,stroke:#1e1e1e,color:#1e1e1e
classDef green fill:#b2f2bb,stroke:#1e1e1e,color:#1e1e1e
classDef red fill:#ffc9c9,stroke:#1e1e1e,color:#1e1e1e
classDef violet fill:#d0bfff,stroke:#1e1e1e,color:#1e1e1e
classDef yellow fill:#ffec99,stroke:#1e1e1e,color:#1e1e1e
classDef grey fill:#e9ecef,stroke:#1e1e1e,color:#1e1e1eSpend 50–60% of your answer on the Action. That is the part that shows your own contribution; the rest is there to make it make sense.
The four parts, with an exampleHow it works
STAR stands for Situation, Task, Action, Result. Here is one story told through all four.
Situation: set the context
Describe the project, team or challenge in 1–2 sentences. Be specific: the company, your role and the timeframe. Avoid vague openers like “at my previous job.”
Task: your responsibility
What were you asked to do, and what was the goal? This shows what you owned and what was at stake.
Action: what YOU did
Not the team: you. Use “I”. Be specific about the technical decisions, the trade-offs and the steps. This is the longest part.
Result: the measurable outcome
Use numbers: latency down by X%, revenue up by $Y, errors down by Z%. If the result was bad, say what you learned.
The same story, told in STAR
Situation
At XYZ Corp, I was the tech lead for the payments team. We were migrating from a monolithic architecture to microservices, and the payment processing latency had increased from 200ms to 2 seconds after the initial migration.
Task
I was responsible for identifying the root cause of the latency increase and reducing payment processing time back to under 300ms without interrupting live transactions.
Action
I profiled the payment service and discovered three sequential HTTP calls to the fraud detection service. I redesigned the flow to make two of the three calls asynchronous using a message queue, and added a Redis cache for the third call since the fraud score was deterministic for the same user and amount. I also introduced a circuit breaker to handle fraud service failures gracefully.
Result
Payment processing latency dropped from 2 seconds to 180ms. The migration completed successfully with zero downtime. The pattern was adopted by two other teams, reducing their migration time by 40%.
Common STAR mistakesPitfalls
Build your STAR story bankPrepare
Prepare a story for each of these common themes. One good story can often answer two or three of them.
Disagreement
A time you disagreed with a technical decision.
Leading without authority
A time you led when you were not the manager.
Failure
A time you failed, and what you learned.
Incomplete information
A time you had to decide without all the facts.
Growing others
A time you mentored someone or improved a process.
Production incident
A time you handled something breaking in production.
Frequently asked questionsFAQ
How long should a STAR answer be?
A STAR answer should run 2 to 3 minutes, roughly 250 to 350 spoken words. Spend about 20 percent on Situation and Task, 50 to 60 percent on Action, and 20 to 25 percent on Result. Practice each story with a timer so you can compress background detail and keep the focus on what you personally did.
How many STAR stories should I prepare before a behavioral interview?
Prepare 5 to 8 STAR stories, and make sure each one covers a different competency. Good themes include leadership without authority, conflict with a teammate, a failure and what you learned, a technical challenge, cross-team collaboration, and a production incident. Each story should be flexible enough to answer two or three different phrasings of the same question.
What if I do not have a measurable result for a STAR story?
Use a concrete before-and-after comparison instead of a percentage. Say things like review time dropped from 3.5 days to 1.2 days, or the process was adopted by three other teams. If nothing improved, state that plainly and describe the specific lesson you took away, which interviewers accept when it is honest and specific.