How to Write a Developer CV That Gets Interviews in Tanzania

Before building the right CV, here is what to avoid. These are patterns we see repeatedly in Tanzanian developer applications:

• Too long. Many Tanzanian CVs run 4 to 6 pages, listing every course, certificate, and secondary school attended. For developer roles, 1 to 2 pages is the target. Hiring managers spend 30 to 60 seconds on initial screening. Every extra page reduces the chance they see the important parts.
• No portfolio links. A developer CV without links to deployed projects and GitHub is like a photographer's resume without photos. If you cannot show your work, you are at a massive disadvantage.
• Generic descriptions. "Responsible for developing software solutions" tells an employer nothing. Replace with specifics: "Built a payment integration handling M-Pesa and Tigo Pesa transactions for 200+ daily users."
• Irrelevant personal details. Photo, marital status, religion, tribe, and date of birth are common on Tanzanian CVs but irrelevant for developer roles and may introduce unconscious bias. Leave them out.
• Listing every technology you have ever touched. If you did one HTML tutorial three years ago, do not list HTML as a skill. Only include technologies you can confidently use in a technical interview or on the job.

A format that works for both startup and corporate applications in Tanzania:

1. Header (2 lines). Full name, email, phone, LinkedIn URL, GitHub URL, portfolio website (if you have one). That is it. No address, no photo.

2. Skills section (3 to 5 lines). Group by category: Languages (JavaScript, TypeScript, Python), Frameworks (React, Node.js, Django), Databases (PostgreSQL, MongoDB), Tools (Git, Docker, AWS), Integrations (M-Pesa, Tigo Pesa, Selcom API). This section should be scannable in 10 seconds.

3. Portfolio projects (half a page to one page). List 3 to 4 projects, each with: project name, one-line description, tech stack used, live URL, and GitHub link. Prioritize projects that demonstrate Tanzanian market relevance (mobile money integration, local problem-solving). If you built it during a course, say so honestly. It still counts.

4. Work experience (if any). For each role: company name, your title, dates, and 2 to 3 bullet points describing what you built and the impact. Use numbers: "Developed payment module processing TZS 50M+ monthly" is better than "Worked on payment system." If you have no professional experience, skip this section and expand the portfolio section.

5. Education (2 to 3 lines). Degree and institution. If you attended UDSM, NM-AIST, or another recognized institution, include it. If you completed a bootcamp or structured course, list it. Keep this brief.

6. Certifications (optional, 1 to 2 lines). Only include certifications that are relevant and recognized: AWS certification, Google Cloud, or completion of a reputable training program. Do not list Udemy completion badges.

The same CV should not go to every employer. Customize for the target:

For banks (NMB, CRDB, Stanbic): Lead with your degree. Banks have formal HR processes that screen for educational credentials. Highlight Java, Oracle, SQL skills. Mention any experience with financial systems, transaction processing, or data security. Use formal language. Include any banking or fintech certifications.

For telecoms (Vodacom, Airtel, Tigo): Lead with relevant technical skills: mobile money APIs, USSD development, mobile app development, and data analytics. A degree from UDSM or NM-AIST helps. Mention any experience with high-volume systems, API design, or payment processing.

For startups (Nala, Selcom, Ramani, agencies): Lead with your portfolio and GitHub. Startups care about what you have built and shipped. Highlight modern stacks (React, Node.js, TypeScript, Flutter, cloud platforms). Show that you can learn quickly and work independently. A degree is less important here; demonstrated capability is everything.

For remote international roles: Lead with portfolio and GitHub, same as startups. Emphasize English communication skills, experience with async collaboration tools (Slack, Jira, GitHub), and any previous remote work experience. If you have contributed to open source, feature it prominently.

Your portfolio projects are the most important part of your application. Tips for maximizing their impact:

• Deploy everything. A project running on your laptop does not count. Deploy to Vercel, Railway, Render, or any free hosting platform. Include the live URL on your CV.
• Write a proper README. Each GitHub repo should have a README that explains what the project does, which technologies you used, how to run it locally, and screenshots. This takes 30 minutes and dramatically improves how your work is perceived.
• Include a mobile money project. If you have integrated M-Pesa, Tigo Pesa, or Airtel Money (even using sandbox/test credentials), feature it first. This is the single strongest signal you can send to Tanzanian employers.
• Make projects look professional. A project with decent UI, proper error handling, and responsive design suggests you care about quality. Ugly or broken projects hurt more than they help.
• Show commit history. Regular commits over time show consistent work habits. A project with 200 commits over 3 months is more impressive than one with a single massive commit.

If you need to build portfolio projects with mobile money integration and proper deployment, the McTaba Full-Stack + AI programme (~TZS 2,400,000) includes capstone projects with payment integration. Create a free account to see the curriculum.