Knowing the method is not the same as using it.

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 and too thin on Action and Result, which is the failure this lesson is about. These are the five most common ways candidates break the structure: ‘we’ instead of ‘I’, Situation and Task as the whole answer, no Result, generic language in the Action, and the hypothetical answer.

Error 1: ‘we’ instead of ‘I’ throughout the Action. The panel scores your contribution. Describing the team’s actions without specifying your own leaves them nothing to score.

Error 2: Situation and Task are the whole answer. A long, interesting situation, and the candidate never reaches what they personally did.

Error 3: no Result. A detailed Action that trails off: ‘And so that was how I handled it.’ Did it work?

Error 4: generic language throughout the Action. ‘I communicated effectively with all stakeholders.’ Communicated how? Which stakeholders? What were the competing positions?

Error 5: the hypothetical answer. ‘What I would do in that situation is...’ The question asked for a past example, not a theoretical approach.

The fix is not more knowledge of the acronym. It is writing one out and looking at the shape of what you wrote, which is what the rest of this lesson does. Each of the five errors becomes a check in the writing steps, as far as a machine can see it.

Photograph: Schölla Schwarz, CC BY 3.0, via Wikimedia Commons, modified

The lesson in outline

The STAR method for UN competency interviews: a complete tutorial

Each step’s heading and the paragraph that opens it. I built the lesson to be worked through step by step, so it is above: interactive, and it ends in something you write for your own application.

Knowing the method is not the same as using it.
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 and too thin on Action and Result, which is the failure this lesson is about. These are the five most common ways candidates break the structure: ‘we’ instead of ‘I’, Situation and Task as the whole answer, no Result, generic language in the Action, and the hypothetical answer.
Each part has a length, and the Action is the bulk.
The durations below are the lesson’s, in sentences. They are what the checks in the writing steps count, so they are worth reading before you write rather than after.
The Action should be more than half of the answer, by words.
The lesson asks for the Action to be the majority of the answer, and a majority means more than half: the Situation, Task and Result together must come to fewer words than the Action.
Pick one competency question, and write it down.
A STAR answer is an answer to something. Take one from a job opening you are actually pursuing, or use the lesson’s own: tell me about a time when you had to communicate complex technical information to a non-specialist audience.
One to two sentences each, and that is deliberate.
The Situation gives the context and the Task gives your specific responsibility in it. Between them they should take four sentences at the outside. Error 2 is spending the answer here, and it is the one this lesson says candidates who know the method still commit.
This is the answer. The rest is scaffolding.
What you did, step by step, in the first person singular. Three to five sentences minimum, and the majority of the whole answer. Be specific about the steps: not I managed the project carefully but I built a three-week work plan with daily milestones and identified the two critical dependencies. Demonstrate the competency through the actions rather than naming it.
The outcome, then one sentence more.
What happened and how it resolved, quantified where that is genuinely possible. Error 3 is stopping here, or stopping before here. Then one additional sentence: what you learned, or what you would do differently. That line is not padding; it is the one that signals self-awareness.

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 take the other free lessons:

Knowing the method is not the same as using it.

Error 1: ‘we’ instead of ‘I’ throughout the Action. The panel scores your contribution. Describing the team’s actions without specifying your own leaves them nothing to score.

Error 2: Situation and Task are the whole answer. A long, interesting situation, and the candidate never reaches what they personally did.

Error 3: no Result. A detailed Action that trails off: ‘And so that was how I handled it.’ Did it work?

Error 4: generic language throughout the Action. ‘I communicated effectively with all stakeholders.’ Communicated how? Which stakeholders? What were the competing positions?

Error 5: the hypothetical answer. ‘What I would do in that situation is...’ The question asked for a past example, not a theoretical approach.

The STAR method for UN competency interviews: a complete tutorial

Each step’s heading and the paragraph that opens it. I built the lesson to be worked through step by step, so it is above: interactive, and it ends in something you write for your own application.

Knowing the method is not the same as using it.

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 and too thin on Action and Result, which is the failure this lesson is about. These are the five most common ways candidates break the structure: ‘we’ instead of ‘I’, Situation and Task as the whole answer, no Result, generic language in the Action, and the hypothetical answer.

Each part has a length, and the Action is the bulk.

The durations below are the lesson’s, in sentences. They are what the checks in the writing steps count, so they are worth reading before you write rather than after.

The Action should be more than half of the answer, by words.

The lesson asks for the Action to be the majority of the answer, and a majority means more than half: the Situation, Task and Result together must come to fewer words than the Action.

Pick one competency question, and write it down.

A STAR answer is an answer to something. Take one from a job opening you are actually pursuing, or use the lesson’s own: tell me about a time when you had to communicate complex technical information to a non-specialist audience.

One to two sentences each, and that is deliberate.

The Situation gives the context and the Task gives your specific responsibility in it. Between them they should take four sentences at the outside. Error 2 is spending the answer here, and it is the one this lesson says candidates who know the method still commit.

This is the answer. The rest is scaffolding.

What you did, step by step, in the first person singular. Three to five sentences minimum, and the majority of the whole answer. Be specific about the steps: not I managed the project carefully but I built a three-week work plan with daily milestones and identified the two critical dependencies. Demonstrate the competency through the actions rather than naming it.

The outcome, then one sentence more.

What happened and how it resolved, quantified where that is genuinely possible. Error 3 is stopping here, or stopping before here. Then one additional sentence: what you learned, or what you would do differently. That line is not padding; it is the one that signals self-awareness.