The role of a Software Engineer at the United Nations is pivotal in the organization’s mission to leverage technology for global development and humanitarian efforts. As a Software Engineer, you will be involved in designing, developing, and maintaining software solutions that support various UN initiatives. This position not only impacts internal efficiency but also enhances the delivery of critical services to member states, NGOs, and the public. Your contributions will directly affect how the UN harnesses technology to address global challenges, making your work both meaningful and influential. In this role, you will engage with cross-functional teams to create scalable and effective solutions that meet the complex requirements of international projects. You will work on various software applications, databases, and systems that facilitate data-driven decision-making and operational efficiency. The challenges you encounter will range from integrating disparate systems to ensuring data security and compliance with international standards. This role is critical as it drives the UN's commitment to innovation and excellence in service delivery, providing you with a unique opportunity to make a significant impact on a global scale.
Application Review
reportedInitial review of candidate applications to assess qualifications and fit.
What to demonstrate
- Initial review of candidate applications to assess qualifications and fit
- Depth in Competency-based interviewing
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Written Assessment
reportedCandidates complete a written assessment to evaluate their technical skills.
What to demonstrate
- Candidates complete a written assessment to evaluate their technical skills
- Depth in Competency-based interviewing
How to prepare
- Answer aloud and timed: Explain your experience with database management systems and how you optimize queries.
- Answer aloud and timed: How do you ensure code quality and maintainability in your projects?
Panel Interviews
reportedCandidates engage with a panel of interviewers focusing on various skills and experiences.
What to demonstrate
- Candidates engage with a panel of interviewers focusing on various skills and experiences
- Depth in Competency-based interviewing
How to prepare
- Answer aloud and timed: Can you discuss a time when you implemented a new technology or tool in your work?
- Answer aloud and timed: Describe a situation where you had to work under pressure. How did you handle it?
PracHub editorial advice for the preparation topics above.
Align with UN values
Ensure that your responses reflect the core values of the United Nations, emphasizing collaboration and service.
Prepare for behavioral questions
Use the STAR method (Situation, Task, Action, Result) to structure your answers to behavioral questions.
Research the organization
Familiarize yourself with the UN's mission, recent initiatives, and challenges in the tech landscape to demonstrate your genuine interest.
Practice technical skills
Engage in coding exercises, system design discussions, and technical problem-solving to enhance your confidence.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Can you explain a sorting algorithm and its time complexity?
Can you explain a sorting algorithm and its time complexity?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Write a function that reverses a string.
Write a function that reverses a string.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you implement a search algorithm to find an element in a sorted array?
How would you implement a search algorithm to find an element in a sorted array?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain the differences between stack and queue data structures.
Explain the differences between stack and queue data structures.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
Find version gaps and relay lag with window functions
outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.
Approach
- Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
- Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
- Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
- Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.
Follow-up
- Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
- Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?
What programming languages are you proficient in, and how have you used them in past projects?
What programming languages are you proficient in, and how have you used them in past projects?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a challenging technical problem you faced and how you resolved it.
Describe a challenging technical problem you faced and how you resolved it.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you ensure code quality and maintainability in your projects?
How do you ensure code quality and maintainability in your projects?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
You are given a project with a tight deadline and limited resources. How would you approach this?
You are given a project with a tight deadline and limited resources. How would you approach this?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a scenario where you had to analyze a large dataset. What tools did you use?
Describe a scenario where you had to analyze a large dataset. What tools did you use?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you design a system to handle an increase in data traffic?
How would you design a system to handle an increase in data traffic?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
If faced with a significant bug in a production environment, what steps would you take to resolve it?
If faced with a significant bug in a production environment, what steps would you take to resolve it?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Discuss a time you had to make a decision without complete information.
Discuss a time you had to make a decision without complete information.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you approach debugging a piece of code?
How do you approach debugging a piece of code?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics United Nations candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the United Nations loop
- Write out the reported sequence: Application Review, Written Assessment, Panel Interviews.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 3 reported rounds, with the weakest marked.
02Work Competency-based interviewing
- Spend the session on Competency-based interviewing, which United Nations candidates report being tested on.
- Write one worked example in Competency-based interviewing and time yourself on it.
Deliverable: One timed worked example in Competency-based interviewing.
03Work Behavioral interview questions
- Spend the session on Behavioral interview questions, which United Nations candidates report being tested on.
- Write one worked example in Behavioral interview questions and time yourself on it.
Deliverable: One timed worked example in Behavioral interview questions.
04Work Technical interviewing (theoretical + practical)
- Spend the session on Technical interviewing (theoretical + practical), which United Nations candidates report being tested on.
- Write one worked example in Technical interviewing (theoretical + practical) and time yourself on it.
Deliverable: One timed worked example in Technical interviewing (theoretical + practical).
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: What programming languages are you proficient in, and how have you used them in past projects?
- Answer aloud, timed: Describe a challenging technical problem you faced and how you resolved it.
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: Behavioral / Leadership
- Answer aloud, timed: Describe a situation where you had to work under pressure. How did you handle it?
- Answer aloud, timed: How do you prioritize tasks when faced with multiple deadlines?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.
07Answer out loud: Problem-Solving / Case Studies
- Answer aloud, timed: You are given a project with a tight deadline and limited resources. How would you approach this?
- Answer aloud, timed: Describe a scenario where you had to analyze a large dataset. What tools did you use?
Deliverable: Spoken answers to 2 reported Problem-Solving / Case Studies question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Explain your experience with database management systems and how you optimize queries.
Explain your experience with database management systems and how you optimize queries.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Can you discuss a time when you implemented a new technology or tool in your work?
Can you discuss a time when you implemented a new technology or tool in your work?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Describe a situation where you had to work under pressure. How did you handle it?
Describe a situation where you had to work under pressure. How did you handle it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize tasks when faced with multiple deadlines?
How do you prioritize tasks when faced with multiple deadlines?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Can you provide an example of how you contributed to a team project?
Can you provide an example of how you contributed to a team project?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle conflicts within a team?
How do you handle conflicts within a team?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What motivates you to perform well in your job?
What motivates you to perform well in your job?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Explain your experience with database management systems and how you optimize queries.
- 02
Can you discuss a time when you implemented a new technology or tool in your work?
- 03
Describe a situation where you had to work under pressure. How did you handle it?
- 04
How do you prioritize tasks when faced with multiple deadlines?
How difficult are the interviews, and how much preparation time is typical?
The interviews can be moderately challenging, requiring a good understanding of technical concepts and behavioral assessments. Candidates typically spend several weeks preparing, focusing on both technical skills and cultural fit.
United Nations Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates demonstrate strong technical knowledge, effective communication skills, and a clear alignment with the UN's values of collaboration, integrity, and service.
United Nations Software Engineer candidate reports ↗What is the culture and working style at the United Nations?
The culture is collaborative and mission-driven, with a strong emphasis on teamwork and inclusivity. Employees are encouraged to be proactive in problem-solving and to contribute to the organization's goals.
United Nations Software Engineer candidate reports ↗What is the typical timeline from initial screen to offer?
The timeline can vary significantly based on the role and location, but candidates may expect anywhere from a few weeks to several months from application to offer.
United Nations Software Engineer candidate reports ↗Are there remote work or hybrid expectations?
While many positions may offer flexibility, specific arrangements will depend on the role and organizational policies. It's advisable to inquire during the interview process.
United Nations Software Engineer candidate reports ↗What topics does United Nations test in interviews?
United Nations interviews most often cover Problem Solving, Competency-based interviewing, Communication Skills, Behavioral Interviewing, and Analytical thinking. The exact emphasis depends on the specific role you apply for.
United Nations Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01United Nations Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.