STACC Done Right: The Fire Service Twist on STAR That Actually Surfaces Character

Retired fire captain. Twenty-five-plus years in the Southern California fire service. My sons Daniel and Tom built FireHire, and they keep asking me to write down what I'd tell any candidate sitting across from me at a panel. So here's the next one.

Last post I told you what panels are actually scoring. Six traits, not your firefighting knowledge. If you didn't read it, the short version is: we hire character first, train skills second.

Now let's talk about the framework that actually surfaces character — because if you walk into a panel without a structure, even your best stories sound like a rambling phone call.

You've heard of STAR. Most of you learned it in college or for a corporate job. Situation, Task, Action, Result. It works fine. The fire service uses a tweaked version called STACC — and the extra letters are exactly where the character traits from the last post show up.

Let me walk you through it.

STAR in 60 seconds

You probably already know this, so I'll be quick.

S — Situation. Where, when, who. T — Task. What was your job in that moment. A — Action. What you did. R — Result. What happened.

Universal. Used everywhere. Works for behavioral interview questions in any industry. If you've prepped for a job in the last ten years, you've probably been told to use it.

Here's where it falls short for the fire service: it stops at the result. We need more.

STACC, letter by letter

STACC is Situation, Task, Action, Consequence, Change. Same first three letters as STAR. The shift is in the last two — and the very last letter is where most candidates lose the panel without ever knowing it.

S — Situation

Set the scene in two sentences. Where you were. When it happened. Who was involved. That's it.

The most common mistake I see is candidates spending 90 seconds painting the scene before getting to the point. We don't need the weather. We don't need your shift schedule. We don't need the name of every coworker.

"I was working a shift at my warehouse job last spring. We were short-staffed and a forklift went down."

Done. Move on.

What this surfaces: Plain talk. Can you tell us where we are without burying us?

T — Task

What was YOUR specific responsibility in that moment? Not the team's task. Not the company's task. Yours.

The trap here is that candidates default to "we were responsible for..." That tells us about the group. We asked about you.

"My job was to get the line moving again before the next truck arrived in 40 minutes."

That's a clear personal stake. Now we know what was on your plate, specifically.

What this surfaces: Ownership without flinching. You're already on the hook before you even tell us what you did.

A — Action

What did you actually DO. Specific verbs. Specific decisions.

This is where most candidates either go vague or go group. Vague sounds like "I addressed the situation and worked with the team to find a solution." Group sounds like "we coordinated and decided that the best approach would be..."

Neither tells me anything.

I want: "I called the swing-shift supervisor and asked if Jose could come in two hours early. He said yes. I rerouted the inbound truck to bay 4. I grabbed the manual jack and got the pallets we could move out of the way myself."

That's three specific actions, all yours. I can picture it. I can grade it.

If the question asks what YOU did and you say "we" — you're not answering the question. We notice every time.

What this surfaces: Composure under pressure. Crew fluency. Did you stay clear-headed and did you involve other people in the right way?

C — Consequence

What happened as a result of what you did?

Here's where you have to be honest. Don't only tell us the times it worked. If you got the line moving but the truck still arrived late, say so. If your fix held for two days but then broke again — say that.

Panels can hear when a candidate is editing their stories to look good. We've heard ten thousand answers. We know what real sounds like.

"The line was moving by the time the truck got there. We were behind, but only by 15 minutes instead of being totally backed up. Jose got time-and-a-half he wasn't expecting, which he was fine with. My supervisor was happy."

Real consequences include the small messy parts. Don't hide them.

What this surfaces: Listening (did you notice what actually happened, not just what you wanted to happen?) and ownership (can you tell us about a result that wasn't perfect?).

C — Change

★ This is the letter most candidates skip. It's also the one we weight the heaviest.

What would you do differently next time? What did this teach you about yourself?

If you can't name what you'd change, you didn't actually learn from it. And if you didn't learn from it, why are you telling me this story?

This is the humility letter. It's where character shows up most clearly. A candidate who can say "I should have called the supervisor 20 minutes earlier instead of trying to figure it out alone — I learned I'm slow to ask for help when I'm under pressure, and I've been working on that" is a candidate I want to hire.

A candidate who says "honestly I'd do it the same way, it worked out" — has just told me they don't grow.

The Change isn't optional. The Change is the part that proves the rest of the story is real.

What this surfaces: Humility, self-awareness, growth, and the whole character thread we covered in the last post.

Side-by-side: weak vs STACC

Let me show you what this looks like with two real oral board questions. Same question, weak answer, then STACC answer. Read both out loud — you'll hear the difference.

Q: "Tell us about a time you disagreed with a coworker."

Weak answer:

"I had a coworker once who I disagreed with on how to handle a situation. We talked it out and came to an agreement. I think communication is really important and I always try to handle conflict professionally."

That's a non-answer. There's no story. There's no specific. There's nothing for us to grade.

STACC answer:

(S) "I was working a swing shift at my last job, on a small crew of four. (T) My job was to close out the day's deliveries by 8pm so the morning crew could start clean. (A) One of my coworkers, Marcus, kept signing off on deliveries that weren't actually verified. I'd been quiet about it for a couple weeks because he had more seniority than me, but it was making my closeout messy. One night I asked him to walk me through his sign-off process. He showed me, I told him what I was seeing, and we agreed I'd start verifying behind him until he could clean it up. (C) The deliveries were accurate within two weeks. He didn't love that I'd flagged it, but he respected that I'd come to him directly instead of going to the supervisor. We're still friendly. (Change) Looking back, I waited too long. Two weeks of being quiet was two weeks of bad data. I've gotten faster at having those conversations early — not waiting for them to become a problem."

Same situation. Different answer. The STACC version actually shows me composure (calm conversation), ownership (he didn't blame Marcus), people-first (he respected Marcus's seniority and dignity), and humility (the Change). I can grade this.

Q: "Tell us about a time you failed."

Weak answer:

"My biggest weakness is that I sometimes work too hard and burn myself out. I've learned to take more breaks."

That's the humble-brag failure. It's not a failure. It's a way to brag about being a hard worker while pretending to be vulnerable. Every panel can spot this from across the room.

STACC answer:

(S) "Two years ago I was a shift lead at a restaurant. (T) Part of my job was managing the schedule for six servers. (A) I had a server, Amanda, who'd been having a hard time at home. She asked me three times if she could swap out of a Friday close. I kept telling her I'd figure it out and then didn't actually do it. The Friday came and she was so checked out she ended up in tears in the back. (C) She quit the next week. Honestly, I was the reason — not the only reason, but a real one. (Change) That was the moment I realized I was prioritizing my own bandwidth over my people's actual lives. I started using a shared schedule sheet so I couldn't 'forget' requests, and I built a habit of saying yes-or-no within 24 hours instead of letting things float. I haven't had anyone quit on me since."

That's a real failure. Real cost. Real ownership. Real change. I'd hire that person.

Common STACC mistakes

Things I watch candidates do over and over.

Skipping the second C. The most-skipped, highest-weighted letter. If you don't name what you'd change, your answer is incomplete and it costs you.

Saying "we" when we asked what YOU did. Every time. We will follow up: "what did YOU specifically do?" If you can't answer, you've shown us that you don't actually own your work.

Performing the framework instead of using it. This is the cadence trap. Some candidates have practiced STACC so much that you can hear them counting it out: "first the situation, then the task, then..." It sounds rehearsed because it is. The framework should disappear inside a real story, not announce itself.

Picking a too-small story. If your "biggest failure" is forgetting to send an email, the panel knows you're hiding the real one. Pick something that actually mattered.

Faking the failure. Manufactured weaknesses are obvious. Don't say you "care too much" or "work too hard." Say you missed something real, name what it cost, name what you changed.

How to practice STACC so it doesn't sound rehearsed

Here's the part most prep materials don't teach.

Don't memorize answers. Memorize the structure and the stories that fit. If you memorize an answer, you'll deliver it with the cadence of someone reciting. If you internalize the structure and walk in with five real stories you know cold, you can adapt to whatever the panel actually asks.

Practice OUT LOUD with another human. Not in your head. The voice tells the truth. You'll hear yourself rambling on the Situation. You'll hear yourself skipping the Change. You can't catch this silently.

Vary the story you use for each letter. If you only have one good ownership story, you'll get caught when the panel asks two ownership-flavored questions in a row. Build a deck of five or six real stories you can pull from. Cross-train them across the question types.

Use the AI tool to drill the rhythm. My boys built the FireHire oral board prep for exactly this — practice STACC against an AI that scores you on the six traits from the last post. Use it. The point isn't to memorize the questions. The point is to get reps where you can hear yourself and tighten the rhythm without burning real practice partners.

Closing

Here's the through-line from both posts.

Six traits + STACC = the actual prep. The traits are what panels are scoring. STACC is the structure that makes sure the traits show up.

If your STACC answer doesn't surface at least one of those six traits cleanly, the framework didn't save you. Go back. Find the trait. Rewrite the answer until it shows up.

Do that 20 times before your panel and you'll walk in different than you walked into your last one.

Go get hired.

— Patrick Latham, Retired Fire Captain — Southern California

Patrick Latham

Retired Fire Captain — Southern California

25+ years in the Southern California fire service, retired as Captain. Served on countless hiring panels. Patrick is Daniel and Tom's dad — and the source of most of the panel-tested coaching wisdom baked into FireHire.

FireHire provides general preparation content and does not guarantee hiring, interview results, test scores, or employment outcomes. Content may be AI-assisted and should be independently evaluated.