Bluewatch — jobs that answer the call

What to expect at a firefighter interview and assessment day

The structure most UK fire and rescue services use for final interviews and assessment centres — and the kind of evidence panels are actually looking for.

By the time you reach the assessment centre or final interview, the service has already filtered out the bulk of applicants on application form, online tests, and often the physicals. The panel is no longer asking "can this person do the job physically?" — they've answered that. They're asking: "Is this person the kind of firefighter we want on our watch in five years' time?"

That's a fit-and-evidence question, not a fitness question. This guide explains what panels are looking for and the kinds of mistakes that get flagged in feedback notes.

How services structure the day

Service-specific, but a typical assessment centre runs through a similar set of components:

  • Welcome and briefing — short presentation about the service, the role, and the day. This is not assessed; it's your chance to read the room and ground yourself.
  • Roleplay — typically a "safe and well" home visit scenario or a community engagement situation. You sit opposite a trained role-player; you have a brief to read, then a few minutes to handle the situation.
  • Written exercise — drafting a short report, note, or response to a brief. Marked on clarity, structure, and judgement under time pressure.
  • Group exercise — 4 to 6 candidates given a problem with limited information. Marked on how you contribute, not on whether the group reaches the "right" answer.
  • Behavioural interview — a structured interview using STAR-style questions, mapped to the service's competency framework.
  • Verbal/numerical re-check — some services re-verify the online tests in person.

You won't necessarily do all of these in one day, and the order varies. London Fire Brigade combines roleplay, interview, written exercise and an online re-check at one assessment centre. West Midlands runs a separate behavioural interview stage with a roleplay around "safe and well" principles. The core components show up in one form or another regardless of service.

The competency framework: PQAs

UK fire services assess candidates against Personal Qualities and Attributes (PQAs). The list comes from the National Firefighter Selection framework and is broadly consistent across services, though the exact wording varies. The core PQAs you'll be assessed on at firefighter level are:

  • Working with Others — how you contribute to and within teams, including teams under pressure
  • Confidence and Resilience — staying composed under stress, recovering from setback
  • Commitment to Excellence — high standards in your own work, taking professional pride
  • Commitment to Diversity and Integrity — treating colleagues and the public fairly, ethical conduct
  • Effective Communication — clear, calm, audience-appropriate communication
  • Commitment to Development — willingness to learn, take feedback, grow technically
  • Situational Awareness — reading what's happening, making sense of incomplete information

Most services publish their PQA list openly. Read your service's published list before the interview. The interview questions are mapped directly to these — if you know the framework, you know what evidence the panel is looking for in each answer.

Why panels use STAR

STAR is Situation, Task, Action, Result. It's the structure most public-sector competency interviews use because it forces concrete evidence:

  • Situation: what was the context?
  • Task: what did you specifically need to achieve?
  • Action: what did you do (not what the team did — what you did)?
  • Result: what was the outcome, and what did you learn?

The "Action" step is where most candidates fall down. Panels flag this constantly in feedback: "candidate spoke about what the team did, not what they personally contributed." If your answer doesn't make clear what you personally did, the panel can't score you against the competency.

A useful prep tactic: take each PQA, write three concrete real-life examples, and rehearse them in STAR structure until you can deliver each in 4–5 minutes without notes. Don't memorise word-for-word — that comes across rehearsed and stilted. Memorise the bullet points and let the words come naturally on the day.

What the panel is actually probing for

A few worked examples without giving anything away:

  • Working with Others under pressure. They want evidence you can adjust your role on the fly, take instruction, give instruction, and rebuild a working relationship after disagreement. Good answers reference specific colleagues or moments. Weak answers stay generic ("I'm a good team player").
  • Confidence and Resilience. They want evidence you can stay functional when things have gone wrong — not heroically immune to stress, but honest about what stressed you and how you handled it. The candidates who get caught out here are the ones who pretend nothing has ever shaken them. Panels read that as either dishonest or insufficiently self-aware.
  • Decision-making with incomplete information. This is what the roleplay and written exercise are mostly testing. They give you less time and less detail than you'd want, deliberately. They're checking that you can act on what you have without freezing, asking for the impossible, or making it up.
  • Dealing with a public that doesn't want your help. Common roleplay setup: a community member is hostile, refusing engagement, or in personal distress. They want to see you stay calm, listen, adapt your approach, and not take it personally. They're not testing whether you can "win" the conversation — they're testing whether you can keep showing up professionally when it's hard.

The biggest mistakes candidates make

Recurring patterns from feedback notes across services:

  • Talking about the team, not yourself. Already covered. The single biggest cause of low interview scores. Use "I" not "we."
  • Generic answers without examples. "I really care about diversity" is not an answer. "Last year on my project, I noticed X colleague was being talked over in meetings, so I…" is.
  • Over-rehearsed delivery. Reciting an answer word-for-word is more obvious than candidates think. Memorise the structure and the key facts; let the words come on the day.
  • Bluffing on a topic you don't know. If a question goes somewhere you don't have evidence for, say so honestly and offer a related example instead. Panels respect "I don't have strong experience there, but a related situation was…" much more than a bluffed answer.
  • Talking too long. Aim for 4–5 minutes per main answer. Going over 7 minutes with a single example dilutes your evidence and eats your other questions' time.
  • Not knowing the service. Not knowing your service's basic structure (number of stations, area covered, recent strategic priorities, who the chief fire officer is) reads as not really wanting the job. Most services publish all of this on their website. Read it.
  • Treating roleplay as a sales pitch. The trained role-player isn't a customer — they're a probe. Trying to "sell" them on something or talk over their concerns gets marked down. Listening, adapting, and being human gets marked up.

What to wear, what to bring

  • Smart office-wear — suit and tie / smart trousers and shirt / equivalent professional dress. Polished shoes. The specific level of formality varies by service, but err on the smart side. Casual reads as not taking it seriously.
  • Photo ID — passport, driving licence, or both if you have them. Services check.
  • Water and snacks — assessment centres can run 6+ hours.
  • A pen and notepad — for the written exercise, the briefing notes, and your own notes if you want to make any.
  • Don't bring — coffee mugs from your current employer, branded fleece from another emergency service, anything that suggests divided focus.

Right before, on the day

Three small things matter more than most:

  • Sleep the night before. Don't try to cram answers at 1 a.m. Tired candidates underperform on every measure — verbal, written, behavioural.
  • Eat properly. Going in hungry costs you cognitive sharpness for the written and roleplay components.
  • Arrive early. Aim to be at the venue 30 minutes before start. The service will have a check-in area; use the time to read your roleplay brief carefully, drink water, and breathe.

Above all: be honest, be specific, and be yourself. Panels meet hundreds of candidates. Authenticity is unfakeable and unmistakable, and it's the single thing they remember.

Built by a serving firefighter. Assessment centre and PQA structure sampled from London Fire Brigade, West Midlands Fire Service, County Durham & Darlington Fire and Rescue Service, and the National Firefighter Selection framework as of 2026.

Browse roles mentioned in this guide

Related guides

Talking to other candidates

Bluewatch tracks the jobs — for live discussion, candidates compare notes on r/firebrigade and the long-running UK Firefighter Recruitment group on Facebook. We aggregate; we don't run a chat platform.