WanaData Fellowships 2026: Get a $250 Monthly Stipend to Digitalise Youth Voices in Africa

Captured cycle: This page is retained for historical guidance. Confirm whether the program has reopened before planning an application.

WanaData Fellowships 2026: Get a $250 Monthly Stipend to Digitalise Youth Voices in Africa

Overview in plain language

This opportunity is a six-month fellowship offered through Code for Africa’s WanaData program, focused on youth and digital rights in the Sahel, neighbouring West Africa, and the Horn of Africa. The announcement page says up to 14 fellows can be selected, and each fellow may receive a stipend of USD 250 per month.

The official list calls it a fellowship and stipend opportunity, not a large research grant. That is an important distinction: the programme is best understood as a structured pathway to produce and improve one piece of practical, publicly visible work (or a small cluster of outputs) with mentorship and support from CfA networks.

As of the current official page state, the opportunity is marked [CLOSED] and the submission deadline is listed as 11 January 2026.

At-a-glance (confirmed)

What this fellowship is for (and what it is not)

The program is designed for practitioners already doing or already able to do public-oriented data work. It is not built as broad startup funding, and it is not an unrestricted salary replacement. If your goal is a full-time position, this is probably not it on its own.

From the announcement text, applicants are expected to produce visible outputs while following CfA-style mentoring, training, and reporting expectations. The fellowship is built around improving the quality, reach, and safety of youth-focused digital-content work.

You can think of it this way:

• It is useful if you need both a small stipend and a structured environment to turn an idea into a completed data product.
• It is less useful if you need long-term contract-level income or unrestricted grant money.
• It is most valuable if your work is in youth civic participation, gender inequalities in digital spaces, or human rights-oriented media and data narratives.

What comes with this fellowship

The announcement lists direct support in three buckets:

1. Hands-on data tools and technical training.
2. One-on-one mentorship.
3. Ongoing support from Code for Africa’s communities and academy team.

The practical impact of this support is often understated. Most readers miss that this is not only about funding; it is also a chance to get into a structured reporting ecosystem.

In practice, this can improve three things at once:

• Technical confidence (especially if you have data analysis and storytelling skills but lack advanced workflow support).
• Editorial discipline (how to narrow a project into something publishable in a fixed period).
• Network effects (who you can collaborate with or reach for review, sources, and peer feedback).

Why the “digitalise youth voices” framing matters

The opportunity language is specific: youth voices in Africa, strengthened through public-interest data work. That wording matters because your proposal should avoid making “youth” a vague concept.

A stronger application makes three choices explicit:

• Which youth audiences are central (for example, civic groups, online communities, students, local journalist collectives).
• Which digital barrier or rights concern you are addressing (privacy, misinformation, harassment, civic participation).
• What a successful output would look like in six months.

The listing’s themes (digital rights, gender data, SDG16, human rights, digital mobilisation) signal that the review is likely looking for work that is both technically sound and socially grounded.

Who should apply: eligibility in practical terms

Below is a practical interpretation of each published requirement.

1) WanaData member requirement

The page requires applicants to be registered members of WanaData. If membership is a gate, include proof of that status clearly in your application. If you have no official proof document, include the profile/profile handle and any public proof of prior participation in WanaData activities. Do not leave this implicit.

2) At least one year of experience as data scientist or data storyteller

This is not “any interest in data” experience. The wording explicitly mentions data journalism, media content creation, and similar roles. The safest interpretation is that you should show you can produce and publish evidence-based work with reliability.

3) Portfolio of published work

This is one of the strongest filters in real review cycles. The page says you must have one. If your best argument is “I’m ready to learn,” that may be too late for this kind of call.

A practical way to present this is:

• 3–6 strong published pieces,
• with date, outlet, and the specific role you played,
• and a one-line note on method or impact per item.

4) Region and relevance

The call prioritizes the Sahel, neighbouring West Africa, and the Horn of Africa and notes exceptional applicants elsewhere in Africa may be considered. That means region is a strong tie-breaker.

You should treat region like a criterion, not a background detail. In your proposal, map each key output to the geography:

• Is source data locally grounded?
• Are partners or interviewees region-relevant?
• Is context understanding real, not inferred from desk research?

5) Language and communication capacity

English or French language capability is required, and bilingual is explicitly marked as an advantage. If your project includes community participants and sensitive content, include language strategy explicitly:

• primary publication language,
• translation workflow,
• whether interview language will create interpretation risks.

6) Interest and fit with themes

Thematic alignment is broad but specific in orientation: digital rights, gender, youth civic engagement, cybersecurity, personal data protection, freedom of expression, SDG16. Your concept needs to sit in that frame, not only touch it.

7) Operational commitment

The page requires participation in mentorship, training, and outreach, plus reporting and contribution tracking. This means you should budget time and communication bandwidth. A six-month fellowship without routine updates can quickly look unfit even if the idea is strong.

8) Policy compliance

You must comply with WanaData policies around attribution, privacy, and friendly space guidelines. This is especially relevant for sensitive topics. Build this in early, not as an afterthought.

Who should seriously consider skipping

Use this filter before writing anything:

• You need multi-year funding.
• You cannot share verified published work.
• You are not comfortable writing or producing content in English/French.
• You can only work part-time with irregular availability and cannot sustain reporting commitments for six months.
• You are planning on a broad, continent-wide scope impossible to deliver in one fellowship cycle.

If you fail only one of these and pass the rest, do not automatically disqualify yourself. But if multiple fail, spend time on another opportunity instead.

What to do first: a realistic suitability check

A fast way to judge fit is this simple scoring grid:

If you score 4+ “yes,” it is usually worth the effort. If 2 or fewer, the current time is probably better spent preparing for a different call.

How to prepare as if applications were open

Because this specific call is closed, the same framework helps you prepare for the next cycle or similar programmes.

Step 1: Define one problem that can be solved in six months

Write one sentence: “I will use [dataset/source/tool] to help [specific audience] understand [specific risk or gap] and produce [specific output].”

If this sentence is longer than 25 words, shorten it. If it refers to multiple countries and outcomes, narrow it.

Step 2: Convert goals into deliverables

Choose a main deliverable and one support deliverable.

Example:

• Main deliverable: one data story or explainable analysis.
• Support deliverable: one methodology brief and one cleaned table/dataset note.

This directly maps to your fellowship promise and the reporting requirement noted in the call.

Step 3: Prepare your evidence file

Create a clean “proof pack” before application.

• WanaData membership evidence.
• 3–6 published links with role and method notes.
• CV or one-page bio with date-filtered experience.
• One-page ethics and privacy plan.
• Partner/contact map (if research requires external sources).

Step 4: Draft your ethics and safety plan first

For youth, digital rights, and personal-data themes, this is non-negotiable.

Include:

• what personal data you will collect or process,
• how consent is handled,
• data retention and storage,
• publication-risk check,
• steps to reduce harm.

Do this before methodology details. Safety is often where strong ideas collapse.

Step 5: Build a simple execution calendar

A six-month cycle should have visible checkpoints:

• Month 1: problem validation and dataset confirmation.
• Month 2: first prototype draft.
• Month 3: source review, ethical revision, publishable outline.
• Month 4: analysis/story build and internal review.
• Month 5: final draft and multilingual clarity pass.
• Month 6: final submission and reporting.

Keep this calendar realistic and consistent with your role and workload.

Eligibility vs preparedness (common confusion)

Applicants often mix “I qualify” and “I am ready.” The page’s criteria are eligibility. Readiness is your readiness to execute:

• Eligibility means you satisfy formal conditions.
• Readiness means you can complete work to the standard expected.

For this call, readiness is often the bigger gap. A candidate can satisfy all formal criteria yet fail from weak planning or insufficiently concrete outputs.

Required materials checklist (from published requirements and practical preparation)

The official text points to form submission, eligibility and support expectations. A practical submission pack should include:

• WanaData membership details.
• Portfolio links (not just list of links; include what you did in each project).
• Short statement of 1-year plus experience with examples.
• Project concept with geography and theme fit clearly stated.
• Mentorship/training participation plan (how often, by what mechanism).
• Reporting plan (what you will log, how often, where stored).
• Language and accessibility plan.
• Privacy and friendly-space compliance statement.

If you are missing one piece at first draft, do not hide it. Mention it plainly and describe how you will deliver it, because incomplete honesty is scored more fairly than polished omission.

Application process: what to submit and where

The official page says to complete a Google form link for application. The specific form URL shown in the listing is:

• Application form: https://forms.gle/Rfg1zCPub89u2rF27

Because this specific opportunity is marked closed on the announcement page, the practical action now is to use the structure above for later rounds rather than attempting a late submission.

The stipend reality (practical budgeting)

The announced amount is USD 250 per month for six months. The page does not state payment cadence or reimbursement specifics. To avoid over-committing, use this assumption:

• Total possible payout: USD 1,500 for 6 months.
• Treat the stipend as support for production costs and partial personal support, not full compensation.
• Do not spend expected income on non-recoverable commitments before official confirmation from the programme.

A strong candidate still uses the stipend responsibly: it can help with translation, cloud costs, and specialist support, but it will not normally replace broader living costs.

How reviewers likely separate strong and weak applications

Based on the published criteria and typical fellowship workflows, strong applications usually show:

1. Theme fit (digital rights, gender data, civic engagement) is explicit and specific.
2. A realistic output and timeline.
3. Evidence of published work and method.
4. Clear ethical handling of sensitive data and people.
5. Demonstrated ability to participate in collaboration and reporting.

Weak submissions usually fail by having:

1. Overbroad goals.
2. No local grounding.
3. Portfolio claims with no public links.
4. Vague ethics treatment.
5. No realistic time budget.

Common mistakes people make with this kind of fellowship and how to avoid each

Mistake: Treating the call like open-ended grant funding

If your concept is “transform digital participation on the whole continent,” it will look unrealistic.

Avoidance

Pick one geography, one population, one output.

Mistake: Thinking stipend implies large operational budget

You can budget modestly for research and communication, but not large teams.

Avoidance

Map expenses to six-month reality and list priorities before writing anything else.

Mistake: Weak explanation of methods

People often say “I will clean data and create visualizations” without saying where the data comes from, how it is verified, and what is excluded.

Avoidance

Use short method fields: source, validation, cleaning, analytical approach, limitations.

Mistake: Ignoring reporting and mentorship commitment

The criteria explicitly mention tracking contributions and reports.

Avoidance

Include a reporting cadence in the proposal itself, even if it feels repetitive.

Mistake: Language mismatch

Many good ideas fail because they are written at the wrong audience level.

Avoidance

Write one paragraph for technical reviewers and one for non-technical readers in your draft, then merge.

FAQs (confirmed where confirmed)

Is this opportunity still open?

The official page currently shows the call as closed.

What is the exact deadline?

11 January 2026.

How much is the stipend?

USD 250 per month for six months.

How many fellows are possible?

The listing says up to 14 fellows.

Is this for people only in the Sahel and Horn of Africa?

Priority is specifically stated for the Sahel region, neighbouring West Africa, and the Horn of Africa, with exceptional applicants elsewhere in Africa possibly considered.

Do I need a portfolio?

Yes. The published requirements include a portfolio of published work.

What can I include about language?

English or French, with bilingual ability noted as a plus.

What is included beyond stipend?

Hands-on data tools and technical training, one-on-one mentorship, and ongoing support from CfA communities and academy teams.

Are all themes mandatory?

No. The themes are the broad focus zone; your proposal should connect clearly to them.

What should I do now that this round is closed?

Use this same structure for future calls and strengthen your portfolio, reporting habits, and ethics documentation.

Official links and documentation status

• Official opportunity page (current source link): https://opportunities.codeforafrica.org/2025/12/09/wanadata-fellowships-digitalise-youth-voices-in-africa/
• Official form link referenced by the page: https://forms.gle/Rfg1zCPub89u2rF27

The opportunity appears as closed, so treat submission status and timing as historical until a new official WanaData announcement appears.

After this round: practical next steps

If you planned to apply and missed this one, your next move should be deliberate:

1. Keep your portfolio up to date with short, published, high-quality work.
2. Build a short ethics template for all youth/digital-rights projects.
3. Turn your concept into one concise deliverable with a timeline.
4. Keep a weekly progress log so reporting is easy in future applications.
5. Revisit Code for Africa opportunities pages regularly for follow-up WanaData cycles.

This call’s value lies in its signal: practical, region-rooted, ethically aware data storytelling with mentorship and support. If you match that profile, the next time a similar opportunity opens, your preparation above will save time and increase your odds.