Civil service interviews are unusual in a way that works in your favour: they are scored against a published framework. Under Success Profiles — still the standard across departments in 2026 — panels assess you against the behaviours named in the job advert (usually three to five of them), often alongside strengths questions, and score each element separately. The marking scheme is public before you walk in. Preparation is therefore an evidence exercise, not a charm exercise.
This guide is a working question bank for that format: motivation, behaviour and strengths questions panels actually ask, five of them with full model answers and marking guidance against four criteria. Read the answer, then the marking, then build your own version from the same skeleton — with your evidence, at your grade.
It is written for people taking the interview seriously because the move matters: stepping in from the private sector, moving departments, or going for promotion in the one you know. The panel discipline is the same in all three cases — what scores is calibrated evidence at the level you are applying for, delivered in a shape assessors can mark.
Practise these questions out loud with a live AI interviewer — free. Start with Try Me
How the marking guidance works
Each model answer below is marked against the four criteria a live aurate session scores:
See how a full session is scored
aurate is a practice tool. Marking guidance describes what strong practice answers show — it isn't an employability assessment.
Why it's asked: A motivation check with a values edge: panels are filtering for people who want this work, not just a stable employer. Generic public-sector praise scores poorly; a specific, honest account of why now and why here scores well.
For the past six years I've built pricing systems for a retail bank — work I'm proud of, but the outcomes stop at the margin line. The projects that stayed with me were the ones with public consequence: I spent eight months seconded to a cross-industry fraud taskforce alongside two government analysts, and the difference in what the work was for was hard to un-see.
I'm applying now for two reasons. First, the role: it needs someone who can turn messy data into decisions that stand up to scrutiny, which is what I've done through three regulatory cycles. Second, the setting: I want the next decade of my work judged on public value, and I'd rather bring my private-sector habits — pace, plain-English analysis, decisions on evidence — somewhere they compound. I've read the department's outcome delivery plan, and the emphasis on evidence over instinct describes the environment I already work best in.
Marking guide
Why it's asked: This is Delivering at Pace, one of the nine Success Profiles behaviours. Panels want evidence that your speed comes from how you organise work — not from heroics, corner-cutting or unpaid weekends. Strong answers show a system change with the quality check built in.
Our team inherited a backlog of 340 unprocessed customer remediation cases with a regulator deadline nine weeks out. As the analyst who knew the case system best, I was asked to get us to zero without the error rate climbing.
I did three things. I timed ten cases end-to-end and found half the effort was re-keying between two systems, so I built a template that pre-filled the repeated fields — the team was using it by day three. I split the backlog into simple and complex queues, so our two most experienced handlers only touched genuinely hard cases. And I set a visible daily count — not as pressure, but so slippage showed up in days rather than weeks.
We cleared the backlog with eight days to spare. Quality checks on a sample of 60 cases found two minor errors, both corrected before submission.
Marking guide
Why it's asked: Making Effective Decisions is among the most commonly tested behaviours at every grade. Panels listen for options genuinely weighed, evidence gathered before deciding, and a decision trail someone else could audit afterwards.
Midway through a systems migration, our supplier told us a data-cleansing stage would slip by three weeks. I had to decide whether to hold the go-live date by cutting the cleansing scope, or move the date and absorb the cost of extending the old contract.
I wrote a one-page options note that afternoon. For each option I set out the evidence: the cleansing stage covered records used daily by two downstream teams, and a sample I ran that morning suggested around one record in six would fail validation without it. Cutting the stage moved risk onto colleagues who hadn't agreed to carry it; moving the date cost a known, bounded amount. I recommended moving go-live by a fortnight, took both options to the project board fully costed, and recorded the decision and rationale in the log.
The board accepted the recommendation. Go-live landed on the revised date, and the downstream teams reported no validation failures in the first month.
Marking guide
Reading answers is the easy half
Panels score what you say out loud, under follow-ups you did not script. A live aurate session runs a civil-service-style interview against your actual CV and target role — and marks it on the same four criteria as the guidance above. Two free sessions to start. No credit card.
Try it freeWhy it's asked: Communicating and Influencing in its most common interview form. The trap is describing simplification as dumbing down; panels want evidence you reorganised the material around what the audience needed to decide.
Our analysis of regional service demand ran to about 40 pages, and the director group who needed to act on it had 15 minutes on their agenda. As lead analyst, my job was to get a funding reallocation agreed — not to present everything we'd done.
I rebuilt the material around the decision: a two-page note with one chart per region, each annotated with the single number that mattered, and every technical caveat moved to an annex with a plain-English one-liner left in the main text. Before the meeting I walked the two most sceptical directors through the draft one-to-one and adjusted where they pushed back — one asked for a comparison year, which strengthened the case.
In the meeting, the note held. The reallocation was agreed inside the slot, and the chair asked us to use the same format for the next planning cycle.
Marking guide
Why it's asked: Working Together — panels listen for genuine interdependence, not politeness. Strong answers show you built a working relationship across a boundary (another team, department or organisation), handled a point of friction honestly, and can name what the other side needed from you.
Why it's asked: Changing and Improving. The differentiator is who else adopted the change and what happened after you stopped pushing it: an improvement only you used, or that decayed within a month, is a weaker answer than a smaller change that stuck. Name the before-state, the after-state and one number that moved.
Why it's asked: Usually mapped to Seeing the Big Picture or Managing a Quality Service. Panels want the reasoning behind the trade-off — what you protected, what you consciously let slip, and how you told the losing party. Answers that claim everything was delivered anyway avoid the question and score accordingly.
Why it's asked: A values question testing whether you understand the Civil Service Code as working behaviour rather than a slogan — and it sets up the follow-up every panel has ready: what would you do if you personally disagreed with a policy?
For me it means three working habits, not an abstract value.
First, advice built on evidence rather than preference: if the analysis supports a conclusion I personally dislike, that conclusion goes in the advice, clearly argued, and my preference stays out of it. Second, serving the government of the day with equal professionalism whatever its politics — ministers are entitled to advisers whose effort doesn't fluctuate with private opinion. Third, knowing the line between challenge and resistance: before a decision I'd expect to argue the evidence candidly, put risks on record and test weak assumptions; after the decision, my job is to deliver it well — or, if something genuinely crossed a legal or propriety line, to raise it through the proper channels rather than around them.
I'd add that impartiality is protective, too. It's what lets officials give honest advice without career consequences — and that only holds if we keep the standard ourselves.
Marking guide
Why it's asked: A strengths question. Unlike behaviours, these are scored on authenticity and energy: assessors watch how you answer as much as what you say, and rehearsed-sounding responses mark down. Answer in 30–60 seconds, honestly, with one brief example — do not force it into STAR.
Why it's asked: Developing Self and Others, tested through your own development. Panels listen for what you actually changed — a named adjustment that stuck — rather than gracious acceptance. The strongest answers include the moment the feedback stung, because that is what makes the change credible.
Why it's asked: A recovery question that panels map to Delivering at Pace or Managing a Quality Service depending on your answer. They want early detection (how you knew), honest escalation (who you told, and when) and a re-plan — not a rescue built on overtime.
Why it's asked: Not scored against a behaviour, but panels remember it. Grade-appropriate curiosity lands best: ask about the work — the team’s biggest delivery challenge this year, what the first three months need to achieve — rather than working patterns you can ask about at offer stage.
The job advert lists them — typically three to five behaviours per role, chosen by the vacancy manager from the nine in the Success Profiles framework. Prepare one strong, complete example for each listed behaviour, plus a spare you can adapt if a question comes at an angle you did not expect.
Panels score each assessed element separately, in most departments on a numeric scale (commonly 1–7), then moderate across the panel and rank candidates in merit order. Your invitation pack usually states exactly what is being assessed — read it as the marking scheme it is.
Behaviour questions ask for evidence from your past and reward structured, complete examples — this is where STAR belongs. Strengths questions ask what energises you and are scored partly on authenticity and natural enthusiasm, so a short, honest answer beats a rehearsed one. Panels often mix both in a single interview.
Yes — assessors are trained to find Situation, Task, Action and Result in your answers, so giving them that shape makes your evidence easy to score. Keep the Action section dominant and finish with a result you can quantify. Do not force STAR onto strengths questions, which reward spontaneity.
For behaviour questions, around two minutes spoken is a workable target — long enough for a complete STAR example, short enough to hold the panel. Strengths answers should be 30–60 seconds. If an answer is heading past three minutes, the Situation section is almost always the culprit.
Many panels allow brief prompt notes, particularly for video interviews — but check your invitation, because practice varies by department. Use single-line prompts at most: reading answers aloud flattens your fluency, and assessors notice.
Two free sessions. No credit card.