plum
Interview workbook

How do I answer behaviour questions with STAR?

Tell one real story: a short Situation and Task, a long Action that says what you did, a snag you handled, then the Result and what you learned. Spoken, 2 to 3 minutes.
Practise

A behaviour question is the “Tell me about a time when…” question. The panel wants one real moment from your past that shows a particular way of working. The STAR method is how you tell it: the Situation you were in, the Task you had, the Action you took, and the Result. STARR adds a second R for Reflection: what you learned, or what you'd do differently.

The part that gets scored is the Action. Spend most of your answer on what you did, and say “I”, not “we”. A good answer also includes a snag, something that went slightly wrong, and how you adapted. Spoken out loud, the whole thing should take 2 to 3 minutes.

This page is a workbook. You'll do it in three steps, one at a time: collect your stories (about 20 minutes), match them to the behaviours your interview tests (about 10 minutes), then write each one up in STARR (about 20 minutes per story). There are five worked answers from bank, HR and healthcare jobs to copy the shape from. Don't try to do it all at once. Do step 1 today, then write one answer at a time, starting with your first interview.

What a behaviour question is, and how it's scored

Civil Service jobs are assessed with Success Profiles, the framework every department uses for recruitment. It can test five things: behaviours, strengths, ability, experience and technical skills. Your job advert says which of these the job uses, and whether they're tested in the written application, at interview, or both.

Behaviours are nine named ways of working: Seeing the Big Picture, Changing and Improving, Making Effective Decisions, Leadership, Communicating and Influencing, Working Together, Developing Self and Others, Managing a Quality Service, and Delivering at Pace. An advert usually picks a handful of them. Each one is described differently for each grade, so the same behaviour asks for more at Senior Executive Officer (SEO) than at Administrative Officer (AO).

Your written application is often scored first, in a stage called the sift: someone reads it, scores it, and decides who gets an interview. At interview, a small panel asks one question per behaviour and scores each answer.

4 = pass
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7

Many departments score each answer 1 to 7, and 4 is the usual pass. Check your candidate pack.

The panel can only score what you tell them you did. A vague answer (“I'm good with people”) gives them nothing to score. A specific one, with steps, a problem you handled and a number at the end, does. That's what STARR is for.

Step 1: collect your stories

Give yourself about 20 minutes. Write one line for every moment from your working life you can remember. Don't worry about spelling, and don't worry yet about which behaviour it fits. Aim for 12 or more.

Messy is fine. It only has to make sense to you. For example: “bank, lady's money going missing, found it, card froze, rent”. Or “bank, 50 accounts in 3 weeks, people cancelled, done early”. Or “care, resident not eating, nurse busy, infection”. Each of those lines later became a full answer on this page.

Stories don't have to be big. Panels at most grades are looking for ordinary work done well: a customer helped properly, a deadline met when it got hard, a mistake put right. Volunteering, caring and study count too.

Stuck? Think of a time you…

8 to do

Step 2: match your stories to behaviours

Give yourself about 10 minutes. Open your job advert and find the behaviours it lists for the interview. Then go down your list of stories and write the number of your best story next to each behaviour.

Here are five behaviours that adverts test often, in plain words. If your advert lists others, read their description on GOV.UK and put it in one plain sentence for yourself the same way: Seeing the Big Picture is roughly “you understood how your work fitted the wider goal”, Leadership is “you took ownership and treated people fairly”, Working Together is “you helped others get the job done”, and Developing Self and Others is “you learned something, or helped someone else learn”.

The behaviours, in plain words

5 to do

One story can work for two behaviours. Just tell it from a different angle. The missing-money story below is Managing a Quality Service, but the same day also involved a quick decision with your manager, which could lead a Making Effective Decisions answer. If you have enough stories, give each behaviour its own one.

Step 3: write it up in STARR

Pick one story. Answer six questions in order, and that's your answer. Give yourself about 20 minutes per story.

Situation: where were you and what was happening? One or two sentences. Task: what did you need to do? One sentence. Action: what did you do, step by step? Say “I”. This is the longest part, because it's the part the panel scores.

Snag: what went slightly wrong, and how did you adapt? This sits inside the Action. Panels like it because it shows you thinking, not just following a plan. Result: what happened in the end? Use a number if you can. Reflection: what did you learn, or what would you do differently?

Situation, Task, Action, Snag, Result, Reflection

Tell me about a time when…

Say

At [where], [what was happening]. I needed to [your task]. First I [step one]. Then I [step two]. [The snag] happened, so I [how you adapted]. In the end, [the result, with a number]. I learned [one thing], and now I [what you do differently].

Like this

At the bank, a customer's money kept leaving her account. I needed to find out why and stop it. I went through 3 months of statements with her and followed our fraud process. Stopping the payments froze her card the day before her rent was due, so I got an emergency withdrawal approved. The payments stopped that day. I learned to warn customers before anything gets frozen.

Why it works: Action is the longest part because it's the part the panel scores. The snag shows you can adapt.

Five worked answers, one for each behaviour

Each answer below is written in full STARR. The snag is marked inside the Action so you can see where it goes. Read them for the shape, then write your own. These are example stories for this guide, not real people.

STARR example · Managing a Quality Service

From a bank job: the missing money

Situation + Task 20%Action 60%Result 20%
S

At the bank, a customer came in worried. Money kept leaving her account and she didn't know why.

T

I needed to find out what was going on and stop her losing any more.

A

I sat with her and went through her last 3 months of statements and found payments to an account she didn't recognise. I followed our fraud process: stopped the payments, raised a case, and wrote up everything so she didn't have to repeat her story. Hit a snag: stopping the payments froze her card, and her rent was due the next day. So I got my manager to approve an emergency cash withdrawal and ordered a new card the same day. I called her back 2 days later with an update.

R

The payments stopped that day and she got the money back. I also told my team lead what I'd spotted, so we checked similar accounts.

R

Reflection: I learned to warn customers before anything gets frozen, so they can plan for it. I do that every time now.

Why it works: the customer's real need was bigger than the fraud case. Spotting the rent problem and solving it the same day is exactly what Managing a Quality Service means. The update call 2 days later shows you kept her informed.

STARR example · Delivering at Pace

From a bank job: 50 accounts in 3 weeks

Situation + Task 20%Action 60%Result 20%
S

Our branch was asked to open 50 new business accounts in 3 weeks, on top of normal work.

T

I was responsible for my share of them, and each one needed ID and compliance checks.

A

I worked out it was about 4 a day and booked appointments straight away, so the diary was full from day one. I sent each customer a checklist of documents to bring, so no meeting was wasted. I tracked every account on a simple spreadsheet and checked it each morning. Hit a snag: in week 2, 5 customers cancelled and I was 6 accounts behind. I rang my waiting list to fill the gaps and asked a colleague to cover walk-ins for two afternoons, and was back on track by Friday.

R

All 50 were opened before the deadline, and none came back with errors at the quality check.

R

Reflection: Cancellations always happen, so next time I'd book a few extra slots from the start instead of catching up later.

Why it works: it shows planning (4 a day), removing blockers (the document checklist), tracking progress, and recovering from a setback without dropping quality. Saying none came back with errors answers the worry that fast means sloppy.

STARR example · Communicating and Influencing

From an HR job: the new absence policy

Situation + Task 20%Action 60%Result 20%
S

In HR, we brought in a new absence policy and a lot of staff were unhappy about it.

T

I had to explain it clearly and get everyone to sign up before the deadline.

A

I wrote a one-page summary in plain English instead of sending the full 12-page policy. I ran short drop-in sessions at different times so shift workers could come too. Hit a snag: only 4 people came to the first session. Night staff couldn't make it. So I switched to 10-minute huddles at shift change and went to them instead. When managers pushed back, I met them one to one, listened, and showed how it made their job easier. I collected the common questions and shared the answers with everyone.

R

90% of staff signed by the deadline and questions to HR dropped by half in the first month.

R

Reflection: I learned to ask people how they want to hear about changes before I plan, not after the first attempt flops.

Why it works: it shows choosing the right way to reach people (a one-page summary, huddles at shift change) and changing approach when the first one didn't land. Meeting managers one to one and listening is the influencing part.

STARR example · Making Effective Decisions

From healthcare: the quiet resident

Situation + Task 20%Action 60%Result 20%
S

On a shift, I noticed a resident who was usually chatty was quiet, wasn't eating and seemed confused.

T

I had to decide whether this was serious and what to do about it.

A

I checked her care plan and the notes from the last few days to see what was normal for her. I took her observations and wrote down exactly what I'd seen and when. Diagnosing wasn't my role, so I went straight to the nurse with the facts instead of waiting to see if she improved. Hit a snag: the nurse was dealing with an emergency on another floor. I didn't want to wait, so I went to the nurse in charge with my notes and stayed with the resident until someone came. I recorded my actions and told the next shift at handover.

R

The nurse arranged a GP visit that day and she was treated for an infection. She was back to herself within a week.

R

Reflection: Writing down exactly what I saw and when made it quick for the nurse to act. I do that for any change in a resident now.

Why it works: a good decision isn't always doing it yourself. Checking the facts, knowing the limit of your role, and getting it to the right person quickly is the decision. It also shows you recorded it.

STARR example · Changing and Improving

From a senior support worker role: the handover sheet

Situation + Task 20%Action 60%Result 20%
S

As a senior healthcare support worker, I noticed things were being missed at shift handover.

T

I wanted to make handovers quicker and more reliable.

A

I asked the team what was going wrong. Most said handovers were rushed and nothing was written down. I made a simple one-page handover sheet with the key things for each resident. I trialled it for 2 weeks on my shifts and asked for feedback each day. Hit a snag: after a week, night staff had stopped filling it in because it took too long. I asked them why, cut it to a tick-box version, and they started using it again. I shared the final version with my manager.

R

Handovers went from about 30 to 15 minutes, missed tasks dropped, and the sheet was used across the unit.

R

Reflection: I should have tested it with night staff from day one, not just my own shifts. Now I try changes with everyone it affects.

Why it works: it starts by asking the people affected, tests the change before rolling it out, and changes it again when it isn't used. The result shows the improvement spread beyond your own shifts.

Check it, then expect the follow-up

Before you practise it

5 to do

After your answer, the panel will often ask a follow-up question: “What would you have done if your manager had said no?” or “How did you know it had worked?” This isn't a trap. It's them checking the story is yours. If you lived it, you'll know the answer, so take a breath and tell them.

If you can't remember a detail, say so honestly and give what you do know. Making up a number to fill a gap is riskier than saying “I don't remember the exact figure, but it was roughly half”.

What to do next

Tonight: do step 1. Write 12 lines, messy, in about 20 minutes. Then do step 2 and put a story number next to each behaviour in your advert.

This week: write up one story a day in STARR, starting with the behaviour you feel least sure about. Check each one against the list above.

Before the interview: say each answer out loud at least twice. Reading it in your head is not the same as saying it. Plum's AI interview panel asks the behaviour question, asks a follow-up like a real panel, and tells you how your answer landed.

What's the difference between STAR and STARR?

STAR is Situation, Task, Action, Result. STARR adds a second R for Reflection: what you learned or what you'd do differently. Ending on a short reflection shows you think about your own work, and it gives the panel a clean end to your answer.

How long should a STAR answer be in a Civil Service interview?

Spoken, about 2 to 3 minutes. Keep the Situation and Task to two or three sentences between them, spend most of the time on the Action, and finish with a short Result and Reflection. Panels differ, so watch whether they let you run or stop you with follow-ups.

Can I say “we” in my answer?

Say “I” for the things you did. The panel scores your actions, so if everything is “we”, they can't tell what was yours. It's fine to mention the team for context, then say what you did within it.

What if I don't have a number for the result?

Use one if you can: time saved, cases cleared, people reached. If you really don't have one, describe the change clearly instead (“she got her money back and kept banking with us”). Don't invent a figure you couldn't explain if asked.

Can I use examples from outside work?

Yes. Volunteering, caring, study or a community role can show the same behaviours. Make it just as specific as a work example, with steps, a snag and a result.

How many STAR examples do I need?

One for each behaviour your advert lists for the interview, plus one spare. One story can cover two behaviours if you tell it from a different angle, but having a separate story for each is easier under pressure.

What score do I need to pass?

Many departments score each answer from 1 to 7, and 4 is the usual pass mark. Some use a different scale, so check your candidate pack, which usually explains how scoring works for that job.

Say your STARR answer out loud

A live AI panel on Plum asks the question and tells you how it landed.

Practise now