If you are preparing for a competency-based interview in the Irish civil service or a local authority, you will meet the STAR method within ten minutes of starting your research: Situation, Task, Action, Result. It is the structure I teach, and it is the structure most Irish interview boards are used to hearing. This post explains what each part is for, where candidates go wrong with it, and why the task, the part most people treat as filler, is the sentence that tells the board what to credit you for.
One admission before the method. For a few years I taught a three-part version that dropped the task, on the grounds that it repeated the situation. Taught badly, it does. Taught properly, it is the part of the answer that separates you from your team, and I would rather you had it.
What is the STAR method?
The STAR method is a way of structuring an answer to a competency-based interview question, the kind that starts "Tell me about a time when" or "Give me an example of". You describe a real situation from your own experience, say what your role in it was and what you had to achieve, explain what you did, and finish with what happened. Boards in publicjobs competitions and council competitions score your evidence against the published capability framework or competency model, and a STAR answer puts that evidence in the order a board can mark it.
That is the whole method. What follows is how to weight it, because the four parts are not equal.
Situation: keep it short
Set the scene in a sentence or two. Where were you working, what was going on, and why did it matter? The board needs enough context to follow your actions and no more. Candidates who run long here are not losing marks on the situation itself; they are spending time that the action needed.
Task: tell the board what your role was and what you had to achieve
This is the part to get right, and the part most candidates waste. The task is not a second description of the situation. It is one or two sentences that tell the board two things: what your role was, and what you, personally, were there to achieve.
"The system was failing, and my task was to fix the system" adds nothing. "The system was failing. As the team lead, my task was to get it stable within the week without pulling staff off the year-end returns" tells the board who you were in the story, what you were responsible for, and what a good outcome would have looked like. Everything you say in the action is now measured against that sentence, and everything you report in the result is credited to you rather than to your team.
That is why the task matters most for people who work in teams, which is nearly everyone. The board is assessing you, not your unit. If the task is clear, "I" comes naturally in the action, because you have already told the board which part of the work was yours. If the task is missing, the action drifts into "we", and an answer full of "we" leaves a board with nothing it can attribute to you. I have written separately about I-centred language, because it is the most common fix in my coaching sessions; a good task sentence does half of that work before the action starts.
Three questions to check your task against. What was my role? What was I responsible for delivering? What did success look like for me, as distinct from the team? If your task answers all three in two sentences, move on.
Action: where the marks are
Spend most of the answer here. Boards in competency interviews are assessing what you did, because your actions are the evidence that you have the capability the question is testing. Walk the board through your decisions and your reasoning: what you looked at, what you weighed, what you chose, and what you did when it did not go to plan. Be specific about the steps and say why you took them. Use "I".
If the task is clear, this section is easier to write, because you are describing how you did the thing you said you had to do.
Result: what changed, and how you know
State the outcome plainly. What changed, by how much, for whom, and how do you know? Quantify where you honestly can, and do not invent numbers to sound impressive. If the result was modest, give the modest result with confidence; boards trust specific and modest over vague and grand. "It went well" is not a result. And tie the result back to the task: you said what you had to achieve, so say whether you achieved it.
A worked example
The question is "Tell me about a time you managed a difficult stakeholder relationship."
Situation. In my previous role I led a project in which a key external partner objected strongly to a change in our approach. They were vocal about it, and there was a real risk the relationship would break down at a critical point in the project.
Task. As project lead, I owned that relationship. My task was to keep the partner engaged and get the change agreed without losing the delivery date. Nobody else was going to do it.
Action. Rather than respond by email or in a group setting, I arranged a one-to-one meeting with their senior contact. I prepared by going through the points they had raised and separating what was valid from what came from a misunderstanding of our plans. In the meeting I listened first and let them set out their concerns fully before I responded, which lowered the temperature considerably. I then acknowledged what was legitimate, adjusted one element of our approach, and explained the reasoning for the parts we were keeping. I followed up in writing the same day so there was no ambiguity, and from then on I updated them at each milestone rather than waiting for them to come to me. By the midpoint of the project they had moved from a source of friction to actively helping resolve issues on their side.
Result. The partner stayed engaged throughout and the project was delivered on time. Their feedback afterwards named our communication approach as a positive. Against the task I set out, both parts were achieved: the partner stayed with us and the date did not move.
Look at the proportions. The situation and task together are five sentences. The action is most of the answer. The result is three sentences, and it answers the task.
How long should each part of a STAR answer be?
A full competency answer runs about two minutes. As a rough guide, the situation and task together should take well under thirty seconds, the action should take more than a minute, and the result should take around fifteen seconds. If your set-up runs longer than that, the board is waiting for markable content. If your result is a single sentence, you are probably leaving evidence unsaid.
Does the board care whether you use STAR?
No. Nobody on an Irish interview board is marking your acronym. They are marking your evidence against the framework published for your competition, and boards are trained to listen for structured answers because structure makes the evidence easier to find. STAR is the structure most of them are used to, which is one reason I teach it, but the marks come from the content of each part, not from the letters.
Some coaches add a fifth part for a learning point, making it STARL or similar. A brief reflection can work when the example had a lesson in it, particularly on a question about a setback. As a compulsory ending to every answer it becomes filler, and boards can hear filler.
What STAR will not fix
Structure organises an answer. It cannot rescue one. Three problems survive any structure.
- "We" instead of "I". Covered above, and worth repeating: the board cannot credit what it cannot attribute to you.
- An example that does not match the competency. A strong story about delivering results, told in answer to a question about leading people, is scored as an answer about leading people, and a weak one. The fix is preparation: build an example bank mapped to your framework before the interview, so the right example is ready for the question asked. If you are in a civil service competition, my guide to the capability framework explains what each dimension is asking for.
- A result you cannot evidence. If you cannot say what changed and how you know, the example is not ready.
Practice it out loud
Reading your examples silently is not practice. Say them aloud, time them, and record one so you can hear where the situation ran long or the task went missing. The free interview preparation checklist puts the full sequence in order, from example bank to the day itself.
If you want to test your answers against someone who will interrupt and probe the way a board does, I offer civil service and local authority interview preparation sessions, with written feedback after each. You can read what a session involves before booking. Email me at sarah@dedico.ie with your competition and your date.
Frequently asked questions
What is the STAR interview method?
STAR stands for Situation, Task, Action, Result. It is a way of structuring an answer to a competency-based interview question so that the board hears a short piece of context, a clear statement of your own role and what you had to achieve, a detailed account of what you did, and a specific outcome, in that order. Most of the marks are awarded for the action, so most of the answer goes there.
What is the task in the STAR method?
The task is one or two sentences stating what your role was in the situation and what you, personally, were there to achieve. It is not a restatement of the situation. It tells the board which part of the work was yours, so that the actions and result that follow are credited to you rather than to your team.
How long should each part of a STAR answer be?
About two minutes in total. The situation and task together should take well under thirty seconds, the action should take more than a minute, and the result should take around fifteen seconds and answer the task.
Do Irish civil service and local authority interview boards require the STAR method?
No. Boards mark your evidence against the published capability framework or competency model for your competition, not the structure you use. STAR is the structure most boards are used to hearing, and it puts your evidence in the order a board can score, which is why it is worth using.