How to Write a Developer CV for Rwanda (With What Employers Actually Want)

We need to start with what matters, not what you think matters. Rwandan tech employers scanning developer CVs are looking for three things:

Evidence that you can build things. Not a list of technologies. Not a certificate from an online course. Links to deployed, working projects. A GitHub profile with real code. If an employer clicks your portfolio link and sees a live application, you are already ahead of most applicants.

Relevant technical skills. For most Kigali companies: JavaScript, React, Node.js, Python, databases, and deployment. For fintech roles: MoMo API and Airtel Money integration experience. For government and enterprise roles: formal credentials may carry more weight. Match your skills to the job posting.

Communication ability. Your CV itself is a communication test. If it is messy, disorganized, full of typos, or hard to scan, the employer assumes your code will be too. Write clearly. Format cleanly. Proofread everything.

What they are not looking for: a three-page life story, a photo (optional in Rwanda, not required), a list of hobbies, or an objective statement that says "seeking a challenging position in a dynamic company." Every CV says that. None of them should.

Here is the structure, in order of importance:

1. Header. Name, phone number, email, location (Kigali or your city), GitHub URL, portfolio URL, LinkedIn URL. No photo unless the job posting asks for one. No date of birth, marital status, or religion. These are irrelevant to a tech role.

2. Summary (two to three sentences maximum). Replace the objective statement with a brief description of what you do. Example: "Full-stack developer with experience building web applications using React and Node.js. Built payment integrations with MTN MoMo for two e-commerce projects. Based in Kigali." That tells the employer more than any objective statement.

3. Projects (most important section for juniors). List two to four projects with:

• Project name and one-sentence description
• Technologies used
• Live URL (if deployed)
• GitHub repository link
• One or two bullet points describing what you built and any notable features

4. Work experience. If you have professional experience, list it with concrete achievements. "Built the MoMo payment integration that processed 500 transactions in the first month" beats "Responsible for payment development." If you have no professional experience, your projects section carries the weight. Do not pad this section with irrelevant jobs unless they show transferable skills.

5. Skills. List only technologies you can discuss in an interview. Group them: Languages (JavaScript, Python, TypeScript), Frameworks (React, Node.js, Express), Databases (PostgreSQL, MongoDB), Tools (Git, Docker, AWS), APIs (MTN MoMo, Airtel Money). Do not list "Microsoft Word" on a developer CV.

6. Education and certifications. Degree, bootcamp, or relevant certifications. List them, but do not expect them to carry your application. The projects do that.

If you have never been paid to write code, your CV needs to compensate with evidence of ability. Here is how.

Make your Projects section the star. Move it above Work Experience. Give each project real detail. A project you built for a class, a bootcamp, or yourself counts. What matters is that it is deployed and the code is on GitHub. See our guide to getting your first tech job with no experience for portfolio strategy.

Include freelance work, even if small. Did you build a website for a friend's business? Set up a WordPress site for a family member? Create a simple tool for a local shop? That is client work. List it with the same detail as any project.

Include relevant bootcamp or course completion. Completing a structured program shows commitment. List the program, what you learned, and any capstone project.

Open source contributions count. Even small pull requests to open source projects show you can read existing code, follow contribution guidelines, and collaborate. If you have contributed to any project on GitHub, list it.

Do not fabricate experience. The Kigali tech community is small. If you claim to have worked somewhere you did not, it will surface. Honesty about your level, combined with strong project work, is always the better strategy.

No portfolio link. If an employer cannot see your work, your CV is just a list of claims. Always include a link to deployed projects or your GitHub profile. This is the single most common mistake we see from Rwandan junior developers.

Listing every technology you have touched. A CV that lists 25 technologies suggests you are a beginner in all of them. List only technologies you can confidently discuss in an interview. Five technologies with evidence beats 25 without.

Generic CV for every application. If you are applying for a fintech role, your MoMo integration project should be at the top. If you are applying for a front-end role, your React project should lead. Spend five minutes tailoring each CV to the specific job. It makes a noticeable difference.

Walls of text. Hiring managers scan CVs. They do not read them word by word. Use bullet points, clear headings, and white space. If your CV looks like an essay, reformat it.

Typos and broken links. A developer CV with broken portfolio links is particularly bad. Test every URL before you submit. Have someone else proofread your CV. Errors signal carelessness.

Including irrelevant personal information. Your date of birth, marital status, number of children, and national ID number do not belong on a tech CV. Some Rwandan CV templates include these by default. Remove them. They waste space and are not relevant to your ability to write code.

This deserves its own section because it is the single most underrated differentiator for developers applying to Rwandan companies.

Most junior developers in Rwanda learn to code from Western tutorials that teach Stripe integration. Very few have hands-on experience with the MTN MoMo API or Airtel Money API. If you have built a project that integrates mobile money payments, even in sandbox mode, you have a skill that most of your competition lacks.

How to present it on your CV:

• In your summary: "...with hands-on MoMo payment integration experience"
• In your projects: a dedicated project showing a payment flow with MoMo (link to live demo or sandbox)
• In your skills: "APIs: MTN MoMo, Airtel Money, IntouchPay" (list only what you have actually used)

If you do not have this skill yet, it is worth investing time to learn. McTaba's mobile money integration course (approximately RWF 100,000) covers MoMo and Airtel Money API patterns. Building one payment integration project for your portfolio can meaningfully improve your job prospects in Rwanda.

Your CV gets you the interview. It does not get you the job. And in Kigali's small tech community, many jobs are filled before a CV is even reviewed.

Your GitHub profile is your second CV. Make sure your pinned repositories are your best work. Write clear READMEs. Green squares on your contribution graph show consistency. Employers check GitHub. Make it worth checking.

Networking fills roles before job boards do. Show up at kLab. Attend tech events at Norrsken House. Join developer communities on WhatsApp and Twitter/X. When a company needs a developer and someone in the community recommends you, your CV becomes a formality, not a filter.

LinkedIn matters in Rwanda. Many Kigali tech companies recruit through LinkedIn. Keep your profile updated, post about projects you are building, and connect with people in the local tech scene. Your LinkedIn profile should mirror your CV: portfolio links, project descriptions, and specific skills.

The CV is necessary. But it is one piece of a larger strategy. For the full picture on job searching in Rwanda, see our guides on tech jobs in Kigali and getting your first job with no experience.