Interview questions

Competency and behavioural questions

"Tell me about a time when...": how interviewers score your real examples, and how to tell them clearly using STAR.

From the interviewer's side

What the interviewer is looking for

  • These questions rest on a simple idea: what you have actually done is the best guide to what you will do. Interviewers ask for real examples from your past because they predict how you will perform far better than promises or hypothetical answers.
  • Each question is tied to one competency from the person specification, such as teamwork or problem solving. The panel has an agreed list of what a good answer contains, notes the evidence you give and scores it against that list, taking the level of the job into account.
  • They listen for your personal part. A team success tells them little unless they can hear what you did, so answers full of "we" are hard to credit and score lower than answers that say "I".
  • Most marks are earned in the action: the choices you made, how you made them and why. The result and what you learned come next, and a story with no ending is very hard to score.
  • Follow-up questions are planned in advance to test whether a story is real. Interviewers probe for detail, such as what you said, what happened next or what you would change, and genuine experience holds up under that probing while a rehearsed story tends to wobble.

For candidates

How to prepare

  • Read the job description and person specification and list every competency they name. Expect a question on most of them, and on the ones mentioned more than once in particular.
  • Build a bank of six to eight real stories from work, study, volunteering or home life. One good story can often answer two or three different questions, so you do not need one for every possible question.
  • Shape each story with STAR: a sentence or two on the situation and your task, most of your time on the actions you took, then the result. Add a line on what you learned, because many panels give extra credit for reflection.
  • Say "I" for what you did. Be generous about the team, but make your own part unmistakable, because the panel can only score what they hear.
  • Practise out loud until you can tell each story in about two minutes without a script. If you have no example that fits exactly, say so, then give the closest real one and explain why it transfers.

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

What the interviewer is really asking

Nearly every job depends on other people, so the interviewer wants proof that you make a team better, not just that you were in one. They are listening for what you personally did to help the group succeed: sharing information, picking up extra work, supporting a colleague or keeping everyone pulling in the same direction. It is also an early look at how you would behave in their team.

What a strong answer shows

  • A clear shared goal, and your own specific part in reaching it.
  • Actions that helped other people do their jobs, not only your own tasks done well.
  • A result the team achieved together, with a sense of what changed because of you.
  • Awareness of how the team worked, for example what made communication or handovers go well.

What loses marks

  • Saying "we" throughout, so the panel cannot tell what you did.
  • A story where you were the hero and everyone else was in the way.
  • General claims such as "I am a real team player" with no example behind them.
  • An example with no result, or one that stops before the team finished the job.

How to answer

  1. Pick an example where the team faced a real challenge, because a smooth week gives you little to talk about.
  2. Set the scene in a sentence or two: the team, the goal and what was at stake.
  3. Spend most of your answer on what you did: the idea you suggested, the colleague you helped, the problem you spotted.
  4. Finish with the result and one thing you learned about making teams work.

An example answer

Our distribution centre does an annual stock count, and our team of eight had one weekend to count the whole chilled section before the auditors arrived on Monday. My task was to count two aisles, but by Saturday lunchtime it was clear we would not finish, because two people were off sick. I finished my aisles early and offered to take on a third. I noticed that people were counting the same bays twice, so I suggested we mark each bay with a coloured sticker once it was done, and I fetched the stickers and showed everyone. I also partnered with a newer colleague who was nervous about the scanner, calling out the counts while she entered them, which sped her up a lot. We finished by six on Sunday and the audit found no errors in our section. I learned that how a team works together matters more than how long it works.

Tell me about a time you dealt with conflict at work.

What the interviewer is really asking

Disagreements happen in every workplace, so the interviewer is not looking for someone who has never had one. They want to see how you behave when you do: whether you stay calm, deal with the issue rather than the person, try to understand the other side and reach a solution that works. They are also checking that you tackle problems rather than avoiding them or letting them grow.

What a strong answer shows

  • That you raised the problem directly and privately, rather than complaining to other people.
  • A genuine effort to understand what the other person needed or was worried about.
  • A practical solution, often a compromise, that kept both the work and the relationship on track.
  • A working relationship that was as good or better afterwards, and what you learned about handling disagreement.

What loses marks

  • Blaming the other person or describing them unkindly, even if they were in the wrong.
  • A story where you simply gave in, or simply won, with no attempt to understand the other side.
  • Going straight to a manager without trying to sort it out yourself first, when it was safe to do so.
  • Choosing a clash so serious or so personal that it raises questions about your judgement.

How to answer

  1. Choose a disagreement about the work, such as priorities, timings or methods, not a personal feud.
  2. Describe the other person fairly and explain briefly what each of you wanted.
  3. Spend most of the answer on what you did: how you raised it, what you asked, how you listened and what you proposed.
  4. End with the outcome for the work and for the relationship, and what you would do the same way again.

An example answer

As a floor supervisor in a busy restaurant, I kept clashing with the head chef on Fridays. My hosts seated every table the moment it came free, so the kitchen was swamped with orders at once and food went out late. I wanted to fix it, not keep arguing. I asked him for ten minutes before Saturday service, away from the kitchen. I began by asking what the worst part of Friday was for him, and I listened. He explained that orders arriving in waves meant dishes sat waiting under the lamps. I explained the pressure the queue at the door put on my hosts. We agreed that I would stagger seating across sections, and he would tell me when the kitchen was close to full. The next Friday, complaints about waiting stopped, and we now plan large bookings together each week. It showed me that a calm, private conversation fixes more than a row during service.

Describe a time you worked under pressure or to a tight deadline.

What the interviewer is really asking

Every job has busy spells, and the interviewer wants to know how you cope when time is short and the stakes are real. They are listening for how you plan and prioritise, whether you tell people early when something is at risk and whether you keep your standards up rather than cutting corners. Staying calm matters, but so does knowing when to ask for help.

What a strong answer shows

  • A clear deadline, and what would have happened if it had been missed.
  • How you decided what mattered most, and what you set aside or asked others to take on.
  • Early, honest communication with the people depending on you.
  • A result delivered on time without lowering quality or safety.

What loses marks

  • A crisis you caused yourself through poor planning, with no sign you learned from it.
  • Claiming you thrive on pressure without showing how you actually handle it.
  • Heroics, such as working through the night, as your only strategy.
  • Cutting corners on safety or quality to hit the date.

How to answer

  1. Pick a real deadline with consequences, ideally one where the pressure came from outside your control.
  2. Explain the deadline and what was at stake in a sentence or two.
  3. Walk through your actions in order: how you planned, prioritised, communicated and kept the quality up.
  4. Give the result, then say what you now do differently to prevent or prepare for that kind of pressure.

An example answer

I was lead electrician on a coffee shop fit-out when the client brought the opening forward by a week. It was my job to finish the wiring, testing and certification in five working days, and the inspection date could not move. That afternoon I sat down with the site manager and split the job into what had to be done before the plasterers returned and what could wait. I asked for a second electrician for three days and gave him the lighting, while I focused on the distribution board and the kitchen circuits, which carried the most risk. I kept a list on the wall so everyone could see what was left, and on day three I told the client the outside signage would be a week late, so there were no surprises. We passed inspection first time and the shop opened on the new date. I now build a buffer into every programme for exactly this.

Tell me about a mistake you made at work and what you learned from it.

What the interviewer is really asking

Everyone makes mistakes, and the interviewer knows it. What they want to see is honesty, ownership and learning: whether you own up quickly, put things right and change how you work so it does not happen again. Someone who cannot name a real mistake is either not being open or not reflecting, and both are a risk.

What a strong answer shows

  • A real mistake, described plainly, with no attempt to shift the blame.
  • Quick action: telling the right people and putting things right.
  • A lasting change to how you work, such as a check or habit you still use.
  • Calm reflection that shows you took it seriously without being knocked off course.

What loses marks

  • Saying you cannot think of one, or offering a "mistake" that is really a boast, such as caring too much.
  • Blaming a colleague, the system or a lack of training.
  • A mistake so serious, or so close to the heart of the job, that the story raises more concern than it settles.
  • Stopping at the apology, with nothing about what you changed.

How to answer

  1. Choose a genuine mistake with a contained impact, ideally from long enough ago that you can show what has changed since.
  2. State what you did wrong in one or two plain sentences, owning it with "I".
  3. Explain how you put it right: who you told, how quickly and what you did to limit the damage.
  4. Finish with what you changed so it would not happen again, and any evidence that the change has worked.

An example answer

When I was a supervisor in a garden centre, it was my job to set up a spring offer on the tills: buy two bags of compost, get one free. I keyed it in as buy one, get one free, and I did not test it before we opened. By late morning a colleague noticed the takings looked low. I checked the system, found my error and corrected it straight away. I told the store manager myself before anyone else could, and worked out it had cost about £180. I suggested we treat it as a goodwill gesture rather than chase customers, and she agreed. After that I wrote a simple checklist for setting up promotions, including a test sale before opening and a second person to check the details, and it is now used across the store. We have not had a pricing error since. It taught me to slow down on small jobs that feel routine.

Give me an example of a problem you solved.

What the interviewer is really asking

The interviewer wants to see how you think, not only that things turned out well. They are looking for the steps a good problem solver takes: noticing the problem, finding out what is really causing it, weighing up the options and acting on the evidence. It also shows whether you take the initiative or wait for someone else to fix things.

What a strong answer shows

  • A problem that mattered to customers, colleagues or the organisation.
  • How you found the real cause, using facts rather than guesswork.
  • The options you considered, and why you chose the one you did.
  • A measurable or visible improvement, and whether it lasted.

What loses marks

  • Jumping straight to the solution with no sign of how you got there.
  • A problem so small it shows little, or one that someone else actually solved.
  • Fixing the symptom without asking why it kept happening.
  • No result, or a result you cannot explain.

How to answer

  1. Choose a problem where your thinking made the difference, even if the problem itself was modest.
  2. Describe the problem and why it mattered in a sentence or two.
  3. Explain step by step how you investigated it, what options you considered and what you decided.
  4. Give the result, with a figure if you have one, and what you learned about solving problems.

An example answer

I work as an administrator in an NHS physiotherapy department, and last year our clinics were losing several appointments a day to patients who did not turn up. My manager asked me to look into it. Rather than guess, I went through two months of missed appointments and phoned a sample of the patients. A pattern came out quickly: most had been booked more than six weeks ahead, and many said they had forgotten or that the letter had gone to an old address. I suggested two changes: a text reminder three days before each appointment, and checking the address and mobile number at every booking. I tested both in one clinic for a month first, so we could compare. Missed appointments in that clinic fell by more than half, and the department now does both as standard. It showed me the value of finding the real cause before choosing a fix.

Tell me about a time you led or influenced others.

What the interviewer is really asking

Leadership is not only for managers. The interviewer wants to know whether you can bring people with you: setting a direction, persuading colleagues to try something new or getting a group to agree, often without any formal authority. How you do it matters as much as the outcome, because people who lead by pressure tend to leave unhappy colleagues behind them.

What a strong answer shows

  • A clear aim, and why it needed other people to change what they did.
  • How you persuaded: listening to concerns, using evidence and leading by example.
  • Respect for the people involved, including those who disagreed at first.
  • A result that lasted after you stepped back.

What loses marks

  • Confusing leadership with telling people what to do.
  • Saying you have never led anything because you have never been a manager.
  • Taking all the credit for what the group achieved.
  • Winning the argument but leaving colleagues resentful.

How to answer

  1. Look beyond job titles: training a new starter, running a project, changing a routine or organising an event all count.
  2. Set out what you wanted to change and why people were not already doing it.
  3. Spend most of your answer on how you brought people with you: who you spoke to, what objections you heard and how you answered them.
  4. Give the result and what you learned about leading people who did not have to follow you.

An example answer

As a care assistant with no management role, I noticed that residents living with dementia were often distressed at teatime. The dining room was loud, and staff were rushing to serve everyone at once. I wanted to try a calmer approach, but I needed colleagues on board. First I asked the senior on shift if I could trial a change on my own table: music turned down, smaller portions and one of us sitting with residents while they ate. I kept a simple note of how each resident ate and settled for two weeks. Then I shared my notes at a team meeting and asked the colleagues who were unsure what worried them. The main concern was time, so I offered to help rework the rota. Within a month the whole home had adopted it, and residents were eating more and settling better. I learned that evidence and listening persuade people more than enthusiasm does.