The STAR method for UN competency interviews: a complete tutorial
Last updated 2 August 2026
Every UN competency interview is scored against evidence. STAR is how you supply it.
This is lesson 7.3 of UN Career Academy, module 7: The Competency-Based Interview. It is free to watch in full, with no account and no payment. The narration follows the video, less the closing pointer to the lessons that come after it.
Transcript
The STAR method is widely described and widely misapplied. Most candidates who know about it still give answers that are too heavy on Situation and Task, too thin on Action, and have no Result at all. This video gives you the full tutorial: what each component is for, how long each component should be, and what the most common errors look like.
S — Situation
Set the context briefly. Where were you working? What was the organisation? What was the background to the situation you are about to describe?
Duration: one to two sentences. This is not the story — it is the context for the story. Candidates who spend three minutes on the Situation and rush the Action are telling the wrong story. Keep it brief. Include the organisation, your role, and the specific challenge you were facing.
T — Task
What was your specific responsibility or challenge in this situation? Not the team's challenge — yours specifically. What were you personally expected to deliver, decide, or resolve?
Duration: one to two sentences. The Task establishes why the Action mattered — without it, the Action has no stakes.
A — Action
This is the substance of the answer. What did you do? Specifically. Step by step. Using 'I' — not 'we'. Not 'the team decided' — 'I proposed the following approach', 'I took the following steps', 'I specifically did X and then Y.'
Duration: the majority of your answer — three to five sentences minimum. This is where you demonstrate the competency. The Situation and Task set the scene; the Action is the evidence.
Three specific instructions on the Action:
First: use the first person singular. The panel cannot score a team's performance — only yours. 'We coordinated the response' tells the panel nothing about what you specifically did. 'I designed the coordination mechanism and chaired the weekly working group, managing the competing priorities of four agencies' tells the panel what your contribution was.
Second: be specific about the steps. Not 'I managed the project carefully' — 'I built a three-week work plan with daily milestones, identified the two critical dependencies early, and escalated one resource constraint to my supervisor ten days before the deadline.' The specificity is the evidence.
Third: demonstrate the competency through the actions you describe. If the question is about Planning and Organising, your Action should include specific planning activities — timelines, resource allocation, risk identification. If the question is about Communication, your Action should include specific communication choices — who you communicated with, how you adapted the message, what response you received.
R — Result
What happened? What was the outcome? How did the situation resolve?
Duration: one to two sentences. Quantify where genuinely possible — 'the report was delivered on time and adopted by the steering committee', 'the team's output improved by X%', 'the negotiation produced agreement where previous attempts had failed'. If you cannot quantify, be specific — 'the revised process was adopted and is now the standard approach'.
Then, in one additional sentence: what did you learn? What would you do differently? This final line signals self-awareness and a genuine orientation toward continuous improvement — qualities the panel is assessing beyond the specific competency.
The five most common ways candidates break the STAR structure:
Error 1: 'We' instead of 'I' throughout the Action. The panel scores your contribution. If you describe the team's actions without specifying your own, the answer is unscoreable.
Error 2: Situation and Task are the whole answer. The candidate describes a complex, interesting situation at length — and never gets to what they personally did about it.
Error 3: No Result. The candidate describes a detailed, impressive Action and then trails off. 'And so that was how I handled it.' What happened? Did it work? The panel is left without the evidence of impact.
Error 4: Generic language throughout the Action. 'I communicated effectively with all stakeholders.' Communicate how? Which stakeholders? What were the competing interests? How did you adapt? Generic language makes the answer unspecific and unscorable.
Error 5: The hypothetical answer. 'What I would do in that situation is...' — the question asked for a past example, not a theoretical approach. If you give a hypothetical answer, tell the panel to stop you: they will.
*Question: 'Tell me about a time when you had to communicate complex technical information to a non-specialist audience.'*
S: 'In 2023, while working as a Programme Officer at an international NGO managing food security programming, I was asked to present the findings of a multi-month nutritional assessment to a group of government ministry officials — most of whom had no statistical background.'
T: 'My responsibility was to ensure that the ministry team understood the key findings well enough to make an informed decision about the programme design, which had significant funding implications.'
A: 'I identified the three findings that were directly decision-relevant and dropped seven others from the presentation entirely. For each of the three findings, I developed a visual summary — a single chart — that showed the key comparison without requiring statistical interpretation. I pre-briefed the Ministry's technical focal point two days before the meeting to identify any terminology that might be misunderstood and adjusted two of the slides accordingly. During the presentation, I used a consistent structure — finding, what it means for the programme, what the options are — and paused for questions after each section rather than presenting all three together.'
R: 'The ministry team agreed to the programme design recommendation at the meeting rather than requesting a further review, which had been the outcome in a comparable earlier process. In a debrief with the focal point, he noted that the earlier process had failed partly because the team did not feel confident they understood the evidence. I learned that the investment in presentation design before a high-stakes audience is at least as important as the quality of the underlying analysis.'
STAR: Situation (context, brief), Task (your specific responsibility), Action (the bulk — specific steps, first person, demonstrating the competency), Result (outcome, quantified where possible, plus a lesson). Two to three minutes spoken. No generics, no 'we', no missing Result.
The rest of the course
This lesson is one of sixty. The full course covers the UN system and its contract grades, every route in, building the profile, the application process end to end, assessments, the competency interview, what happens after it, and the agencies themselves.
See what is included and what it costs, or watch the other free lessons: