Skip to main content

STAR: Situation

The Situation sets the stage. Without clear context, even the best story falls flat. This is where you establish why the story matters.

Learn

What is the Situation?​

The Situation is the context — the who, what, when, and why that frames your story. It answers:

  • Where were you working? (company, team, role)
  • When did this happen? (timeline, deadlines)
  • What was the context? (project, problem, opportunity)
  • Why did it matter? (stakes, impact, urgency)

The Goldilocks rule​

The most common mistake with Situation is getting the length wrong:

Too ShortJust RightToo Long
"We had a project that was behind schedule.""I was a senior engineer on the payments team at a fintech startup. We were 3 weeks from launching our first enterprise client, and our payment processing pipeline was failing 12% of transactions — well above the 0.1% threshold in our SLA."A 5-minute background story covering the company founding, the team's history, three previous projects, and the org chart.

Aim for 2-3 sentences. Enough to understand the stakes, not so much that the interviewer loses the thread.

What makes a strong Situation​

Great Situations share these properties:

  • Specific — Real numbers, real timelines, real stakes
  • Consequential — Clear why this mattered (revenue, customers, deadlines)
  • Scoped — Focused on what's relevant to the story you're about to tell
  • Recent — Ideally from the last 2-3 years (shows current capability)

Red flags interviewers listen for​

  • Vague context: "We had some issues with the project..." (what project? what issues?)
  • No stakes: "I worked on improving our documentation." (why did it matter?)
  • Team-only framing: "Our team decided to..." (what was YOUR role specifically?)
Do

Exercise: Rate these Situations​

Read each Situation and rate it: Weak, Okay, or Strong. Then see the analysis.

Situation A:

"I was working on a project and we had some problems."

→ Weak. No specifics — no role, no company, no stakes, no timeline. The interviewer has no context to evaluate the rest of the story.

Situation B:

"Last year on my team, we were building a new feature and the deadline was tight."

→ Okay. There's a timeline hint and urgency, but still missing: what team? what feature? how tight? what were the consequences of missing it?

Situation C:

"I was the tech lead for a 6-person team at a healthcare SaaS company. We had committed to delivering HIPAA-compliant audit logging to our largest client by Q3, but halfway through the quarter we discovered our event pipeline couldn't handle the throughput — we were dropping 30% of events under peak load."

→ Strong. Role is clear, stakes are specific (HIPAA compliance, largest client, Q3 deadline), the problem is quantified (30% drop), and the scope is well-defined.


Now write your own: Think of a challenging project or decision from your experience. Write a 2-3 sentence Situation that includes your role, the stakes, and a specific detail.

Check

How long should the Situation portion of a STAR answer typically be?

Which element is MOST important to include in a strong Situation?

An interviewer hears: 'We had some challenges with the system.' What's wrong with this Situation?