plum
Answer checklist

One interview answer, built from level 1 to level 7

Start with the answer most people give, then add one thing at a time: a real story, your own steps, a number, what went wrong, and what you do differently now.

A panel can only score what you show it. Below, one answer to one question is built up from level 1 to level 7. At each level you'll see the full answer, why it scores where it does, and exactly what to add to go up one level.

The 7 levels are Plum's way to check and improve an answer step by step, not an official Civil Service scale. In each example, the bold part is what's new.

The question all the way through: “Tell me about a time you had to deliver results under pressure.” The example is made up to show the shape, so use your own.

How Civil Service answers are scored

Most Civil Service jobs test behaviours from Success Profiles, the framework that sets what each job looks for. You show a behaviour by telling the story of one real time you did it, usually in the STARR shape: Situation, Task, Action, Result, Reflection.

Behaviours are usually scored out of 7. The advert or candidate pack sets the pass mark, and 4 is common. The panel marks what you did, so the detail of your own actions is where the marks are.

Your example doesn't have to come from an office job. Success Profiles says it can come from work experience, volunteering or a hobby, as long as you did the thing yourself.

Level 1: you describe your job

A level 1 answer

Sounds like

“In my role I'm responsible for handling customer queries and complaints. I deal with a high volume of contacts every day and I make sure they're resolved within our targets.”

Do this instead

Pick one real time something needed fixing, and say what you did about it.

Why it scores 1: it describes your job, not something you did. There's no time, no pressure and no result, so it doesn't answer the question.

Level 2: you say you're good at your job

A level 2 answer

Sounds like

“In my role I'm responsible for handling customer queries and complaints. I'm a hard worker and a strong communicator, and I work well under pressure. I stay calm when it gets busy and I'm a real team player.”

Do this instead

Cut the claims about yourself. Tell one real time instead, and let what you did show it.

Why it scores 2: hardworking, calm and team player are claims. Everyone in the queue says them, and a claim can't be scored.

“You could be awful at your job, and this sentence would still be true.”

Civil Service staff who sift applications, on duty lines

Level 3: you tell a story, but it's “we”

To reach level 3: Tell one real time, not your whole job.

Say

Last [when], [the problem and who it affected]. [How it ended].

Like this

“Last year we had a backlog of complaints after a system change. Customers were waiting weeks for a reply. We set up a new system to track them, we all worked really hard, and we cleared it.”

Why it scores 3: it finally answers the question, with a time, a problem and an ending. But it's all “we”, so the panel can't see which part was you. This is where most people stall.

Level 4: you say each step you took

To reach level 4: Swap “we” for “I”. Say what you were asked to do and each step you took, in order.

Say

My manager asked me to [task]. I [first step], because [reason]. Then I [next step].

Like this

“Last year, after a system change, unanswered complaints built up and some customers had waited weeks for a reply. My manager asked me to get the backlog under control without letting new complaints slip.” “I checked the backlog and sorted it by how long each customer had waited. I called the 12 oldest cases first, because they were the most likely to escalate. Then I set up a daily list showing every open complaint and who owned it.” “Each morning I checked the list and moved anything over 5 days old to the top. In the end, the backlog was cleared.”

Why it scores 4: the panel can see what you were asked to do, each step you took and why. Four is often the pass mark, and where offers start.

The weak spot is the ending. “The backlog was cleared” can't be checked.

Level 5: you put a number on the result

To reach level 5: Put a number on the result.

Say

Within [time], [what you measured] went from [before] to [after].

Like this

… “Within two months, complaints fell from 30 a month to 8, and none of the 12 oldest customers took their complaint further.”

Why it scores 5: “from 30 a month to 8” shows how much difference you made, in one line. A number is what the panel remembers after a long day of interviews.

It still sounds too smooth. Real work rarely goes to plan, and the panel knows it.

Level 6: you say what went wrong and how you fixed it

To reach level 6: Add the moment it went wrong and how you fixed it, at the point it happened.

Say

In [when], [what went wrong], because [why]. I [what you did to fix it].

Like this

… “In week two the list broke, because two people were updating it at once and cases were getting lost. I split it by team, so each team updated only its own tab, and I checked the totals each afternoon.”

Why it scores 6: the problem makes the story believable, and the fix shows how you think when things change. Keep it to one sentence for the problem and one or two for the fix.

Level 7: you say what you learnt and what you do now

To reach level 7: End with what you learnt and what you do differently now.

Say

What I learnt is [lesson]. Now I [what you do differently], so [why it helps].

Like this

… “What I learnt is that a new tool needs testing before everyone relies on it. Now I test any new tracker with one team for a week before everyone uses it, so a problem like the one in week two shows up early.”

Why it scores 7: it ends with something you now do differently because of what happened. That shows you learn, and the panel can picture you doing it in their team.

“I learnt communication is important” would drop you back to level 2. The whole answer is under 200 words, well inside a 250-word limit.

The full level 7 answer

Here's the whole answer in one place, split into the 5 STARR parts. Most of the words are in the action, which is where the marks are.

STARR example · Delivering at Pace

Clearing a backlog of customer complaints

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

Last year, after a system change, unanswered complaints built up and some customers had waited weeks for a reply.

T

My manager asked me to get the backlog under control without letting new complaints slip.

A

I checked the backlog and sorted it by how long each customer had waited. I called the 12 oldest cases first, because they were the most likely to escalate. Then I set up a daily list showing every open complaint and who owned it. Each morning I moved anything over 5 days old to the top. In week two the list broke, because two people were updating it at once and cases were getting lost. I split it by team, so each team updated only its own tab, and I checked the totals each afternoon.

R

Within two months, complaints fell from 30 a month to 8, and none of the 12 oldest customers took their complaint further.

R

Reflection: What I learnt is that a new tool needs testing before everyone relies on it. Now I test any new tracker with one team for a week before everyone uses it, so a problem like the one in week two shows up early.

Check your answer

Read your answer out loud, then tick each line it passes. The first line you can't tick is the level you're at. Fix that line before you touch anything else.

Which level is my answer at?

7 to do

What to do next

  1. Start from your weakest answer

    Run the checklist on each answer you've written. Work on the one with the lowest level first.

  2. Spend your words on the steps

    Keep the situation and task to two or three sentences. Most of a 250-word answer should be what you did.

  3. Find your number

    If you don't have one, count something: cases, days, people, complaints. A rough count you can explain beats none.

  4. Keep it true

    Panels ask follow-up questions at interview, so every step and number has to be real and yours.

Plum matches you to live Civil Service jobs, shows which behaviours each one tests, and helps you write and practise your examples. You apply on Civil Service Jobs itself.

Common questions

Are the 7 levels the official Civil Service scoring scale?

No. They are Plum's checklist for improving an answer one step at a time. Civil Service behaviours are usually scored out of 7, and the advert or candidate pack sets the pass mark, often 4.

Why can't I just say I'm a good communicator?

Because the panel scores evidence, not claims. Anyone can say they are a good communicator. Tell one real time you did it, the steps you took and what changed.

Is it OK to say “we” in an interview answer?

Only for the setting, like who was in the team. For everything you did yourself, say “I”, so the panel can see which part was you.

What if my result doesn't have a number?

Count something you can stand behind: how many people, cases, days or complaints. If nothing can be counted, say what changed and how you know.

Should I mention something that went wrong?

Yes, if you fixed it. A problem you spotted and solved shows how you handle change, and it makes the story sound real.

What goes in the reflection?

One thing you learnt, said as something you now do differently. “Now I test new trackers with one team first” works. “I learnt teamwork is important” doesn't.

Practise your answers with Plum

See which behaviours each live job tests, and get help turning your experience into answers.

Open Plum