Orava

Structured interview answers

How to turn your experience into STAR interview answers

Updated Oct 6, 2026

STAR is easy to describe and hard to do under pressure. Most weak answers follow the format and still fail, because the format was never the hard part. Choosing the moment and the decision inside it is.

What each part of STAR is for

STAR stands for situation, task, action and result. Most guides stop there. It is more useful to know what the interviewer does with each part, because that tells you how much of your two minutes each one deserves.

The situation lets them place the story: where you were, how big it was, what was at stake. One or two sentences. Every extra sentence here delays the part they're scoring.

The task tells them what was yours. Not the team's goal, your piece of it. This is the sentence that stops the answer from turning into a project summary.

The action is what they score. It should be the longest part of the answer, told in the first person, in the order you did things. Inside it there should be at least one decision: a point where you could have done something else and chose not to.

The result closes the loop. A number if you have one, an observable change if you don't, and ideally one sentence on what you learned or would do differently.

STAR as written has no slot for the decision or the reflection, and those are the two things that separate a strong answer from a tidy one. The worksheet below adds both.

The worksheet

Do this on paper or in a document, one story per page. The first one is slow. By the third you'll find yourself looking for the decision before anything else.

0. Pick the moment, not the project

Name one specific week or meeting where something turned. "The rollout" is a project. "The Tuesday we found the data was wrong two days before launch" is a moment.

1. Situation, in one sentence

Where were you, what was the work, and what was at stake if it went wrong? Cut anything the interviewer doesn't need to follow the rest.

2. Task: what was yours

Finish the sentence "My job was to ___." If the honest answer is "help", find a narrower story.

3. The decision

"I could have ___ or ___. I chose ___ because ___." Write down what the choice cost you. If there was no real alternative, there was no decision, and the story is weaker than it feels.

4. Actions, in order

Two to four things you did, starting each with "I". Note who you spoke to and what you said, because the follow-up will ask.

5. Result

What changed, with a number if you have one. Then what happened after: did it stick, did anyone reuse it, did it change how the team works?

6. Reflection

One thing you'd do differently. Make it specific enough that it changes behavior, not "communicate earlier".

7. The twenty-second test

Say the whole story in twenty seconds: moment, decision, result. If you can't, you don't know what the story is about yet, and the two-minute version will ramble.

If you're not sure which experiences to build worksheets for, start from the job posting. Its requirements tell you which skills the interviewer will be probing, and you want at least one story per requirement. Running your resume against the posting in the resume-to-job-description comparison gives you that list quickly.

Before and after: a deadline story

Example: before

"Tell me about a time you worked under a tight deadline."

"So at my last company we were migrating our customer data to a new CRM, which was a big project across sales, support and marketing, and there were a lot of stakeholders involved. Note 1 The timeline was really tight because the old contract was ending. We had some issues with the data quality, so we worked really hard Note 2 and we managed to get it done on time, and everyone was happy with it. Note 3"

  1. Half the answer is situation. The interviewer still doesn't know what the candidate's job was.
  2. "We worked really hard" is the whole action. There's no decision, and every "we" hides who did what.
  3. "Everyone was happy" isn't a result. The interviewer can't score it, so they'll spend the next question digging for one.

Example: after

"I was the analyst responsible for data quality on our CRM migration, and the old contract ended on a fixed date. Note 1 Two weeks out, I found that about a fifth of customer records had duplicate accounts the new system would reject. I had two options: clean everything, which would miss the date, or migrate the clean records on time and quarantine the duplicates. I chose the second, because the accounts that mattered for renewals that month were almost all clean. Note 2 I wrote the matching rules, agreed with the support lead that her team would resolve the quarantined records in the first month, and set up a weekly count so nobody lost track of them. We switched over on the contract date. The quarantine was cleared in five weeks, a week over plan. Note 3 If I did it again, I'd run the duplicate check at the start of the project, not near the end."

  1. Situation and task in one sentence each. The ownership is clear before the story starts.
  2. A decision with two named options and a reason. This is the sentence the interviewer writes down.
  3. A result with a date, an honest miss and a reflection specific enough to change behavior next time.

Composite answers written for this page, not a real candidate.

Before and after: a mistake story

Example: before

"Tell me about a mistake you made."

"I think my biggest mistake is that I sometimes take on too much because I care about doing a good job. Note 1 On one project I said yes to too many things, but I learned to prioritize better. Note 2"

  1. A strength wearing a mistake's clothes. Interviewers hear this one constantly and it reads as evasive.
  2. No consequence and no change. The interviewer learns nothing about how the candidate handles being wrong.

Example: after

"I sent a pricing change to all of our customers a day early. I'd misread the scheduled date in the email tool, and about two hundred customers saw the new price before sales had told their accounts. Note 1 I told my manager within the hour, before anyone escalated it. Then I wrote the correction email and sent the sales team a list of affected accounts sorted by contract size, so they could call the biggest ones first. Note 2 We didn't lose any accounts over it, but two sales reps had awkward calls they shouldn't have had to make. Since then, every scheduled send in our team gets a second person to check the date and the list. Note 3"

  1. A real mistake with a real consequence for other people.
  2. Ownership first, then actions that reduced the damage for the people affected.
  3. An honest cost and a process change that still exists. That's what makes a mistake story count in your favor.

Composite answers written for this page, not a real candidate.

Failure modes worth checking for

The story that buries the result

You get to the outcome at minute three, and by then the interviewer has interrupted with a follow-up. Fix it by saying the result early, in your first or second sentence, and then explaining how you got there. It feels backward. It works, because the interviewer listens to the rest knowing why it matters.

The answer with no decision in it

Everything happened in a sensible order and nothing was ever in doubt. These answers sound competent and score badly, because the interviewer has nothing to evaluate. If your story has no fork in it, look for the moment someone disagreed with you, or the thing you chose not to do.

The "we" answer

Credit-sharing is a good habit at work and a bad one in an interview. You can name the team once. After that, every sentence about the action should be about what you did. Interviewers will ask "what was your part?" if you don't, and the follow-up costs you time.

The memorized script

A word-for-word answer sounds recited, and when you lose your place you blank completely. Memorize the moment, the decision and the result. Let the sentences in between come out differently each time you say them.

The answer that only exists on paper

Written answers hide rambling. The only way to know whether a story fits in two minutes is to say it out loud with a timer running. Most first attempts run long, usually in the situation.

One story, several questions

A good worksheet story answers more than one question. The CRM story above answers "a tight deadline" just as well as "a time you found a problem late". Once you have six or seven solid worksheets, you can cover most of a standard behavioral round, including the common questions on the behavioral interview questions page. If you're a manager, the same worksheet applies to leadership stories, with a few extra topics covered in the engineering manager interview guide. If your best stories come from a different career, the career change interview page shows how to bridge them.

Hear how your answer actually sounds

Take one worksheet story and say it out loud. Orava asks the question, follows up like a real interviewer and scores your answer on clarity, structure and confidence, so you can see where it rambles before the interview does.

Practice this answer

Tonight: one story, start to finish

Pick the requirement in your target job you feel least ready to talk about. Find one moment from your work that fits it, and fill in the worksheet, decision first. Run the twenty-second test. Then say the full answer out loud with a timer and cut whatever you said before you reached the decision. One finished story is worth more than ten half-written ones.