How to prepare for a United Nations competency-based interview

What "competency-based" means

Instead of hypothetical questions, you will be asked to describe real situations from your past: "Tell me about a time when you had to deliver under a tight deadline." A panel scores your answer against a defined competency, so the substance and structure of your example matter more than how confident you sound.

The UN competency framework

Questions map to the organization’s competency framework, which typically has three layers:

• Core values: integrity, professionalism, and respect for diversity.
• Core competencies: communication, teamwork, planning and organizing, accountability, client orientation, creativity, and technological awareness.
• Managerial competencies (for supervisory roles): leadership, vision, empowering others, managing performance, building trust, and judgement and decision-making.

Use the STAR method

Structure every example around four parts: the Situation you faced, the Task you were responsible for, the Action you personally took, and the Result you achieved. Spend most of your answer on the action and quantify the result wherever you can. Say "I", not "we", so the panel can see your individual contribution.

Prepare your examples in advance

Read the competencies listed in the vacancy, then prepare one or two concrete examples for each. Reuse strong examples across competencies where they fit. Have at least one example ready for integrity or ethics and one for working across cultures, because these come up often and catch unprepared candidates out.

Logistics to expect

Interviews are usually conducted by a panel, often over video, and may be preceded by a written test or technical assessment. Some processes record the interview. Treat a video interview with the same preparation and setup, quiet room, stable connection, as an in-person one.

Common mistakes

• Giving vague or hypothetical answers instead of a specific past example.
• Saying "we" throughout, so your own contribution is invisible.
• Not quantifying the result.
• Running out of prepared examples for values and diversity competencies.

A fully worked STAR answer

It helps to see the method applied end to end rather than described. Take a common UN competency, planning and organising, and a question such as, tell us about a time you had to deliver under a tight deadline with limited resources. A strong answer stays tightly structured and keeps you as the clear actor throughout. Notice how each part does a specific job, and how the result is concrete without inventing precise figures you cannot back up.

Situation: our team had to produce a briefing pack for a senior visit, and a colleague fell ill three days before the deadline. Task: I was responsible for delivering the full pack on time without dropping quality. Action: I mapped the outstanding sections, ranked them by what the principal actually needed first, reassigned two lighter items to a willing colleague, kept the rest myself, and set a short daily check-in so blockers surfaced early. Result: the pack was delivered the evening before the visit, the meeting ran on the briefed points, and my manager later asked me to document the triage approach for the team to reuse.

Evidencing several competencies from one story

Good prepared stories are versatile. The same well-chosen example can be retold to evidence different competencies, because what changes is the emphasis, not the facts. This is why preparing a small bank of rich situations beats memorising a separate script for every competency on the framework. Build perhaps six to eight strong stories from real experience, each detailed enough to be steered in more than one direction.

Using the briefing-pack example above, you can foreground different skills depending on what the question asks. The trick is to lead with the part of the action that matches the competency in the question, and trim the rest, rather than telling the whole story the same way every time.

• Planning and organising: stress the mapping, prioritising, and the daily check-in that kept delivery on track.
• Teamwork: stress how you brought in a colleague, shared the load fairly, and kept everyone informed.
• Client orientation: stress how you worked back from what the principal needed and protected the meeting outcome.
• Communication: stress how the check-ins surfaced blockers early and kept everyone aligned under pressure.

Handling virtual and panel logistics

Many UN interviews now run online and in front of a panel, and the format itself can help or hurt you before you have answered a single question. Treat the setup as part of your preparation. Test your connection, camera, and microphone in advance, sit somewhere quiet with a plain background and decent light on your face, and have a charged backup such as a phone hotspot ready in case the main link drops. Keep a printed copy of the vacancy and a short list of your prepared stories nearby, but do not read from a script: panels can hear it instantly.

On a panel, expect several interviewers who often take turns and read questions from a common script while they write notes. Short silences while they type are normal, so do not rush to fill them or assume you answered badly. Greet the panel, then make eye contact with the camera as you speak rather than staring at your own image, and address your answer to whoever asked while occasionally including the others. If a question is unclear, it is fine to ask for it to be repeated rather than guessing.

• Join a few minutes early, with your full name displayed and notifications silenced.
• Position the camera at eye level and look into the lens for the points that matter most.
• Note the competency in each question so your answer lands on what they are scoring.
• Keep water within reach, and have the panel's or coordinator's contact ready in case you are disconnected.

The mistakes that sink strong candidates

Most failed competency interviews are not failed on knowledge. They are lost on habits that are easy to fix once you know to watch for them. The single most common error is talking about what we did, so the panel never learns what you personally contributed. Competency interviews score the individual, so own your actions and use I where it is honest to do so.

The other frequent traps are length and relevance. Answers that wander lose the panel, and answers with no clear result leave nothing to score. Keep each response focused, finish with the outcome, and make sure the example actually matches the competency in the question rather than a story you simply wanted to tell.

• Hiding your role behind we, so your individual contribution stays invisible.
• Rambling without structure, or stopping before you reach the result.
• Using a hypothetical instead of something you genuinely did, which panels probe and quickly expose.
• Bringing only one example and reusing it for everything, so later answers feel thin.
• Criticising former colleagues or managers, which reads as a teamwork and judgement risk.
• Skipping your own questions at the end, which can read as low interest in the role.