Back to Blog
By
•12 min read•Updated

STAR Method Interview: How to Answer Behavioural Questions (With Examples)

Where the STAR method is actually expected in UK recruitment, where it is only a useful shape, one full answer written out and marked up section by section, and the weak version of the same answer.

The invitation says the interview is competency-based, or the application form has a box asking for an example of a time you delivered under pressure, and you have to turn something that happened at work eighteen months ago into an answer a panel can score. STAR is the structure most UK recruiters expect that answer to have.

This page covers where STAR is genuinely expected, where it is only a useful shape, and what a complete answer looks like. The centrepiece is one full answer written out as it would be spoken, then marked up line by line, followed by the weak version of the same story. Both are written for a fictional candidate, so swap in your own facts.

What STAR Stands For

The National Careers Service defines the four parts as the situation you had to deal with, the task you were given to do, the action you took, and "what happened as a result of your action and what you learned from the experience". That last clause is the one candidates drop.

LetterMeaningWhat to cover
SSituationWhere you were, when, and what was going wrong. One or two sentences.
TTaskWhat you were responsible for. One sentence, and it must be yours rather than the team's.
AActionThe steps you took and why you chose them. The longest part. "I", not "we".
RResultWhat changed, with a number or a concrete outcome, plus what you learned.

GOV.UK's guide to competencies gives the same structure and adds the split most people get wrong: "Keep the situation and task parts brief. Concentrate on the action and the result." It also asks candidates to focus on the "how" and to be clear about what they personally did.

Where STAR Is Expected, and Where It Is Just a Useful Shape

In UK public-sector recruitment, STAR is named in the official guidance. Success Profiles is the recruitment framework used within the Civil Service, and behaviours are one of its five elements, defined as "the actions and activities that people do which result in effective performance in a job". The GOV.UK guide to Civil Service behaviours tells candidates directly: "In your own examples, consider using the STAR method which allows you to set the scene, show what and how you did and the overall outcome."

The same guide removes some of the pressure people put on themselves: "There is no expectation that you need to demonstrate every part of each example to be successful." A thin Task sentence is not a failed answer. How behaviours and strengths are scored is covered in the Success Profiles guide.

Outside the public sector, almost nobody names STAR. A private-sector panel scores you against the criteria in the advert, not against an acronym, and a candidate who announces "Situation: in my last role..." sounds like someone reading a framework rather than telling you what happened. The National Careers Service asks you to "try to get your points across in a conversational way so as not to appear too rehearsed", which is the whole argument in one line.

My position: STAR is a checklist you use before the interview and a shape you keep in your head during it. Written application forms are the exception. In a box that asks for an example against a named behaviour, labelling the parts helps the person marking it find the evidence, and I would use the labels there.

One Answer, Written Out in Full

Nadia is a fictional candidate applying for a customer operations team leader job at a water company. The question is one of the most common there is: "Tell me about a time you improved something that was not working." Here is her whole answer, as it would be spoken. It runs to about 105 seconds.

"When I joined the billing support team we had a backlog of about 400 unresolved complaints, and roughly a quarter of them were more than six weeks old. Complaints over eight weeks old can go to the ombudsman, so the age of that queue was the risk, not just the size of it.

I wasn't the manager. I was the senior adviser, and my job was to clear my own share of the queue, but I asked for two weeks to look at why it kept growing.

I read the last hundred cases and sorted them by what had actually stalled them. Two thirds were waiting on a meter reading from the field team, and we were emailing a shared inbox that nobody owned. I took that to our team manager with the numbers, and proposed one change: a single named contact in the field team and a twice-weekly list of readings we needed, oldest first. I built the list myself in a spreadsheet so it cost nobody any set-up time, and I agreed with the field supervisor that anything over four weeks old came first. I also took the twelve oldest cases myself so the team could see them close.

After six weeks the backlog was under 120 cases and nothing was older than five weeks, so nothing reached the ombudsman from that queue that quarter. The list is still running. What I took from it is that I assumed we had a staffing problem until I read the cases, and it was a handover problem."

The same answer, marked up

PartThe lineWhat it is doing
S"a backlog of about 400 unresolved complaints... a quarter more than six weeks old"Scale in one sentence. "About" is doing useful work: it is honest and it survives a follow-up question.
S"Complaints over eight weeks old can go to the ombudsman"Says why it mattered. Without this the panel has to guess whether 400 is a lot.
T"I wasn't the manager... I asked for two weeks to look at why"Separates what she was given from what she took on. For a team leader job, taking it on is the point.
A"I read the last hundred cases and sorted them by what had actually stalled them"A method, not an intention. The panel can picture her doing it.
A"Two thirds were waiting on a meter reading... nobody owned"The diagnosis, with the evidence that produced it. This is the sentence that makes the rest credible.
A"proposed one change... I built the list myself so it cost nobody any set-up time"Shows judgement about other people's workload, which is a team leader behaviour in itself.
A"I took the twelve oldest cases myself"One concrete personal cost. It stops the answer being a description of a process.
R"under 120 cases and nothing older than five weeks"Two numbers that answer the risk named in the Situation, not a generic improvement.
R"The list is still running"Evidence the fix held after she stopped pushing it. Panels notice the difference between a sprint and a change.
R"I assumed we had a staffing problem... it was a handover problem"The learning the National Careers Service asks for, and it admits something. That reads as honest rather than rehearsed.

Note the proportions: Situation and Task take about 25 seconds of the 105, the Action about 55, and the Result about 25. Note also that she never says the word "situation".

The weak version of the same story

Same candidate, same events, unprepared. This is closer to what most first attempts sound like.

"So in my last role we had a really big backlog of complaints, it had been building up for a while before I got there and it was a difficult team to be honest, people were leaving and the field side were not very responsive. We knew we had to do something about it so we all pulled together and got organised, and I was heavily involved in that. We put some new processes in place around how we chased things up and I think we got a lot better at communicating. It made a big difference and customers were a lot happier by the end, and my manager was really pleased with how we'd turned it around."

  • "Really big backlog" gives the panel nothing to score. One number fixes it.
  • "It had been building up before I got there" and "a difficult team to be honest" spend the opening on blame. The panel is not scoring the old team.
  • "We knew we had to do something" is the Task missing entirely. Nobody asked her to do anything; she volunteered, which was the best fact in the story, and she has cut it.
  • "We all pulled together and got organised" is the Action replaced by a mood. There is no method, no diagnosis and no decision.
  • "I was heavily involved" is the sentence that sinks it. Every "we" in an Action section costs you the credit for the part you actually did.
  • "Some new processes". Which ones? The whole answer turns on one specific change.
  • "It made a big difference" is a result with no evidence. So is a pleased manager.
  • No learning, so the panel cannot tell whether she would spot it faster next time.

The gap between the two answers is not confidence or vocabulary. It is twenty minutes of preparation: one number for the scale, one for the result, the name of the thing that was broken, and the decision that was hers.

Building Your Story Bank

Prepare six to eight stories, not twenty. Each one should be able to bend to several questions depending on which part you emphasise. The rescue-the-backlog story above answers questions about improvement, influencing without authority, and working with another team.

Map them to the advert. Take the essential criteria or the named behaviours and check you have a story for each. Any criterion with no story attached is the one you will be asked about.

Find the numbers before the day. Go back through old reports, dashboards or emails and dig out the before-and-after figures while you can still check them. If you cannot check, say "about" and be ready to explain how you know. Strong action verbs help you describe the action tightly, on paper and out loud.

Non-work examples count. The National Careers Service says to "use examples that work for you - these could be from work, home or volunteering". Trustee work, running a club, a course project: say where it comes from in half a sentence and then answer it exactly as you would a work example.

Prepare for the follow-up, not just the answer. The same page tells you to "be prepared to answer follow-up questions about the examples you give". For each story, write down the two questions you would least like to be asked: usually "what would you do differently?" and "how did the people affected react?"

Say them out loud. In a study by Tross and Maurer (Journal of Occupational and Organizational Psychology, 2008), 144 participants were given one of three levels of coaching before a structured experience-based interview: an introduction only, an introduction plus awareness training, or both plus skill training. Those who had the more comprehensive coaching received higher interview ratings. Rehearsal also catches the answer that runs to four minutes.

Behavioural Questions by Competency

Interviewers usually signal the competency in the question. Use this list to check your story bank has the coverage.

Leadership and making decisions

  • "Tell me about a time you led a team through a difficult situation."
  • "Describe a decision you made without all the information you needed."
  • "Give me an example of when you dealt with someone who was underperforming."

Working with others

  • "Describe a disagreement with a colleague and how you resolved it."
  • "Tell me about a time you had to get something from a team you had no authority over."
  • "Give me an example of working with someone whose style was very different from yours."

Problem solving and improvement

  • "Tell me about a time you spotted a problem nobody had raised."
  • "Describe a situation where you had to analyse complex information to decide something."
  • "Give me an example of a change you made that stuck."

Resilience and handling failure

  • "Tell me about a time you failed and what you learned."
  • "Describe a time things did not go to plan. What did you do?"
  • "Tell me about the most difficult professional situation you have faced."

Delivering at pace and prioritising

  • "Tell me about a time you managed several priorities at once."
  • "Describe a situation with a tight deadline. How did you handle it?"
  • "Give me an example of saying no to a request to protect higher-priority work."

Two More Worked Examples

Both are written for fictional candidates. The point of reading them is the proportions and the level of detail, not the content.

Conflict: a disagreement that was slowing a project down

Question: "Describe a situation where you disagreed with a colleague and how you resolved it."

S: "I was leading a product launch with a colleague from engineering. I thought the launch date was fixed by a commercial commitment; he thought the scope had to shrink to hit it safely. Two weeks of the plan went by with nothing agreed."

T: "As project lead I had to land a plan we would both stand behind, without going over his head to his manager."

A: "I asked for an hour with him and no slides. It turned out I had never told him what missing the date cost commercially, and he had never shown me which two components carried the technical risk. Once both were on the table we scoped a phased launch: the core journey on the commercial date, the rest three weeks later. I wrote it up the same afternoon and took it to the sponsor with his name on it as well as mine."

R: "The core launch went out on the original date and the second phase followed five weeks later, two weeks late but with nothing broken. We worked together on two projects after that. What I changed is that I now share the commercial constraint at the start rather than defending the date at the end."

Failure: a mistake that was genuinely yours

Question: "Tell me about a time you failed and what you learned from it."

S: "In my first year as an account manager I handled a renewal on my own for the first time. I misread a message about our floor price and offered the client a discount below it, verbally, on a call."

T: "I had committed a number I could not honour, and I had to sort out both the client's expectation and the internal problem I had created."

A: "I told my manager the same afternoon rather than waiting to see whether the client accepted. We agreed I would go back, say the mistake was mine, and put a revised figure with an extra training day alongside it. I made the call myself; I did not let my manager do it for me."

R: "The client took the revised price and renewed. The change I made is that I now confirm any price in writing before I say it out loud, and I have not repeated it in four years of renewals."

What Goes Wrong Most Often

"We" all the way through the Action. The panel cannot score a team. Say "I proposed", "I built", "I decided", even when the outcome belonged to everyone.

A Situation that eats half the answer. If you are still setting the scene at 40 seconds, cut it. Keep only the facts the Result will refer back to.

A result with no evidence. "It went really well" is not a result. If you cannot quantify it, name the concrete change: the process was adopted elsewhere, the client renewed, the audit finding closed.

A story where you watched. Pick examples where you decided something. A story in which things happened around you scores as an observation, however dramatic the events were.

Numbers you cannot defend. Any figure you say invites a follow-up. "About a quarter" that you can explain beats "27%" that you cannot.

For the questions that surround the behavioural ones, see common job interview questions. The weakness question needs a different shape from STAR, and the weaknesses guide covers it. If you are applying to the NHS, the NHS interview questions guide covers values-based questions, which use examples in the same way.

Sources

Frequently Asked Questions

What does STAR stand for in an interview?

Situation, Task, Action, Result. The National Careers Service defines them as the situation you had to deal with, the task you were given to do, the action you took, and what happened as a result of your action and what you learned from the experience.

Is the STAR method used in UK Civil Service interviews?

It is named in the guidance. Behaviour questions are part of Success Profiles, the recruitment framework used across the Civil Service, and the GOV.UK guide to Civil Service behaviours tells candidates to consider using the STAR method in their own examples. It also says there is no expectation that you demonstrate every part of each example to be successful.

How long should a STAR answer be?

Ninety seconds to two minutes spoken, which is roughly 200 to 250 words. Situation and Task together should take 20 to 30 seconds. GOV.UK's guide to competencies puts it plainly: keep the situation and task parts brief, and concentrate on the action and the result.

Should I say the words "situation" and "task" out loud in an interview?

No. Nobody scores the acronym, and announcing the sections makes a rehearsed answer sound more rehearsed. The National Careers Service asks you to get your points across in a conversational way so as not to appear too rehearsed. Use STAR as a checklist before the interview, not a script during it. On a written application form, labelled sections are fine.

Can I use the same STAR story for different questions?

Yes, if you change which part you emphasise and which result you finish on. A story about rescuing a late project can answer questions about pressure, prioritisation and influencing. Six to eight stories cover most competency areas without you repeating yourself.

What if I have no work example for a STAR question?

Use a different part of your life. The National Careers Service says to use examples that work for you, and that these could be from work, home or volunteering. Say briefly where the example comes from and then answer it exactly as you would a work example.

What is the difference between behavioural and situational interview questions?

Behavioural questions ask what you did ("Tell me about a time when..."). Situational questions ask what you would do ("What would you do if..."). STAR fits behavioural questions directly. For a situational question, describe the steps you would take and, if you have one, finish with a real example of having done something similar.

How do I answer a STAR question about failure?

Pick a real failure that was genuinely yours and was not catastrophic. Keep the situation short, own the decision that went wrong without blaming anyone else, and spend most of the answer on what you changed afterwards. In a failure answer, the result is the change you made and what it prevented next time.