Writing a Developer CV That Survives Kenyan Screening

Here is what happens to your CV when you apply for a developer role at a Kenyan company. At a startup, the CTO or engineering lead glances at it for about thirty seconds. They scan for technologies they use, check if there is a GitHub link, maybe click through to your portfolio, and make a quick yes-or-no decision on whether to schedule a call. At a larger company or bank, your CV first passes through an Applicant Tracking System (ATS) that scans for keywords before a recruiter ever sees it.

In both cases, the window is narrow. You do not have time to tell your life story. You have time to answer three questions: Can this person code? Have they built anything relevant? Are they worth thirty minutes of interview time?

The Kenyan job market has some specific norms that differ from international standards. Many job seekers still use a traditional CV format that includes a headshot, national ID number, marital status, and a long list of referees. For tech roles, most of this is unnecessary and some of it is actively counterproductive. The global tech industry has largely moved away from including personal details that could introduce bias, and Kenyan tech companies (especially startups and international firms) are following this trend.

That said, some Kenyan banks and corporates still expect a more traditional format. The key is to research the specific company. A CV for Safaricom might look slightly different from one targeting a Y Combinator-backed startup in Westlands. The advice in this guide covers the modern approach that works across most tech employers, with notes on where traditional Kenyan norms still apply.

Your CV should follow a clear hierarchy that puts the most important information first. Here is the structure that works best for developer roles in Kenya.

1. Header: Name and Contact Information

Your full name, phone number, email address, location (city is enough, not your full address), and links to your GitHub, LinkedIn, and portfolio website. That is it. No headshot, no date of birth, no marital status, no national ID number. If a company specifically requests these details later, you can provide them. They do not belong on a developer CV.

2. Professional Summary (2-3 sentences)

A brief statement that says what you are, what you specialize in, and what you are looking for. Make it specific. "Full-stack developer with experience building fintech applications using React, Node.js, and PostgreSQL. Strong in M-Pesa integration and payment system design. Seeking a backend-focused role at a product company in Nairobi." That tells the reader everything they need to know in three seconds. Avoid generic statements like "passionate problem solver seeking to leverage my skills." That could be anyone.

3. Technical Skills

List your technologies grouped by category. Languages, frameworks, databases, tools, and platforms. Be specific and honest. If you have used React extensively, list it. If you followed one tutorial on Django, do not list it. Interviewers will ask about anything on your CV, and getting caught listing a technology you cannot discuss is worse than having a shorter list.

4. Projects (the most important section for junior developers)

For each project, include the name, a one-sentence description of what it does, the tech stack you used, a link to the live demo, and a link to the source code. If the project has users, mention that. "Personal finance tracker with M-Pesa integration. Built with React, Supabase, and the Daraja API. Currently used by 40 people." That single line tells an employer more than a paragraph of generic skills description.

5. Work Experience

If you have relevant tech experience, list it with bullet points that describe what you built, not just what your role was. "Built and maintained the payment notification service handling 50,000 daily M-Pesa callbacks" is useful. "Responsible for software development activities" is not. If you are a career changer, keep non-tech experience brief and focus on transferable skills: project management, data analysis, team coordination.

6. Education

List your degree, university, and graduation year. If you completed a relevant bootcamp or certification, include it here. Do not list your high school. Do not list every short course you have ever taken. Keep it tight.

GitHub profile link. This is non-negotiable for developer roles in Kenya. If your GitHub is empty or full of forked repos you never modified, fix that before you start applying. Pin your best 2-3 repositories. Make sure each has a clear README with a description, setup instructions, and screenshots. Hiring managers at Kenyan tech companies consistently say that they check GitHub links, and an empty profile raises questions about whether you actually code.

Portfolio or deployed projects. A link to a live, working application is more convincing than any description on a CV. Even a simple project that loads, works, and does not crash tells an employer that you can ship software end-to-end. If the link is broken or the site takes fifteen seconds to load, you have just made a negative impression. Test your links before you submit any application.

Specific technologies with context. Do not just list "JavaScript." Say "JavaScript/TypeScript (3 years, primary language for all projects)." Context helps the reader gauge your depth. Similarly, mention specific libraries and tools: "React with React Router and TanStack Query" tells a much richer story than just "React."

Quantifiable achievements. Wherever possible, attach numbers to your work. "Reduced API response time from 2.3 seconds to 400ms by implementing database indexing and query optimization." "Built an internal tool that automated invoice processing for 200 vendors." Numbers are concrete and memorable. They stick in a reviewer's mind when they are comparing your CV against a stack of others.

M-Pesa and local integration experience. If you have any experience with M-Pesa (Daraja API), USSD applications, or SMS integrations, highlight it prominently. This is a genuine differentiator in the Kenyan market. International candidates do not have this experience, and many local candidates have not bothered to build it into their portfolio. Even a side project that processes test payments through the M-Pesa sandbox demonstrates relevant capability.

Contributions to open source or community. If you have contributed to any open-source project, mention it. If you have spoken at a meetup, organized a hackathon, or mentored other developers, include it briefly. These details signal that you are engaged with the broader developer community, which is attractive to employers who value collaborative culture.

The headshot debate. Traditional Kenyan CVs often include a passport-size photo. For developer roles, skip it. Most tech companies do not require or expect it, and research consistently shows that photos can introduce unconscious bias in screening. Some HR departments at banks and corporates may still expect one, so check the job listing for specific requirements. If it does not ask for a photo, leave it off.

Personal details that do not belong. Your national ID number, date of birth, marital status, religion, and number of children have no bearing on your ability to write code. Including them is a holdover from traditional Kenyan CV formats. Modern tech employers do not need this information at the application stage, and many actively prefer not to receive it to avoid bias claims.

A generic objective statement. "To obtain a challenging position in a dynamic organization where I can utilize my skills." Delete this. It says nothing. Replace it with a specific professional summary that describes your actual skills and what you are looking for.

Irrelevant work experience. If you worked as a waiter, a shop attendant, or a bank teller, you do not need three bullet points about each role unless you can connect it to transferable skills. "Managed a point-of-sale system and identified a workflow inefficiency that reduced queue times" is relevant. "Served customers and maintained cleanliness" is not. Be ruthless about what you include. Every line on your CV should either demonstrate technical skill or a transferable competency.

Long lists of soft skills. "Team player, fast learner, excellent communication, attention to detail, hardworking." Everyone writes this. It communicates nothing because everyone claims the same things. Instead, demonstrate these qualities through your project descriptions and work experience. "Collaborated with a team of four developers to build and deploy a payment processing system in six weeks" shows teamwork far more effectively than listing "team player" as a skill.

References on the CV itself. "References available upon request" wastes a line. Employers know they can ask for references. Listing three referees with their phone numbers takes up valuable space. Save references for when they are requested, which is usually after the interview stage.

Larger Kenyan companies, especially banks, telecoms, and established tech firms, use Applicant Tracking Systems to filter incoming applications. If your CV does not pass the ATS, no human will ever see it. Understanding how these systems work gives you a significant advantage.

How ATS works in practice. The system scans your CV for keywords that match the job description. If the listing asks for "React, Node.js, PostgreSQL, and REST API experience," your CV needs to contain those exact terms. Not "React.js" when the listing says "React." Not "database management" when the listing says "PostgreSQL." The matching is often literal. Read the job description carefully and mirror the language.

Use standard section headings. ATS systems are trained to recognize headings like "Work Experience," "Education," "Skills," and "Projects." Creative headings like "My Journey" or "What I Bring to the Table" confuse the parser. Keep it simple and conventional. The time for creativity is in your portfolio, not your CV formatting.

Avoid complex formatting. Tables, columns, text boxes, headers and footers, and embedded images can all break ATS parsing. Stick to a clean, single-column layout with clear section breaks. Use standard fonts (Arial, Calibri, or similar). Save as PDF unless the application specifically asks for a Word document. Some older ATS systems handle Word better, but modern ones parse PDF reliably.

Include the full technology name and common abbreviations. Write "JavaScript (JS)" and "TypeScript (TS)" so the ATS catches both forms. Write "Amazon Web Services (AWS)" on first mention. This covers cases where the ATS is searching for either the full name or the abbreviation.

Do not keyword-stuff. Some candidates try to game ATS by hiding keywords in white text or cramming every technology they have heard of into a skills section. This might get you past the machine, but the recruiter or hiring manager who reads the CV next will notice. If your skills section lists fifty technologies and your projects section shows experience with three of them, the disconnect is obvious and damaging.

Tailor for each application. Yes, this is more work. No, you should not send the same CV to every company. At minimum, adjust your professional summary and skills section to mirror the language in each job description. For roles you really want, customize your project descriptions to highlight the most relevant aspects of your work. A CV that speaks directly to the job listing converts at a much higher rate than a generic one.

If you are a junior developer or career changer in Kenya, your biggest challenge is the experience gap. You do not have three years of professional software development to list. But you have more to work with than you think.

Lead with projects, not experience. Move your projects section above work experience. This is unconventional in traditional Kenyan CV culture, where employment history comes first, but for developer roles it makes sense. Your projects are your evidence of capability. If your strongest proof of skill is a full-stack application you built during a bootcamp, put it front and center. A well-described project with a live demo and GitHub link is more compelling than a two-year customer service job at a bank.

Frame your previous career as an asset. If you were an accountant, you understand financial data and business logic. If you were a teacher, you can communicate complex ideas clearly. If you were in sales, you understand user needs and stakeholder management. Map these skills explicitly to software development. "Three years in financial analysis, providing strong foundation for building fintech applications that handle accounting logic, compliance requirements, and financial reporting." That is a selling point, not a gap.

Include bootcamp and self-directed learning. If you attended a bootcamp like McTaba Labs, list it in your education section with the technologies covered and the projects you built. Self-directed learning is also worth mentioning if you can point to concrete outcomes. "Completed 500+ hours of structured learning through The Odin Project, building six full-stack applications" is credible and verifiable through your GitHub.

Use a functional-hybrid format. Instead of a purely chronological layout, group your experience by skill area. A section on "Full-Stack Development" that combines your bootcamp projects, freelance work, and open-source contributions presents a stronger picture than a chronological timeline with a gap where your career change happened.

Our full-stack developer bootcamp at McTaba Labs emphasizes portfolio development throughout the program specifically because we know what Kenyan employers screen for. Graduates leave with deployed projects, clean GitHub profiles, and a CV strategy that positions their bootcamp experience as professional development, not a footnote. If you want to build the kind of portfolio that gets callbacks in the Kenyan market, our Full-Stack Software and AI Engineering course (KES 120,000) covers the full stack and helps you build production-grade projects employers recognize.

Before you submit your CV to any Kenyan tech company, run through this checklist. Each item addresses a common mistake that costs candidates interviews.

• Length: Is it two pages or fewer? If it is three pages, cut ruthlessly. Remove anything that does not directly support your candidacy for this specific role.
• Links work: Click every link on your CV. Does your GitHub profile load? Does your portfolio site work? Is the deployed project actually running? Broken links are an instant negative signal.
• No typos: Read it out loud. Have someone else read it. Typos in a developer CV are particularly damaging because attention to detail is part of the job. A misspelled technology name is worse than a grammatical error.
• Contact info is correct: Double-check your phone number and email address. An incorrect digit means they cannot reach you, and they will not try hard to figure it out.
• Technologies match the role: Does your skills section reflect what the job listing asks for? If the listing mentions Python and your CV only mentions JavaScript, either you are applying for the wrong role or you need to adjust your CV.
• Quantifiable results: Does at least one bullet point include a number? Response times, user counts, transaction volumes, deployment frequency. Something measurable.
• Professional email: Use an email address that looks professional. Your university email or a clearly personal Gmail works fine. An email like coolguy2003@yahoo.com does not.
• File name: Save it as "FirstName-LastName-Developer-CV.pdf" not "CV-final-FINAL-v3.pdf." This small detail signals organization.

Get these basics right and you are already ahead of a significant portion of applicants. The bar for CV quality in the Kenyan tech market is not impossibly high. It just requires attention and specificity, which is exactly what writing good code requires too.