STAR Method Example Answers for Government Interviews

Most STAR examples online are written for corporate interviews. They are fine as structure, but they miss what a government panel is doing: marking your answer against a named capability at a named level. A story that would impress a hiring manager can score poorly with a public sector panel simply because the evidence sits at the wrong level.

These four examples are written for that context. Each one names the capability it evidences, and after each answer there is a short note on how the same story would need to change to carry a higher classification.

The proportions that work in a panel interview

• Situation — two sentences. Enough context for the decision to make sense, no more.
• Task — one sentence naming what you specifically were accountable for. Panels use this to confirm the story is about you.
• Action — around 60% of the answer. What you did, in order, and why you chose it over the alternative.
• Result — what changed, with a number if you have one, and one line on what you took from it.

Aim for around two minutes spoken. If more than half your answer is scene-setting, the panel has stopped recording evidence. Our STAR method examples page covers the structure in general; this article is the public sector version.

Example 1 — Achieves results (prioritising under pressure)

Situation: "Our processing queue ran at about forty applications a week. A two-day system outage left us well behind, with statutory deadlines on some of the files."

Task: "I was responsible for my own queue and for flagging risk to my team leader."

Action: "I re-sorted the backlog by statutory deadline rather than date received, identified the six at real risk, and told my team leader that morning so the risk was visible rather than discovered. I drafted a short holding message for the applicants likely to run late, which she approved, and worked the six first."

Result: "None of the six missed a deadline, the backlog cleared in three days, and no applicant chased us because they had already been told."

Why it scores: there is a reason for the order of work, and the escalation happened before the failure rather than after it. To carry this story at APS 5 or above, the emphasis would shift from working the queue correctly to changing how the queue was triaged for everyone.

Example 2 — Cultivates productive working relationships

Situation: "I co-ordinated a quarterly report needing figures from three business areas, and one supplied late every quarter."

Task: "The report deadline was mine."

Action: "Instead of escalating, I asked to see how their extract was produced. Their data was not available until after their own monthly close — the deadline we had agreed had never been achievable for them. I rebuilt the sequence around their real close date, asked for a partial extract earlier so I could start, and confirmed the new arrangement in writing so it did not depend on either of us remembering."

Result: "The report went out on time for the next three quarters. The change removed a recurring escalation instead of repeating it."

Why it scores: the panel is listening for what you attempted yourself before involving management. Escalation as the first move reads as avoidance at every level above APS 4.

Example 3 — Exercises judgement and manages risk

Situation: "My branch head asked me to look at why processing times had blown out. There was no further definition than that."

Task: "I had to turn a loose question into a piece of work I could stand behind."

Action: "I split it into three questions that could actually be answered — volume, staffing and rework — and pulled six months of data on each. Rework accounted for most of the movement, and within rework two request types accounted for the majority. Before doing the full analysis I wrote the scope down and tested it with two team leaders, which corrected one of my assumptions about seasonal volume."

Result: "I recommended a change to the intake form for those two request types. Rework on them fell by roughly a third the following quarter, and I had ruled out staffing with evidence rather than assertion."

Why it scores: the value is in reframing the question defensibly, which is exactly what APS 6 and above are being asked to do. At APS 5 the same story would be told as scoping and delivering the analysis you were given.

Example 4 — Personal drive and integrity

Situation: "Six weeks after publication I found an error in a figure in our annual report. Nobody had queried it."

Task: "Raising it meant a formal correction and some discomfort for the area that had supplied the figure."

Action: "I verified the error against the source data before saying anything, took it to my director the same day with the corrected figure and a paragraph on the cause, and drafted the correction notice myself rather than handing the problem over."

Result: "The correction was published and I added a two-person verification step for published figures, so the outcome was a process change rather than an apology."

Why it scores: values questions are marked on action through the proper channel. An answer that describes a belief, or something you noticed but did not act on, gives the panel nothing to record.

Three habits that separate a scored answer from a good story

• Name the decision. Somewhere in the action there should be a moment where you chose between two options and can say why.
• Keep the result honest. An approximate number stated as approximate is stronger than a precise one you cannot defend under probing.
• Match the level. Applying the guideline, deciding inside it, defining the work, or deciding about other people's work — pick the one the classification calls for.

For question sets by jurisdiction, see government interview questions and answers, and for classification-specific pitching try APS 5, APS 6 or EL1. To rehearse these out loud with feedback on structure and evidence, use the Interview Practice Lab.