Career Tips · 16 Nov 2026 · 7 min read

The Written Test Uganda NGOs Use Before They’ll Interview You

Most NGO applicants in Uganda never reach the panel. They lose at the written stage. Here’s how the concept note and log frame tests actually work.

By Career Tips
The Written Test Uganda NGOs Use Before They’ll Interview You

A programme officer candidate in Kampala once told a recruiter she’d “prepared for weeks” for an NGO interview. She meant the panel. She hadn’t heard there was a written test first: a 72-hour concept note exercise that arrived by email the Friday before, due Monday at 5pm. She opened it on Sunday night. She never heard back.

That story repeats itself across Uganda’s development sector every month. Candidates pour their preparation into the wrong stage. They rehearse “tell me about yourself” while the organisation has already quietly eliminated most of the shortlist through a written assignment nobody warned them to expect.

If you’ve applied to UNICEF, WFP, IRC, GIZ, World Vision, CARE International, Mercy Corps, or Save the Children in Uganda and gone quiet after submission, there’s a real chance you were tested on paper and scored out before anyone considered calling you in. This is the stage that decides who gets a panel seat. Here’s how to actually pass it.

Why the panel is often the easy part

Uganda hosts the largest refugee population in Africa, concentrated in West Nile, Kiryandongo, and the south-west, and that has built a development sector large enough to run its hiring like a formal profession rather than a favour economy. Programme-facing roles, and increasingly MEAL, grants, and even some HR and finance positions, are shortlisted on paper, then tested on paper again before anyone picks up a phone.

The written stage exists because a panel interview is expensive to run and easy to perform well in with a rehearsed answer. A concept note or budget exercise is harder to fake. It shows, in roughly two hours of actual thinking, whether you can structure a problem the way the job requires. Organisations score it against a rubric built before your document lands in their inbox, and a weak score there is difficult to recover from in the room, even with a strong panel performance.

The three forms this test usually takes

Not every written assessment looks the same. Know which one you’re facing before you start typing.

  • The concept note. You get a problem statement — a displacement crisis in Adjumani, a nutrition gap in Karamoja, a WASH failure in a refugee settlement — and two to four pages to propose an intervention. This tests programme design logic, not creativity.
  • The log frame or results-framework exercise. You’re handed a partially completed table and asked to fill in missing outputs, outcomes, or indicators, or to spot where the logic breaks. This tests whether you actually understand cause and effect in programme design, not just the vocabulary.
  • The budget narrative review. Common for finance, grants, and operations roles. You’re given a draft budget with errors or unexplained line items and asked to flag and justify corrections. This tests compliance instinct, not arithmetic.

Most vacancy notices don’t say which one is coming, or that one is coming at all. If the recruiter calls to schedule “the next stage,” ask directly: “Is there a written exercise before the panel, and roughly how long will I have?” Most will tell you. Almost no other candidate asks.

What a concept note actually needs to contain

The single most common failure isn’t bad writing. It’s skipping the logic chain. A concept note that scores well always makes these connections explicit, in roughly this order:

  1. Problem statement with a number in it. Not “WASH access is poor in the settlement” but “only 38% of households in the settlement have access to a water point within 500 metres, against the Sphere minimum standard.” A reviewer scoring forty submissions notices the one with a figure.
  2. A stated target population, with rough size, not “vulnerable communities.”
  3. Objectives that map directly to the problem, not generic development language lifted from another proposal.
  4. Activities that produce the stated outputs, written as verbs with a responsible actor attached.
  5. One acknowledged risk or assumption. Reviewers read this as evidence you’ve actually designed programmes before, rather than described one in theory.

Here’s the gap in practice. A weak sentence: “The project will improve livelihoods for affected communities through training and support.” A sentence that scores: “120 households will receive a four-month agribusiness training cycle, followed by a start-up grant of UGX 400,000 disbursed in two tranches tied to attendance.” Same idea. One of them tells a scorer you’ve done this before.

The log frame trap almost everyone falls into

Candidates confuse levels constantly, and reviewers are specifically trained to catch it. An output is something your project directly delivers and controls: “200 teachers trained.” An outcome is the behaviour change that follows, which you influence but don’t fully control: “teachers apply the new curriculum in class.” An impact is the long-term change you contribute to alongside many other actors: “improved literacy rates in the district.”

The test almost always plants at least one deliberately mismatched row, an “output” that’s actually phrased as an impact, or an indicator that can’t realistically be measured within the project timeline. Finding it and fixing it, briefly, is worth more than filling every blank cell.

Timing discipline matters more than polish

Most written tests arrive with a 48 to 72-hour window, sometimes shorter. The candidates who score well don’t write faster. They plan before they write. A workable split for a 72-hour window: roughly four hours reading the brief and sketching the logic on paper, four hours drafting, two hours cutting it down and checking against the stated word or page limit.

That last part is not optional. Submissions that run over a stated two-page limit are frequently scored down or disqualified before a reviewer reads the content, because following a page limit is itself part of what the role requires. If the brief says two pages, two pages means two, not two and a half with smaller margins.

How the scoring actually works against you

Development organisations use rubric scoring with weighted categories: typically problem analysis, logical coherence, feasibility, and compliance with instructions, each marked out of a fixed scale. Your score on this stage is often combined with the panel score at a fixed ratio, sometimes 40/60, sometimes closer to even. A strong panel interview cannot fully erase a weak written score, because the rubric is designed precisely to stop personality and interview charm from overriding demonstrated analytical capability.

This is why some candidates who interview brilliantly still don’t get the offer, and some quieter candidates with sharp written logic do. If you know you interview well but write under pressure less confidently, budget extra rehearsal time specifically for the written stage, not the panel.

Three mistakes that cost scores no matter which test you get

Reviewers who sit through dozens of these submissions in a single week report the same patterns, over and over, regardless of whether the exercise is a concept note, a log frame, or a budget review.

  • Copying language straight from the vacancy notice. Restating “the project aims to strengthen community resilience” back at the organisation that wrote those words tells a scorer nothing except that you can paste. Replace every borrowed phrase with your own, more specific version.
  • Ignoring the stated format entirely. If the brief asks for a table and you submit prose, or asks for Arial 11 and you submit something else, that’s treated as a signal about how you’ll handle donor reporting templates later, not a cosmetic slip.
  • Writing for a general reader instead of the reviewer in front of you. A budget narrative for a finance manager should read differently from a concept note for a programme director. Candidates who submit the same tone and depth to every organisation usually show it, and reviewers who read sector-wide submissions can tell.

None of these take extra time to fix. They take a second pass through the brief with a different question in mind: not “did I answer this,” but “would the specific person reading this recognise that I understood what they actually asked for.”

If you get short notice

Sometimes the window is 24 hours, not 72. In that case, resist the instinct to write immediately. Spend the first thirty minutes outlining the logic chain on a blank page: problem, population, objective, output, one risk. Everything else is filling in sentences around a structure you’ve already decided. Candidates who start typing from the first paragraph without that structure tend to produce text that drifts, and drift is exactly what a rubric scorer is trained to penalise.

Once you clear the written stage, the panel that follows runs on a different logic entirely: competency questions, STAR-method answers, and a much heavier emphasis on safeguarding and sector knowledge. What the NGO panel interview actually tests covers that stage in full once you’re through the door.

Before you submit anything

Read the brief twice before you open a blank document. The second read almost always reveals an instruction missed on the first pass, a specific donor framing, a named district, a required format. Build your CV and LinkedIn profile to reflect the same precision the written test is scoring for; a LinkedIn profile written for Uganda’s job market walks through making your profile match the specificity sector recruiters already expect from you on paper.

And once an offer is on the table, remember that NGO salary bands are fixed by the grant that funds the role, so the real negotiation often sits in benefits rather than base pay. What’s actually in a Uganda salary package beyond the number explains where that room usually is.

Programme vacancies are posted daily on ReliefWeb, and Uganda’s formal development-sector employment has grown steadily over the past decade according to data from the Uganda Bureau of Statistics. Whatever the contract terms, pension contributions still run through NSSF Uganda the same way they would in any formal-sector job. The written test is simply the first place that growth gets rationed. Treat it that way, and you give yourself an actual shot at the panel.

Browse current NGO, programme, and development-sector vacancies at Kampala Index.

Know someone job hunting? Send them this.

More Stories