How to Write a Developer CV That Gets Interviews in Uganda

Your developer CV should follow this structure, in this order:

1. Contact information. Name, email, phone, LinkedIn, GitHub link, portfolio link. No photo (it adds bias and takes up space). No date of birth, marital status, or religion. These are irrelevant to your ability to write code and some Ugandan CVs include them unnecessarily.

2. Technical skills. A clean list of languages, frameworks, tools, and platforms you actually know. Be honest. If you list "Python" but cannot write a function without looking up syntax, remove it. Group by category: Languages, Frameworks, Databases, Tools, Cloud/DevOps.

3. Projects (if you lack work experience) or Work Experience (if you have it). For each entry, describe what you built, what technologies you used, and what the result was. Use numbers where possible. "Built a full-stack booking system with MTN MoMo payments (React, Node.js, PostgreSQL)" is better than "Worked on web development projects."

4. Education. Degree, institution, year. If you completed a bootcamp or relevant course (Refactory, McTaba, freeCodeCamp), include it here.

5. Certifications (if relevant). AWS, Google Cloud, or other recognized certifications. Do not pad this section with irrelevant certificates.

Too long. Three, four, five pages. No. One to two pages. If you have less than five years of experience, one page is ideal. Hiring managers scanning 50 CVs will not read your four-page document.

Generic objective statement. "I am a passionate and dedicated software developer seeking a challenging role..." This tells the hiring manager nothing. Either replace it with a two-sentence summary of your specific skills, or remove it entirely.

Listing duties instead of achievements. "Responsible for front-end development" tells me nothing about what you actually built. "Built a customer dashboard in React that reduced support tickets by 30%" tells me exactly what you did and why it mattered.

Including irrelevant personal details. Your marital status, number of children, religion, and national ID number do not belong on a developer CV. Some Ugandan employers still expect these, but tech companies generally do not, and including them marks your CV as non-technical.

No links. A developer CV without a GitHub link or portfolio URL is incomplete. This is where hiring managers go to verify your claims. If your GitHub is empty, fill it before sending your CV.

Listing technologies you barely know. If you completed one tutorial in Go, do not list Go as a skill. Interviewers will ask about anything on your CV, and being caught out on a listed skill damages your credibility for everything else.

Highlight mobile money skills. If you have experience with MTN MoMo API, Airtel Money API, or any mobile money integration, put it prominently in your skills section and describe the project in detail. This skill is in high demand and short supply in Uganda.

Mention local context. If you built something for the Ugandan market (a school fees payment system, a boda-boda booking app, an agricultural marketplace), say so. It shows you understand the local market, which matters to Ugandan employers.

Tailor for the employer type. If you are applying to MTN Uganda or a bank, a slightly more formal CV with your degree prominently placed works well. If you are applying to a startup or remote company, lead with your projects and skills. Different employers value different signals.

For remote roles, emphasize communication. Add a line about your experience with remote collaboration (Git workflows, async communication, English proficiency). Remote employers need to know you can communicate clearly across time zones.

For developer roles, your CV gets you considered. Your portfolio gets you interviewed. Every hiring manager worth their title will click your GitHub link and portfolio URL.

What they want to see:

• Clean, readable code with meaningful commit messages
• README files that explain what the project does and how to run it
• Deployed, working applications they can interact with
• Projects that solve real problems, not just tutorial clones
• Consistent activity (not just a burst of commits three months ago)

If your portfolio is weak, strengthening it is a better investment than polishing your CV. The McTaba Full-Stack course (approximately UGX 3,400,000) produces portfolio-ready projects with payment integration that stand out to Ugandan employers.