Interviews and the STAR method

Why it matters

Most technical interviews include behavioural questions, such as "Tell me about a time you...". Employers ask them because past behaviour is a reasonable guide to future behaviour. They want to know how you handle deadlines, mistakes, teamwork, conflict and learning new things. Candidates with strong technical skills often lose offers here because their answers ramble or stay vague.

The STAR method gives your answers a clear shape, and preparing a few STAR stories in advance makes interviews far less stressful.

The core idea: STAR

STAR stands for:

• Situation: the context, briefly. Where were you, and what was going on?
• Task: your responsibility or the goal. What needed to happen, and what was your part?
• Action: what you did, step by step. This is the longest part.
• Result: what happened, ideally with a number, plus what you learned.

A good STAR answer takes about one to two minutes. Spend roughly 15% on Situation and Task together, 60% on Action and 25% on Result.

Worked example

Question: "Tell me about a time you had to deal with a tight deadline."

Rambling answer:

Oh, that happens a lot. In my last project we always had tight
deadlines, so I just worked hard and made sure we got everything done.
I'm good under pressure.

STAR answer:

Situation: In my final-year group project, we were building an app
to track lab equipment bookings. Two weeks before the demo, our
teammate who handled the database left the course.

Task: I volunteered to take over the database work on top of my
front-end tasks, so we could still demo a working app.

Action: First I listed what the database still needed and found that
only three of the eight tables were finished. I asked the team to
cut two "nice to have" features so we could focus. I followed a
tutorial to learn the parts of SQL I didn't know, built the remaining
tables, and wrote a short test script to check bookings couldn't
overlap. I posted a progress update in our group chat every evening
so nobody was surprised.

Result: We demoed on time with all core features working, and we got
the second-highest grade in the class. I learned to cut scope early
instead of hoping to do everything.

Notice the "I" statements in the Action. Interviewers want to know what you did, not what "we" did. Mention the team, but be clear about your own part.

Common behavioural questions

Prepare at least one story for each theme:

• Teamwork: "Tell me about a time you worked on a team project."
• Conflict: "Describe a disagreement with a colleague and how you handled it."
• Mistakes: "Tell me about a time you made a mistake."
• Problem solving: "Describe a difficult problem you solved."
• Learning: "Tell me about a time you had to learn something quickly."
• Initiative: "Tell me about something you improved without being asked."
• Customers or users: "Describe a time you helped a frustrated customer."

Six to eight good stories can cover most questions, because one story can often be adapted. The deadline story above also fits "learning quickly" and "initiative".

Where to find stories

You do not need professional experience. Strong stories come from:

• school, college or bootcamp projects;
• part-time jobs (retail, food service, warehouse, tutoring);
• volunteering, clubs and sports teams;
• personal projects, such as building a website, fixing a car or a computer, or a home lab.

Choose stories where you made a real choice and something changed because of it.

Answering the "mistake" question

Many candidates fear "Tell me about a mistake". Interviewers are checking honesty and learning, not perfection. Pick a real but not disastrous mistake, own it without blaming others, and spend most of the answer on what you did to fix it and what you changed afterwards.

Result: The report went out a day late, which I told my manager about
straight away. Since then I check my calculations against a second
method before sending anything with numbers in it.

Delivering your answers

• Practise out loud, ideally with a friend or by recording yourself. Writing stories down helps; saying them is what matters.
• Keep notes short: a few keywords per story, not a script.
• Pause before answering. "Let me think of a good example" is fine.
• Answer the question asked. If the question is about conflict, the story should have a real disagreement in it.
• End with the result. Do not trail off. A short "...and that's what I learned" closes the answer cleanly.
• Be ready for follow-ups like "What would you do differently?"

At the end, interviewers usually ask whether you have questions. Prepare two or three about the work itself: "What would a typical first month look like?" or "How does the team review each other's work?"

Common mistakes

• No specific example, only general claims ("I'm a hard worker").
• Too much Situation, so the Action gets rushed.
• "We" all the way through, hiding your contribution.
• No result, or a result with no learning.
• Made-up stories. Follow-up questions expose them quickly.

Quick recap

• STAR: Situation, Task, Action (longest, in "I"), Result (with numbers and learning).
• Prepare 6–8 stories covering teamwork, conflict, mistakes, problem solving and learning.
• Draw stories from projects, jobs, volunteering and personal work.
• Practise out loud and prepare questions for the interviewer.

Try it

Open the Do tab. You will write and rehearse STAR answers to three behavioural questions.