PickedJobs
All tools

STAR method interview answer builder

Shape a behavioral answer into Situation, Task, Action and Result.

Free, no sign-up. Checks run in your browser; AI coaching is optional.

Where and when; just enough context.

What you were responsible for, and the stakes.

What you did, step by step, and why. Say “I”.

What changed, in numbers if you can, and what you learned.

Spoken length

0:52

129 words at 150 words a minute

Share of the answer by part, with the suggested range
Situation14%aim 10–20%
Task14%aim 10–15%
Action43%aim 45–60%
Result29%aim 15–25%

  • Pass: Action carries the answer

  • Pass: Result is measurable

  • Pass: A good length

  • Pass: Clear about your own role

Your answer

Tell me about a time you solved a difficult technical problem. Our checkout API started timing out during peak traffic after a marketing launch, and error rates reached 4%. As the on-call backend engineer, I had to find the cause and stabilize checkout before a weekend sale. I traced the slow requests to an N+1 query in the pricing service using our APM traces. I replaced it with a batched query, added a short-lived Redis cache for price lookups, and load-tested the fix at twice our peak traffic. I rolled it out behind a feature flag so we could switch back instantly. p95 latency dropped from 2.1 seconds to 280 ms and errors fell below 0.1%. The sale processed 30% more orders than our previous record without an incident, and I added an alert so we catch similar regressions early.

AI coach

Feedback on your story and a tighter version written to be said out loud.

 

AI is optional. When you use it, the text above is sent to Anthropic's Claude to write the result. We don't store it and it isn't used for training. Check the result before you use it.

How to use the STAR method

  • Situation: set the scene in one or two sentences: the team, the product, the problem.
  • Task: say what you were responsible for and why it mattered.
  • Action: walk through what you did and the choices you made. This is where interviewers learn how you work.
  • Result: finish with the outcome, measured if possible, and what you would repeat or change.

Common mistakes

  • Spending half the answer on background. Interviewers need context, not history.
  • Describing what the team did instead of your own part.
  • Ending without a result, or with a vague one like “it went well”.
  • Picking a story with no real difficulty. The best stories involve a trade-off, a risk or a disagreement.

Many of the same stories make strong resume bullets: the action and result often fit in one line.

Frequently asked questions

What is the STAR method?

A way to structure answers to behavioral questions such as “Tell me about a time when…”. You describe the Situation, your Task, the Actions you took and the Result, in that order.

How long should a STAR answer be?

About one and a half to two minutes when spoken, roughly 200–300 words. Interviewers can ask follow-up questions if they want more detail.

Which part of a STAR answer matters most?

The Action. Spend about half your answer on what you personally did and why, and keep the Situation and Task to a sentence or two each.

Should I say “I” or “we”?

Say “I” for what you did. Interviewers are assessing you, not your team. Use “we” only for genuinely shared work, and then explain your part.

How many STAR stories should I prepare?

Six to eight strong stories cover most interviews: a hard technical problem, a conflict, a failure, leadership, a tight deadline, and a time you influenced a decision. One story can often answer several questions.

Related tools

All free tools