November 12, 2026

How to Answer “Tell me about a time you….” in a UK Interview using the STAR Method

If you are preparing for a job interview in the UK, you have probably heard of the STAR method. It is a simple structure for telling a story about your work. STAR stands for:

  • Situation
  • Task
  • Action
  • Result

The structure sounds simple. But after working with many clients, I have noticed there are some parts that people struggle with or miss out completely.

In this post, I will go through each part of STAR: what usually goes in it, what can go wrong, what to do instead, and some useful phrases you can use.

Prefer to watch? You can find the full video here: How to Answer “Tell me about a time you….” in UK Interviews Using the STAR Method

When should you use STAR?

There are three main times to use STAR in a job interview.

1. Competency-based questions

These questions ask how you have dealt with real situations at work. They often start like this:

  • “Tell me about a time you… solved a problem / worked as part of a team / showed your organisation skills.”
  • “Can you give me an example of when you…?”

2. Questions about mistakes or things that went wrong

For example:

  • “Tell me about a time you made a mistake.”
  • “Describe a project that didn’t go as planned.”

3. Any question where a specific example would make your answer stronger

This is true for many interview questions, especially in the UK. If the interviewer asks, “How do you work in a team?”, you could say: “I work really well in a team. I’m a good listener, and I collaborate well.”

But a specific example of a time you worked well in a team is much stronger.

So keep STAR in mind for the whole interview. It helps you explain things clearly and concisely. And a real story is more engaging and memorable than a general statement. And being memorable is really important in an interview.

One note: we are not telling long, detailed stories. Try to keep them as concise as possible.

Our example question

To go through each part, let’s use this question:

“Tell me about a time you solved a difficult technical problem.”

Before you start: Choose ONE Specific Example

The first problem I see happens before people even get to the S of STAR. They talk generally about a job, instead of about one specific event in that job.

❌ Too general:

“In my last job, I worked on lots of automation projects, and I often solved technical problems.”

This tells the interviewer what your role involved — but they can see that on your CV. It doesn’t show them how you work.

✅ Better:

“A good example of that was when our packaging line kept stopping six weeks before a really important deadline.”

Now it is one event, and the interviewer wants to know what happens next.

Preparation tip: Before your interview, think of lots of different examples that show the skills needed for the role, and practise talking through them. There is nothing worse than trying to think of an example in the interview and your mind goes blank.

S – Situation: Set the Scene

Give the background information that is important for this story, so the listener can imagine the context. Remember, the interviewer wasn’t there. They don’t know where you worked, what kind of company it was or what the culture was like.

In two or three sentences, explain:

  • where you were working and the type of company
  • your role
  • the main problem
  • any details that will be important later

Example:

“Two years ago, I was a mechanical engineer at a food packaging factory in Manchester. We’d just installed a new automated line for one of our biggest clients, and we had a really large order to deliver within six weeks. But the line kept stopping, and we were losing about six hours of production a week.”

Notice the client and the six-week deadline. These details are important because they will come back in the result.

Useful phrases:

  • “A good example of that was when…”
  • “At the time, I was working as… at…”
  • “The main problem was that…”

T – Task: Explain Your Responsibility

What was your responsibility, and what did you need to achieve? Keep this short: one or two sentences is enough.

If something made your task more difficult (for example, a tight deadline or a team member being off sick), mention it here.

Example:

“We couldn’t shut the line down completely because of the deadline, so my job was to find the cause as quickly as possible.”

Useful phrases:

  • “My job was to…”
  • “I was responsible for…”
  • “What made it more difficult was that…”

A – Action: What YOU did, and WHY

This is the main part of your story. There are two common problems here.

Problem 1: saying “we” all the time

Many people say “we” because they want to sound modest, or to show they work well in a team. That is a good quality — but the interviewer isn’t hiring your team. They want to know what you did. Even if the question is about teamwork, they want to know what you did within the team.

❌ “We looked at the data and we fixed the sensor.”

✅ “I analysed the data and I found the fault. I then worked with the maintenance team to fix it.”

You can still mention your team — they were probably very involved. Just make your own part clear.

Problem 2: saying what you did, but not why

Giving the reason shows how you think, and that is what interviewers want to see. So justify your actions. (Justify means giving a good reason for something.)

❌ “I analysed the fault data.”

✅ “I analysed the fault data first because I wanted to find the cause before we spent lots of money on new parts.”

Useful phrases:

  • “I decided to… because…”
  • “First, I… so that…”
  • “I then worked with… to…”

R – Result: The Outcome and the Impact

The result is probably the most important part of your story — but many people rush it or forget it completely. They finish with: “And then we fixed it.”

Instead:

  1. Explain the outcome and how it affected the business. Use numbers if you can. If you don’t have exact figures, use words like around or roughly.
  2. Mention the impact on the team or the client — whichever is most relevant to the question.

Example:

“As a result, stoppages fell from six hours a week to less than one. We delivered the order on time, and the client renewed their contract.”

Add what you learned

One thing I ask my clients to add to the result is what they learned, or what they would do differently in the future.

“What I learned from this was to speak to the operators early. Since then, I’ve always done that before starting an investigation.”

This is especially important when you are describing something negative, like a mistake. Interviewers know that everyone makes mistakes, so you don’t need to hide it or make it look better than it was. But they want to see that you took responsibility, learned from it and changed your behaviour.

“I once approved a design change without checking with production, and it caused a two-day delay. Since then, I’ve always reviewed changes with the production team first.”

Useful phrases:

  • “As a result, …”
  • “This reduced / increased … by around …”
  • “What I learned from this was…”
  • “Since then, I’ve always…”
  • “If I did it again, I would…”

Here’s an Example…

Here is the full answer to “Tell me about a time you solved a difficult technical problem”:

“That’s a good question — let me think. Two years ago, I was a mechanical engineer at a food packaging company in Manchester. We’d just installed a new automated line for one of our biggest clients, and we had a large order to deliver to them in six weeks. The main problem was that the line kept stopping, and we were losing about six hours of production time a week.

We couldn’t shut the line down because of the deadline, so my job was to find the root cause as quickly as possible.

To do this, I analysed the fault data first, because I wanted to find the cause before we spent a lot of money on new parts. Interestingly, the data showed that most of the stops happened when we changed to a larger product size. So I spoke to the operators to find out what they were seeing, and that helped me discover that a sensor wasn’t in the correct position. I then worked with the maintenance team to fix it during planned maintenance time, so we didn’t lose any more production.

As a result, stoppages fell from six hours a week to less than one, and — importantly — we delivered the big order on time and the client renewed their contract, which was a big relief for everyone.

What I learned from this was to speak to the operators sooner. Since then, I’ve always done that before I start any investigation.”

Notice two things:

  • It is one specific event.
  • The deadline from the beginning comes back in the result. This ties the story together and shows the impact you had on the business — and the impact you could have on their business.

What to do next…

  1. Choose one example from your work experience.
  2. Write it out using the STAR structure, so you are sure you have all the details.
  3. Practise speaking about it using these points as a guide.

Don’t just memorise a script. You want to feel flexible when you tell the story, so it sounds natural in the interview.


Are you preparing for a job interview in the UK? In my one-to-one coaching, we build and practise your examples together, so you feel clear and confident on the day. Find out more about one-to-one coaching. I also have self-study courses coming in the new year: watch this space.

And if you prefer to learn by video, you can watch the full video on my YouTube channel.

READ MORE BLOG POSTS