'Tell Me About a Time When...' in English: Building a STAR Answer

Halfway through an interview the question changes shape: Tell me about a time when you had to deal with a difficult stakeholder. The factual questions before it ended when you stopped talking. This one does not end by itself, because the interviewer is not waiting for information - they are waiting for four specific things, and they will interrupt as soon as the first one takes too long.

Why behavioural questions are answered differently from factual ones

A factual question has an answer the interviewer can check; How many years have you used Python? takes eight seconds, and extra detail makes it worse. A behavioural question has four answers inside one, and the interviewer fills four boxes while you talk.

The UK National Careers Service defines those boxes as situation, task, action and result. A handout for interviewers published by the Government of the Northwest Territories spells out the check: a clear statement of the situation or task, the action taken, and the result or outcome, all from one specific event rather than a description of how you usually work.

That is why the two types behave so differently. The US Office of Personnel Management describes structured interviews as asking every candidate the same pre-written lead questions and follow-ups, scored against benchmarks set before you arrived; the interviewer is not collecting information from a blank page, but matching your words against a scale.

Chronology is not that scale. Narrating the project in order fills one box for a full minute and leaves the other three empty, and the follow-up, And what did you personally do?, tells you the answer was filed as background.

The four parts of a STAR answer, and how long each takes

The parts are not four equal quarters. A guide published by the University of Washington careers centre suggests roughly 20% situation, 10% task, 60% action and 10% result. The imbalance is the point: the interviewer is buying your decisions, and the decisions live in the action.

Part	What the interviewer is listening for	Share of the answer
Task	What was yours to solve, not the team's remit	about 10%
Action	The decisions you made, including what you rejected	about 60%
Result	What changed, and how you know it changed	about 10%

Those shares turn into seconds once you fix a total. All figures below are in seconds.

Total answer	Situation	Task	Action	Result
90	18	9	54	9
120	24	12	72	12
180	36	18	108	18

Two places where the listener is most often lost. The first is the opening, where background is stacked before the event: I had been working on a project that had already been delayed, and we had had two meetings about it uses three verbs and still has not said what happened. Name the event first in the simple past, then add only the background that is needed.

The second is the pivot into the action, where we takes over: We rebuilt the pipeline and we shipped it in three weeks. The handout written for interviewers lists the use of we as something they are told to watch for, with the follow-up ready: What was your own role in that? If a sentence stays true when every other member of the team says it, it is context, not action.

Choosing the story before the interview

Stories are chosen by competency, not chronology, and before the interview rather than during it. The National Careers Service notes that examples can come from work, home or volunteering, which matters if your job history is short.

Four stories cover most behavioural loops: a disagreement, a mistake you repaired, a deadline you did not set, and a time you had to change someone's mind. Write one card for each, five lines long:

• When and where, with a period or a date
• What was at stake for someone other than you
• The decision that was only yours to make
• What you did first, as a verb
• What changed, with one number or one artefact you can point to

Each card then has to answer three questions: is this one event rather than a habit, was there a decision nobody else was going to make, and can I say how it turned out without guessing?

The action section: what you did, not what the team did

Interviewers are trained to listen for the pronoun, so keep one we for context and then switch. Three moves carry the action section: what you saw, what you chose, and what you did next.

Start with the diagnosis, because it shows judgement rather than effort: I could see that three settings differed between the two environments, so I started there. Then the choice and the road not taken: I considered rebuilding the fixture data and rejected it, because the migration was already frozen. Then the mechanics in verbs, with the person stated: I fixed the setting I owned that afternoon and wrote the other two up for the platform team.

Six stems open the action section cleanly in spoken English, and all six keep the first person:

• The first thing I did was...
• I could see that ... , so I decided to...
• I checked with ... before I...
• I chose ... over ... , because...
• I took it on myself to...
• What I changed was...

Ending on a result you can defend

Two sentences are enough, provided one of them is checkable. A defensible number is one you can rebuild in front of the interviewer: a count you kept, a date you met, a duration you measured. A number you cannot reconstruct is a liability, because the next question is How do you know?

With no number, use a contrast and an artefact: Before the change, every release needed a manual check that took an afternoon. After it, the same check ran inside the pipeline.

The other six stems open the result section:

• In the end...
• The result was ... after ... weeks
• By the time I left...
• It is still ... today
• My manager used the same approach for...
• The number I can point to is...

Then stop. Do not attach a summary of your strengths, and do not add a lesson nobody asked for. Stopping is part of the answer: it gives the interviewer room to ask the follow-up they are already holding.

Four worked answers at 45, 90, 120 and 180 seconds

The four answers below describe the same fictional migration and grow from one decision into a full story. Record yourself on each one and compare it against the timing sheet.

45 seconds: one decision

• Two weeks before a data migration, the test environment started failing every night. (situation)
• My job was to find out why before the freeze. (task)
• I compared the two environments, found three settings that differed, fixed the one I owned and wrote the other two up for the platform team the same afternoon. (action)
• The migration shipped on the closing date and the nightly failures stopped. (result)

90 seconds: stakes, a rejected option, a number

• Two weeks before a data migration the test environment failed every night, and the migration could not move because the quarter closed on the same date. (situation)
• I owned the test environment; the platform team owned the pipeline that fed it. (task)
• I compared the environments setting by setting and found three differences. I considered rebuilding the fixture data and rejected it, because the dataset was already frozen for the release. The setting that was mine I fixed that afternoon; the other two I sent to the platform team with the evidence attached. (action)
• The migration shipped on the closing date, and nightly failures went from five a week to zero. (result)

120 seconds: the disagreement, and the follow-through

• Two weeks before a data migration the test environment failed every night, the quarter closed on the same date, and the platform team believed the fault was in my environment while I believed it was in theirs. (situation)
• I owned the test environment and the release checklist, and I had to hand over a working result rather than an argument. (task)
• Instead of reopening the argument, I built a comparison: the same job run in both environments, with the three differences printed side by side. I took the page to the platform lead and said I would fix the setting that was mine that afternoon if we agreed on the other two before the freeze. He accepted, and I wrote both shared fixes into the release checklist with owners. (action)
• The migration shipped on the closing date, failures went from five a week to zero, and the comparison page became part of the handover document. (result)

180 seconds: learning, and what changed afterwards

• Two weeks before a data migration the test environment failed every night, the quarter closed on the same date, and the platform team and I were pointing at each other's systems. (situation)
• I owned the test environment and the release checklist, and the migration could not move until someone proved where the fault was. (task)
• I stopped arguing and made the fault reproducible: the same job in both environments, with the three differences printed side by side. I showed the page to the platform lead, offered to fix my setting that afternoon if we agreed on the other two before the freeze, and he accepted. I wrote both shared fixes into the release checklist as checkboxes with owners, and asked the platform team to keep the comparison job running afterwards as a monitoring step. (action)
• The migration shipped on the closing date, nightly failures went from five a week to zero, and the two settings became permanent checks in the release process. (result)
• What I would do differently is start the comparison on day one: I spent three days reading logs before building the thing that answered the question in an hour. (learning)

Practising with the most common interview questions in english

Practise the questions, not a script. Behavioural questions cluster around a few competencies, so write the prompts you expect, shuffle them, and answer whichever one comes up. Working from a shuffled list of the most common interview questions in english keeps the rehearsal from turning into a memorised speech. The National Careers Service adds a warning that fits rehearsal: get your points across conversationally, and stay ready for follow-up questions about the example you gave.

Six prompts cover a lot of ground:

• Tell me about a time you disagreed with a colleague.
• Describe a situation where you had to meet a deadline you did not set.
• Give me an example of a mistake you made and what you did next.
• Tell me about a time you had to change someone's mind.
• Tell me about a time you had to learn something quickly.
• Describe a situation where a customer was unhappy with what you did.

A rehearsal loop that needs only a phone:

1. Record one answer without notes.
2. Time the four parts against the sheet above; if the situation runs past its slot, the story is starting too early.
3. Count first-person verbs in the action section. If we outnumbers I, record it again.
4. Listen for the result. With no number and no artefact, add one and record that sentence twice on its own.
5. Play the recording to one other person and ask a single question: what did I do?

With no one to rehearse with, an AI conversation partner closes part of the gap: HiBay offers interview-scenario conversation practice and reports on speaking in bands modelled on IELTS and TOEIC criteria, which catches filler and pace even when it cannot tell you whether the story was the right one.

When you have no example for the question

Three honest moves, in order of preference.

Move the context and keep the behaviour: The closest example I have is from a voluntary project rather than a job - is that useful? The National Careers Service notes that examples can come from work, home or volunteering, so the setting does not disqualify the story; only an unrelated behaviour does.

Give the smaller version and label it as smaller: I have not run a team through a redundancy. What I have done is close a project inside a week when the client moved the launch date. You are not pretending the scale matches; you are handing over something real to score.

Say what you have not done and bridge: I have not handled a formal complaint. I have handled a customer who was given the wrong delivery date, and I did it in writing before I called.

One rule holds across all three: never answer in the hypothetical. I would probably speak to my manager first is not evidence of past behaviour, and the handout written for interviewers lists conditional answers among the responses that cannot be scored. Feelings have the same problem: I am very organised is a preference, while I kept the release checklist for eleven releases is something the interviewer can write down.

Frequently asked questions

How long should a STAR answer be in an English interview?

Aim for 90 to 120 seconds by default. A careers-centre guide published by Duke University puts a strong STAR response at one to two minutes, and 45 seconds is enough for a narrow competency. Use the timing sheet above to hold the shape, with about 60% of the time in the action. Longer answers only work when the panel has asked for depth.

What if I have no example for a behavioural interview question?

Use a real example from outside work and say so in one clause, give a smaller version of the situation and label it as smaller, or state what you have not done and bridge to the nearest thing you have. Then stop and let the interviewer reshape the question. Answering in the hypothetical, as in I would..., is a different question type, and interviewers are told to treat it as an answer they cannot score.