Interview frameworks

The STAR method, explained for people who have never used it.

Behavioural questions — "tell me about a time…" — are the ones freshers lose most often, not because they have nothing to say, but because the story has no shape. STAR is the shape. Here is what each letter means, how long an answer should run, and four worked examples you can copy the structure from.

What STAR stands for

S

Situation

Set the scene in two or three sentences: where you were, who else was involved, and what was at stake.

Keep it short. Interviewers stop listening once the setup outlasts the story.

T

Task

Say what you personally were responsible for, not what the team or the company was supposed to do.

Use "I" here. This is the line that tells them what to judge you on.

A

Action

The steps you actually took, in order, and why you chose them over the obvious alternative.

Spend about two thirds of the answer here. This is the part they score.

R

Result

What changed because of it — a number if you have one, otherwise an outcome you can point to.

Never end on the action. A story without an ending sounds like nothing happened.

Out loud, a whole STAR answer should land in 60 to 120 seconds. If you are past two minutes, the Situation has usually run long or you are telling two stories at once.

Four worked sample answers

Written at fresher level, from ordinary college and internship situations. Copy the structure, not the sentences.

"Tell me about a time you worked as part of a team."

Why they ask: They want to know what you do when the plan falls apart and nobody is telling you what to fix.

  1. Situation

    Final-year project, four of us building a registration site for our campus tech fest. Two days before the demo, one teammate dropped out for placement prep.

  2. Task

    I owned the backend, so I had to cover his registration forms as well without pushing the demo date back.

  3. Action

    I wrote out everything still unfinished, picked the two items that blocked the demo, and took those myself. I cut the optional seat-map feature, asked another teammate to review my code each evening so nothing broke, and told our tutor about the scope change the same day instead of at the demo.

  4. Result

    The demo ran on schedule, about 40 students registered during the pilot week, and we scored 82%. The thing I took from it was that flagging a scope change early costs you nothing, while hiding it costs you the demo.

Why this works

  • The setup is three sentences; the action is four.
  • "I cut", "I asked", "I told" — the decisions are clearly yours.
  • The result has a number and an honest lesson, not "and we learned teamwork".

"Describe a time something went wrong."

Why they ask: They are checking whether you own a mistake or quietly blame the process.

  1. Situation

    For our annual college fest we printed 300 brochures, and the morning of the event I noticed the QR code on them led to a broken sign-up link.

  2. Task

    I had run the print run, so fixing it before doors opened at 9 was on me.

  3. Action

    I regenerated the code, printed 60 corrected sheets on the office printer and taped those over the wrong ones at the desks we expected traffic at, put the plain URL on the stage backdrop as a backup, and sent the volunteer team a one-line message so they stopped pointing people at the old code.

  4. Result

    We got about 120 sign-ups that day and nobody scanned a broken link. The team kept the "check the code before printing" step in their checklist for the next fest.

Why this works

  • "I had run the print run" — the mistake is owned in one clause, then the answer moves on.
  • The fix is specific enough that you can picture it.
  • It ends with something that outlasted the event.

"Tell me about a time you disagreed with someone."

Why they ask: They want to see whether you argue with evidence and whether the other person is left as the villain.

  1. Situation

    In a group assignment, a teammate wanted a 20-slide deck and I thought a 10-minute walkthrough would land better with our evaluator.

  2. Task

    I needed the group to decide quickly without losing two days of work or making the presentation a contest.

  3. Action

    I suggested we test it instead of arguing: I built the short version in one evening, then asked two seniors which they would rather sit through and why. I showed the group their answers rather than my opinion.

  4. Result

    The group went with the short walkthrough plus a 10-page appendix, so my teammate's content was still there. We scored 8 out of 10, and the appendix is how we present now.

Why this works

  • Nobody in the story is the bad guy.
  • The disagreement was settled with evidence, not rank or volume.
  • Both people's work survived the decision.

"Give me an example of learning something quickly."

Why they ask: "I'm a fast learner" means nothing. They want the method you actually use.

  1. Situation

    On my summer internship, on the third day I was asked to build a weekly Power BI report for six regions. I had only ever used Excel.

  2. Task

    It had to be in front of the sales lead by Friday.

  3. Action

    I read one chapter of the internal guide and copied an existing report's layout instead of starting blank. I wrote my questions down through the day and asked the analyst twice for 20 minutes each, rather than interrupting her every ten minutes.

  4. Result

    The report went out on Thursday, the team started using it in their Monday review, and I was the one who updated it for the rest of the internship.

Why this works

  • It shows a repeatable method: copy a working template, batch your questions.
  • The result is that the work kept being yours, not that you "enjoyed learning".
  • It is short enough to say out loud in about 90 seconds.

The six mistakes that sink behavioural answers

  • The story has no ending

    Fix: Finish with what changed. If you cannot name a result, pick a different story.

  • Ten minutes of context, thirty seconds of action

    Fix: Cap the Situation at two or three sentences and put the weight on what you did.

  • "We" all the way through

    Fix: Say what the team did once, then switch to "I" for the decisions that were yours.

  • A list of duties instead of one event

    Fix: Pick a specific day or week. "I handled customer complaints" is a job description, not a story.

  • A story where someone else fixed it

    Fix: Choose an example where you were the one who acted, even if you were the junior person in the room.

  • Rehearsing word for word

    Fix: Memorise the four beats and the numbers, not the sentences, so it still sounds like you talking.

How to prepare in about an hour

  1. 1

    Pick five real events: a project, an internship or part-time job, a fest or event you organised, something that went badly, and something you fixed.

  2. 2

    Write the four beats for each one — one line per beat, not a script.

  3. 3

    Add the numbers you remember, and be honest when you are estimating.

  4. 4

    Say each one out loud once, on your phone, and check it lands inside two minutes.

  5. 5

    Match your five stories against the questions they are most likely to ask, so you are never inventing a story on the spot.

Twelve questions to practise on

All of these are answered with the same five stories you just prepared.

  • Tell me about a time you worked under pressure.
  • Describe a goal you set and how you reached it.
  • Tell me about a time you failed.
  • Give an example of a time you had to convince someone.
  • Describe a time you took initiative without being asked.
  • Tell me about a time you had to learn something new fast.
  • Describe a conflict with a teammate and how you resolved it.
  • Tell me about a time you juggled multiple deadlines.
  • Give an example of a time you went beyond what was expected.
  • Describe a time you received critical feedback.
  • Tell me about a time you made a decision with incomplete information.
  • Describe a time you helped someone else succeed.

Quick answers

What does STAR stand for?

Situation, Task, Action, Result. You set the scene, name what you were responsible for, describe the steps you took, and close with what changed.

How long should a STAR answer be?

Roughly 60 to 120 seconds spoken. If you are past two minutes, the Situation is usually too long or you are telling two stories at once.

Do I need numbers in the Result?

Not always. If you have a figure, use it. If you do not, name an outcome you can point to: the report kept being used, the client stopped escalating, the tutor asked us to present it to the next batch.

When should I not use STAR?

For technical explanations, "how would you do X" hypotheticals, and motivation questions like why you want the role. STAR is for questions about something that already happened.

What is STAR-L?

The same structure with a Learning at the end. Some interviewers, especially for graduate and fresher roles, want that last line about what you would do differently.

Practise this on your own resume

A list of questions is fine for practice, but the ones that decide your round come from what is actually on your paper. Paste your resume and get questions with model answers, then say them out loud.

Want the resume itself checked first? Scan it for ATS score.

More practice: all interview question guides.