What Is PACE Interviewing? The Complete UK Guide to Getting It Right
You’ve got the interview. Great. You’ve researched the organisation, ironed your shirt, and rehearsed answers to “tell me about yourself” in the mirror. And then you read the words “competency-based interview” in the confirmation email — and your stomach drops a little.
If the role is in UK policing, the NHS, the Civil Service, fire and rescue, or even a large corporate graduate scheme, there’s a decent chance you’re about to face something called a PACE interview. Most candidates have never heard of it. Fewer still understand how it actually works.
Here’s the honest truth: PACE isn’t something to be intimidated by. Once you understand the framework, it actually makes interview preparation easier — because you know exactly what’s expected of you before you walk through the door. There’s no guessing, no rambling, no hoping the interviewer likes you. You give structured evidence. They score it. Simple.
This guide covers everything you need — what PACE stands for, how it differs from STAR, what assessors are genuinely looking for, and how to structure answers that actually score well. There are real examples, practical tips, and a section for hiring managers too.
Table of Contents
What Is PACE Interviewing?
At its core, PACE interviewing is a structured, competency-based interview technique. It’s built around a four-part answer framework — Problem, Action, Conclusion, Evaluation — that guides candidates through giving real, specific, evidence-based answers rather than vague generalisations.
The underlying idea isn’t new. Behavioural interviewing has been around for decades, and it’s grounded in a fairly obvious principle: the best way to predict how someone will behave in a job is to look at how they’ve actually behaved before. Not how they think they’d handle a situation. Not what they would do if things went sideways. What they did — in a real, documented situation, with real consequences.
What makes PACE slightly different from other frameworks is its insistence on that final step: Evaluation. More on that shortly.
PACE is particularly common in UK public sector hiring because it ties neatly into published competency frameworks — the College of Policing’s Competency and Values Framework (CVF), the NHS Healthcare Leadership Model, the Civil Service Success Profiles. These organisations need hiring decisions that can be defended, audited, and scored consistently. PACE gives them the structure to do that.
What Does PACE Stand For?
Let’s break down each letter, because understanding what each component actually requires is where most candidates get an edge.
P — Problem
This is your scene-setter. Tell the assessor what situation you were in, what the challenge was, and what was at stake. Keep it tight — 30 to 45 seconds maximum. The Problem section exists to give context, not to eat up your answer time. Assessors don’t need your entire career history; they need enough to understand what you were up against.
A — Action
This is the heart of your answer, and it’s where most candidates either shine or fall flat. The Action section should explain specifically what you did — not your team, not your manager, not the wider organisation. You. What decisions did you make? What did you say, organise, challenge, or create? Walk the assessor through your thinking, not just the sequence of events. The “why” behind your actions is often more revealing than the actions themselves.
C — Conclusion
What happened as a result? This doesn’t need to be a dramatic success story — outcomes that were mixed or challenging can still demonstrate excellent competency — but it does need to be specific. “It went well” is not a Conclusion. “The team reduced error rates by 28% over the following month” is a Conclusion. If numbers aren’t available, describe the human impact. Who benefited? What changed for the organisation or the people involved?
E — Evaluation
This is the component that separates PACE from most other frameworks, and the one candidates most often skip. Evaluation asks: What did you actually learn from this experience? What would you do differently if you faced the same situation again? What did you take forward into your next role or your next challenge?
A shallow Evaluation sounds like: “I learned that communication is really important.” A strong one sounds like: “I realised I’d been assuming the team understood the project timeline when I’d never explicitly checked. Since then, I always build in a formal confirmation step at the start of any project — it’s saved me from that assumption twice.”
One is a platitude. The other is evidence of a person who reflects, grows, and applies what they’ve learned. That’s what assessors are hoping to hear.
How PACE Differs From STAR
If you’ve done any interview preparation in the UK, you’ve probably encountered STAR — Situation, Task, Action, Result. It’s everywhere, and for good reason. It works.
But PACE and STAR aren’t the same thing, and if you’re walking into a PACE interview with only STAR preparation, you might be leaving marks on the table.
| Component | STAR | PACE |
|---|---|---|
| Setting the scene | Situation + Task | Problem |
| What you did | Action | Action |
| What happened | Result | Conclusion |
| What you learned | Not required | Evaluation |
The table makes it clear. STAR stops at the result. PACE keeps going — and that Evaluation step is genuinely important in roles where continuous learning, professional development, and self-awareness are part of the job description.
Think about it from a policing or healthcare context. An organisation hiring a Police Constable or a Band 6 nurse doesn’t just want someone who got a good outcome once. They want someone who reflects on their practice, learns from experience, and develops over time. PACE is designed to surface exactly that.
So if you’re applying for a PACE-based role: don’t cut your answer short at the Conclusion. The Evaluation isn’t an optional extra. In many scoring frameworks, it’s a scored component in its own right.
Where Is PACE Interviewing Used in the UK?
PACE crops up in more places than most candidates realise.
UK Police Forces are probably the most well-known users of the framework. Many constabularies use PACE or a closely aligned method when selecting Police Constables, Detective Constables, and supervisory ranks. Answers are assessed against the College of Policing’s Competency and Values Framework.
The NHS uses structured behavioural interviews extensively, and PACE aligns naturally with the NHS Healthcare Leadership Model. If you’re applying for a clinical or management role and the person specification lists behaviours like “inspiring shared purpose” or “holding to account,” expect to be asked for PACE-style evidence.
Fire and Rescue Services across England and Wales use structured competency interviews for wholetime and on-call roles. The process varies by service, but the PACE approach — or something very close to it — is standard.
The Civil Service uses its Success Profiles framework, and the “Behaviour” and “Experience” elements of that framework are essentially PACE answers with different labelling. If you’ve ever applied for a Civil Service role and been asked to give examples of “working together” or “delivering at pace” (yes, that’s actually a Civil Service behaviour — confusingly), you’ve already done PACE-adjacent answering.
Corporate employers are catching on, too. Firms like KPMG, Deloitte, BT, and the BBC use structured behavioural interviews at assessment centres and final stage level, with assessors trained to probe for PACE-style evidence even if the framework isn’t named explicitly.
How PACE Interview Questions Are Structured
PACE questions are open behavioural prompts. They sound like this:
- “Tell me about a time when you had to manage a difficult situation…”
- “Give me an example of a time you influenced someone to change their approach…”
- “Describe a situation where things didn’t go to plan and how you responded…”
- “Can you think of an occasion when you had to make a difficult decision under pressure?”
Once you’ve given your initial answer, a well-trained assessor will follow up with structured probes to pull out any component you’ve missed or underdeveloped:
- “What was the specific challenge you were facing?” (digging into the Problem)
- “What exactly did you do personally?” (pressing for individual Action)
- “And what was the outcome?” (looking for Conclusion)
- “Looking back, what do you think you’d do differently?” (the Evaluation probe)
Here’s the thing: if you structure your answer well from the start, the probing is minimal. You’ve already covered everything. Assessors notice that. It signals confidence, preparation, and interview intelligence — all qualities that reflect well regardless of the specific competency being tested.
How to Answer PACE Interview Questions: Step-by-Step
Step 1: Pick the Right Example
This sounds obvious, but it’s where a lot of candidates go wrong. Don’t just grab the first situation that comes to mind. Before your interview, map out six to eight strong examples that cover the key competencies in the job description. Then, when a question comes up, you’re selecting from a curated shortlist — not improvising under pressure.
A strong example is recent (ideally within the last three to four years), specific, and shows genuine personal contribution. Vague or distant examples don’t score well, regardless of how well you structure them.
Step 2: Set the Scene Quickly
Your Problem section should be 30 to 45 seconds. Give the assessor the context they need — where you were working, what the situation was, what made it a challenge — then move on. Don’t get lost in backstory. The Problem exists to frame the Action, not to fill time.
Step 3: Give the Action Real Detail
This is where you spend most of your time, comfortably, 60 to 90 seconds. Be specific. Use “I” not “we.” Explain your decisions and your reasoning. If you had to choose between two approaches, say so, and explain why you chose the one you did. That kind of detail tells an assessor far more about your competency than a list of tasks.
A weak Action section sounds like: “I spoke to the team and we sorted it out.”
A strong one sounds like: “I set up a quick one-to-one with each team member to understand where the bottleneck actually was, rather than assuming. What I found was that two people were unclear on the sign-off process, not the work itself. So I drafted a one-page process guide and ran a fifteen-minute briefing, which removed the blockage entirely within two days.”
See the difference? Same basic story. Completely different level of evidence.
Step 4: Make the Conclusion Specific
Outcomes matter. Try to quantify wherever you can — percentages, timelines, numbers of people affected, money saved or recovered. If the outcome was qualitative, describe it in concrete human terms. “The feedback from the team was positive” is weak. “Three team members told me directly it was the clearest they’d felt about their responsibilities in over a year, and sickness absence dropped noticeably in the following quarter” is something an assessor can score.
Step 5: Don’t Phone In the Evaluation
Take it seriously. The Evaluation is your chance to show genuine self-awareness — a quality that’s genuinely hard to fake in an interview, which is exactly why assessors value it so highly.
Tell them what worked. Tell them what you’d change. Tell them what you carried forward into the next challenge. Keep it honest. If things didn’t go perfectly, that’s fine — what matters is that you know why, and you applied that knowledge.
PACE Interview Examples
Example 1: Leadership Under Pressure (NHS / Public Sector)
Question: “Tell me about a time you led a team through a difficult period.”
Problem: “I was working as a community healthcare supervisor when two of my eight team members went on long-term sick leave in the same month. This coincided with a spike in patient referrals over winter, which meant our remaining team had to absorb significantly more casework at exactly the wrong time.”
Action: “My first call was an honest team meeting — not to alarm people, but to acknowledge the situation openly and ask where they felt the pressure most. I’ve found that asking is almost always better than assuming. Based on that, I redistributed caseloads to reflect individual capacity rather than splitting evenly, which would’ve swamped two of the more junior members. I also took on a higher caseload myself so I could demonstrate I wasn’t just managing from a distance. In parallel, I put together a written business case for temporary agency cover and escalated it to my line manager with urgency — and got approval within a week.”
Conclusion: “We brought in one agency worker within ten days. Our KPI targets were held throughout the period, and patient waiting times stabilised. The pulse survey we ran six weeks later showed the team felt supported — something I was particularly glad to see given how stretched everyone had been.”
Evaluation: “Honestly, the thing I took from this was about communication. My instinct at the start was to manage quietly — deal with the problem without creating anxiety. But when I decided to be upfront with the team instead, things moved faster, and people rallied. I’ve used that approach consistently since. Transparency in a crisis is almost always better than protection.”
Example 2: Problem-Solving (Corporate / Finance)
Question: “Give me an example of a time you identified and solved a significant problem at work.”
Problem: “In a procurement analyst role, I started noticing invoice discrepancies from three of our regular suppliers — individually small amounts, but when I added them up across six months, they came to about £18,000. Each individual discrepancy sat below the threshold for formal audit review, so they’d been flagged but not investigated.”
Action: “I pulled the payment data myself and built a simple aggregation spreadsheet to see whether there was a pattern — and there was. Two of the three suppliers were applying pricing terms from a contract version that had been superseded after a renegotiation eighteen months earlier. I set up reconciliation meetings with each supplier, walked through the discrepancy evidence, and in both cases, they agreed to the overcharges immediately. I also proposed to the finance director that we add a cumulative threshold to our audit criteria — not just per-invoice, but rolling six-month totals — because the existing rules were essentially allowing pattern errors to slip through.”
Conclusion: “We recovered £14,500 in overpayments. The cumulative threshold proposal was adopted and is now part of our standard audit framework. We also updated the contract management process to include a mandatory bi-annual review.”
Evaluation: “The learning that stuck with me was that I’d actually spotted the pattern about a month before I acted on it. I kept waiting until I was more certain. That delay probably cost us around £3,000 in additional overpayments. Now, when I notice something that looks off, I investigate it promptly rather than waiting for certainty. A preliminary look costs nothing. Waiting can cost a lot.”
What Assessors Are Actually Looking For
Here’s something worth understanding clearly: PACE assessors aren’t judging whether they like you. They’re scoring specific evidence against specific criteria, usually on a numerical scale — often 1 to 5 per competency. Their job is to find the evidence, not to be impressed by your personality.
That changes how you should approach the interview. You’re not performing. You’re presenting evidence.
The qualities that score well are:
Specificity. “I always try to keep my team informed” scores nothing. A named situation, a specific action, and a measurable outcome do. If your answer could apply to any situation or any person, it’s too vague.
Personal ownership. “We managed to resolve it” is weak evidence. “I drafted the communication, I escalated the timeline concern, and I checked in personally with the two team members who seemed most uncertain” is strong evidence. Use “I” deliberately.
Proportionality. The scale and complexity of your example should match the level of the role. A Band 7 management position needs examples with broader organisational impact than an entry-level role. Assessors calibrate what “good” looks like against the seniority they’re hiring for.
Real reflection. An Evaluation that amounts to “it taught me the importance of teamwork” will be seen for what it is immediately. Real reflection is specific, honest, and shows application. It names the precise thing that changed about how you work.
Relevance. Every part of your answer should be earning its keep against the competency being assessed. If the question is about problem-solving, your Action section should be full of problem-solving decisions — not tangential context or impressive-sounding but irrelevant achievements.
Common Mistakes That Cost Candidates Marks
These come up again and again. Being aware of them before you walk in is half the battle.
Skipping the Evaluation. This is the single most common mistake. Candidates give a solid Problem, a decent Action, a clear Conclusion — and then they stop. “And that’s the end of my example.” No Evaluation, no score for that component. Don’t do it.
Going hypothetical. “What I would do in that situation is…” is not a PACE answer. Full stop. Assessors are listening for real events, past tense, with specific details. If you catch yourself answering hypothetically, stop, reframe, and find a real example.
Hiding behind “we.” It’s natural to describe teamwork as “we,” but in a competency-based interview, it erodes your evidence. Assessors can’t score “the team.” They can only score you. Be specific about your contribution, even — especially — when it was part of a group effort.
Picking the first example that comes to mind. Rushed preparation leads to weak examples. The example you choose matters as much as how you structure it. Prepare your evidence bank beforehand and select examples that genuinely showcase the competency.
Rushing through the Action. Most candidates spend too long on the Problem and not enough on the Action. This is backwards. The Problem is context; the Action is evidence. Flip the balance.
Vague outcomes. “It had a positive impact” means nothing. Numbers, timelines, and human impact give assessors something to score.
Tips for Hiring Managers Using PACE
PACE is only as fair and reliable as the people running it. If you’re an assessor or hiring manager, the framework demands rigour from you too.
Ask the same questions in the same order, every time. This isn’t just good practice — under the Equality Act 2010, inconsistent questioning can expose your organisation to discrimination claims. Structure is your protection.
Define your scoring anchors before interviews start. What does a “3 out of 5” look like for this competency? What does a “5” look like? If you can’t answer that before the panel convenes, you’re at risk of unconscious bias creeping into your scoring after the fact.
Probe neutrally. If a candidate gives a vague answer, you need to probe. But the way you probe matters. “Can you tell me more about what you specifically did?” is neutral. “So did you take the decision to escalate?” is a leading question that corrupts the evidence. Let candidates find their own words.
Score as you go. Don’t wait until you’ve seen all the candidates to complete your scoring matrix. Memory is unreliable, and recency bias is real. Score each answer as it happens, while it’s fresh.
Keep your notes. If a recruitment decision is ever challenged, contemporaneous scoring notes are your evidence. Brief observations under each scored component will serve you far better than end-of-day summaries written from memory.
FAQ
What does PACE stand for in an interview?
PACE stands for Problem, Action, Conclusion, and Evaluation. It’s a structured framework used in competency-based interviews that guides candidates through giving evidence-rich, reflective answers based on real past experiences rather than hypothetical responses.
Is PACE the same as STAR?
They’re closely related but not the same. STAR (Situation, Task, Action, Result) is more widely used in corporate settings and stops after the Result. PACE adds a fourth step — Evaluation — which asks candidates to reflect on what they learned. That might sound like a minor difference, but in roles where personal development and self-awareness are important, it’s actually a significant one. A STAR answer without an Evaluation will often score lower in a PACE-based assessment.
Where is PACE commonly used in the UK?
PACE is particularly prevalent in UK public sector recruitment — police forces, NHS trusts, fire and rescue services, local government, and the Civil Service. You’ll also encounter it or close variants in corporate graduate schemes and structured assessment centres at firms like KPMG, Deloitte, and the BBC. Many hiring managers use the PACE methodology even when they don’t call it by that name.
How long should a PACE interview answer be?
Aim for somewhere between two and four minutes. Problem: 30 to 45 seconds. Action: 60 to 90 seconds (this should be your longest section). Conclusion: 30 to 45 seconds. Evaluation: 30 to 60 seconds. Practise out loud — most people are surprised by how quickly they reach the upper end of that range.
How many PACE examples should I prepare?
Prepare at least six to eight solid examples before you go in. Map them against the competencies listed in the job description and make sure you’re not relying on the same scenario for multiple questions. If an assessor notices you’ve used the same example twice, it raises concerns about the breadth of your experience.
Can I use personal or voluntary examples in a PACE interview?
Absolutely, especially at the entry level or if you’re changing careers. What matters is the quality and relevance of the evidence, not whether it came from a paid job. Volunteering, community roles, sports leadership, university projects — all of these are fair game. The PACE framework doesn’t care where the experience happened; it cares about the competency you demonstrated.
How do I prepare for a PACE interview in the UK?
Start with the job description and person specification. Identify the competencies being assessed and research the organisation’s published frameworks if there are any (the College of Policing CVF, NHS Healthcare Leadership Model, and Civil Service Success Profiles are all freely available online). Then map your strongest examples to each competency. Practise your answers out loud — ideally with someone who can give you honest feedback — and time yourself. A polished PACE answer takes more preparation than most candidates realise, but that preparation pays off.
Conclusion
PACE interviewing isn’t complicated. But it does reward preparation in a very direct way — probably more than any other interview format.
The framework is designed to be fair, structured, and evidence-based. If you understand that going in, you can work with it rather than against it. You know what the assessor needs. You know which component they’ll probe if you’re vague. You know that the Evaluation — the bit most people skip — is often where the highest-scoring candidates pull ahead.
So prepare your examples carefully. Practise structuring them out loud. Don’t hide behind “we.” Quantify your outcomes. And take the Evaluation seriously — because that’s where you show them not just what you’ve done, but who you are as a professional.
If you’re a hiring manager, hold yourself to the same standard of rigour. PACE works when it’s implemented consistently. The structure protects you legally and produces better hiring decisions. Use it properly.
Good luck — though if you’ve done the preparation, you won’t really need it.
