A complete 2026 guide to writing a winning tech CV — with a free template, real examples, recruiter insights, and tips specific to Kenya's job market.
G-Tech Blog | 2026 | 20 min readA strong CV is your first and most important step to getting shortlisted for tech jobs in Kenya. Recruiters and hiring managers spend only a few seconds scanning each CV before deciding whether to read further — and in a competitive market where hundreds of applicants may apply for a single role, clarity, relevance, and structure matter far more than fancy design or length. This guide walks you through everything you need to know to write a tech CV that gets results in Kenya's job market in 2026.
Kenya is home to one of Africa's most vibrant technology ecosystems. Nairobi — often called "Silicon Savannah" — hosts the African headquarters of major global tech companies including Google, Microsoft, IBM, and Cisco, alongside a thriving community of homegrown startups, fintech companies, and digital agencies. The tech sector has grown significantly over the past decade, driven by mobile money innovation, a young and educated workforce, widespread smartphone adoption, and increasing internet penetration across East Africa.
For job seekers, this creates both opportunity and competition. Entry-level developer roles attract hundreds of applicants. A well-structured, targeted CV is not optional — it is the difference between getting shortlisted and being overlooked in the first screening round. Understanding what Kenyan recruiters and hiring managers actually look for is the starting point for writing a CV that works.
The Kenyan tech job market has also increasingly embraced remote work since 2020. Many developers now work for companies based in Europe, the United States, or the Gulf region while living in Nairobi or other Kenyan cities. This means your CV may be read by both local Kenyan recruiters and international hiring managers — and it needs to work well for both audiences.
Before you write a single word, get the format right. A poorly formatted CV — regardless of how strong your experience is — signals a lack of attention to detail, which is a red flag for any technical role. Here are the non-negotiable format rules for tech CVs in Kenya.
Every strong tech CV follows a consistent structure. Hiring managers scan CVs in a predictable pattern — they expect information to be where they expect to find it. Surprising them with an unusual layout adds friction and reduces your chances. Here is the recommended section order for tech roles in Kenya.
Place this at the very top of your CV. Include: your full name (large, prominent), phone number with country code (+254 for Kenya — key for international recruiters), professional email address, your city (Nairobi, Mombasa, Kisumu, etc.), LinkedIn profile URL, and GitHub profile URL.
You do not need to include your physical street address, ID number, date of birth, marital status, religion, or a photograph unless the specific job advertisement explicitly requests these. Most modern Kenyan tech employers and virtually all international employers do not require this personal information and may view its inclusion as unfamiliar with current hiring norms.
A professional summary is optional but highly recommended. It sits directly below your contact information and serves as your 30-second pitch — the answer to "tell me about yourself" in written form. Keep it to 3— 4 lines and focus on three things: your role or specialization, your years of experience or level (entry, mid, senior), and your most relevant strength or the value you bring.
The summary should change for every application you make. If you are applying for a React Developer role, your summary should mention React. If you are applying for a data engineering position, mention data pipelines and relevant tools. A generic summary that works for every job actually works for none of them.
"Recent Computer Science graduate from the University of Nairobi with hands-on experience building full-stack web applications using React and Node.js. Passionate about clean code, open-source contribution, and solving real-world problems with technology. Seeking a junior software engineering role in a fast-growing Kenyan tech company."
"Software Engineer with 4 years of experience building scalable fintech and e-commerce platforms in Nairobi. Proficient in Python (Django/FastAPI), PostgreSQL, and AWS. Led development of a mobile money integration serving 200,000+ users. Seeking a senior backend engineering role at a product-focused company."
The skills section is often the first thing a technical recruiter looks at after your name and contact details. It serves as a quick filter — if the required technologies are not visible, your CV may be discarded before anyone reads your experience. Keep this section focused, honest, and structured.
Group your skills into logical categories for easy scanning. Common categories for tech roles include: Programming Languages, Frontend Technologies, Backend Technologies, Databases, Cloud & DevOps, Tools & Platforms, and Methodologies. Only list skills you can genuinely discuss in an interview — claiming proficiency in something you barely touched is a risk that often backfires in technical screenings.
This is the most important section of your CV. List your positions in reverse chronological order — most recent first. For each role, include: your job title, the company name and a brief description of the company if it is not well known (e.g. "a Nairobi-based fintech startup"), the dates of employment in month and year format (e.g. March 2023 — Present), and 3— 5 bullet points describing your key contributions and achievements.
Include internships, freelance work, contract roles, and relevant part-time positions. For fresh graduates with limited formal work experience, include any volunteer projects, bootcamp practical work, or university group projects that involved real technology. Gaps in employment are not automatically negative — be prepared to explain them briefly in interviews if asked.
List your highest qualification first. Include: the degree or qualification name, the institution, the year of graduation (or expected graduation year). Add your grade if it was strong (Upper Second or First Class for university degrees). Include relevant coursework, final year project titles, or academic awards if you are a recent graduate and need to fill out the section.
Certifications from recognized providers deserve their own short section or can be added under education. In Kenya's tech market, certifications from Google (Associate Android Developer, Professional Data Engineer), AWS (Cloud Practitioner, Solutions Architect), Microsoft (Azure Fundamentals), and Cisco (CCNA) carry real weight and are worth listing prominently.
For developers with limited work experience — fresh graduates, bootcamp graduates, self-taught developers — the projects section can be the most compelling part of the CV. A well-documented project that solves a real problem and demonstrates a full technology stack tells a recruiter far more about your abilities than a list of courses completed.
For each project include: the project name, a one to two line description of what it does and who it is for, the technology stack used, and a link to the live version or the GitHub repository. Three to five strong projects are better than a long list of half-finished or trivial ones.
Use the structure below as the foundation for your own CV. Replace every placeholder with your real information. The layout is deliberately simple — clean, ATS-friendly, and easy for human readers to scan quickly.
The bullet points in your experience section are the most scrutinized part of your CV. Weak bullets describe what you were responsible for. Strong bullets describe what you actually did, built, or achieved — and ideally, the impact it had. The difference between a weak and strong bullet is often the difference between getting shortlisted and not.
Follow this formula for every bullet point: Action verb + what you did + technology/method used + result or scale. Not every bullet will have a quantifiable result, but push yourself to include numbers wherever you genuinely have them — percentage improvements, user counts, transaction values, time saved, team size, or performance metrics all make your bullets concrete and credible.
| Weak Bullet | Strong Bullet |
|---|---|
| Responsible for backend development | Built and maintained 8 REST API endpoints using Node.js and Express serving 15,000 daily requests |
| Worked on the company website | Redesigned company website in React, reducing page load time by 55% and increasing mobile conversion rate by 20% |
| Helped with database management | Optimized 12 slow PostgreSQL queries by adding indexes and rewriting subqueries, reducing average query time from 4s to 0.3s |
| Did testing | Wrote 200+ unit and integration tests using Jest and React Testing Library, raising code coverage from 42% to 87% |
| Integrated payment systems | Integrated M-Pesa Daraja API (STK Push and C2B) for a retail platform processing KES 500K+ in daily transactions |
Start every bullet with a strong past-tense action verb for previous roles (Built, Developed, Designed, Implemented, Optimized, Led, Reduced, Increased, Integrated, Migrated, Automated) and present tense for your current role (Build, Maintain, Lead, Develop). Avoid passive constructions like "was responsible for" or "involved in."
The skills section looks simple but is frequently done poorly. The two most common mistakes are listing too many skills (to appear well-rounded) and listing skills at an inaccurate level. Both hurt your credibility. A recruiter who sees 30 technologies listed on a junior developer's CV will immediately be skeptical. A developer who claims "expert" Python but can't write a basic function in an interview destroys trust instantly.
HTML/CSSJavaScriptTypeScriptReactNext.jsTailwind CSSFigmaGitREST APIsResponsive Design
Node.jsPythonExpressDjangoFastAPIPostgreSQLMongoDBRedisDockerREST/GraphQL
FlutterDartReact NativeAndroid/KotlinFirebaseREST APIsM-Pesa integrationApp Store/Play Store
PythonPandasNumPyScikit-learnTensorFlowSQLPower BITableauBigQuerySpark
Projects are the great equalizer in Kenya's tech job market. They let you demonstrate real skills regardless of whether you have formal employment experience. A compelling, well-documented project — especially one that solves a Kenya-specific problem — can impress a hiring manager far more than a lengthy list of courses and certificates.
The best projects for a Kenyan tech CV are ones that address local needs: M-Pesa integrations, NHIF or KRA automation tools, matatu tracking applications, agricultural market price finders, Swahili language processing tools, or school management systems. These demonstrate not just technical skill but also contextual understanding of the local market — something that genuinely differentiates you from candidates who build generic tutorial-level projects.
One of the most common questions from new developers in Kenya is: "How do I write a CV when I have no professional experience?" The answer is that you have more to work with than you think — and the key is to be strategic about what you emphasize.
If you are a fresh graduate from a university or bootcamp, lead with your skills and projects, not your experience. Reorder your sections so that Skills and Projects come before Education and Experience. Expand your projects section significantly — three to five projects with live demos and detailed descriptions carry more weight for junior roles than an empty experience section. Include internships, attachment placements, hackathon projects, and university coursework projects. Any real code you have written counts.
If you have three or more years of experience, your challenge is different: you likely have too much to include and need to make strategic cuts. Focus your CV on the experience most relevant to the type of role you are applying for. A backend developer applying for a DevOps role should move their infrastructure experience to the front and de-emphasize pure coding work. An engineer moving into management should highlight team leadership, mentoring, and cross-functional collaboration alongside technical achievements.
Quantify your impact aggressively. At the senior level, recruiters expect to see evidence of scale and leadership, not just task completion. How many users did your systems serve? How much did your optimizations save in server costs or response time? How many developers did you mentor? What was the revenue impact of features you built? Numbers make your experience concrete and memorable.
Kenya's tech talent is increasingly sought by international companies. Platforms like Andela, Toptal, Upwork, LinkedIn, and Remote OK regularly feature opportunities for Kenyan developers to work with companies in the US, UK, Europe, and the Gulf. Applying for these roles requires a few adjustments to the standard Kenyan CV approach.
For remote and international applications, your CV should demonstrate not just technical skills but also remote work competencies: written communication, self-management, experience with asynchronous tools (Slack, Notion, Linear, GitHub), and any previous remote work experience. Mention time zone flexibility and your reliable internet setup if relevant to the role.
Salary expectations are often requested in international applications. Research market rates for your role and experience level in the target country — rates for Kenyan developers working remotely for US companies are typically higher than local Kenyan salaries but lower than US-based salaries. Sites like Levels.fyi, Glassdoor, and the Stack Overflow Developer Survey give useful benchmarks.
If you have experience integrating M-Pesa (Safaricom's Daraja API), Pesalink, or other Kenyan fintech systems, highlight this prominently. Kenya is a global leader in mobile money, and companies both locally and internationally value developers who understand this ecosystem. Name the specific API (STK Push, C2B, B2C, B2B), the transaction volumes handled, and the platform it was built for.
Applications and systems built for Kenya-specific contexts — NTSA integrations, KRA tax compliance, NHIF claims, eCitizen API, or MPDB databases — demonstrate local domain knowledge that international candidates can't match. Mention these where relevant.
A surprisingly high proportion of tech hiring in Kenya happens through LinkedIn — both through active job postings and through recruiters searching for candidates directly. Your LinkedIn profile should mirror and expand on your CV. Keep it updated, use the "Open to Work" feature when job seeking, and post occasionally about projects you are working on. Many Kenyan developers have been approached for roles they never applied for simply because a recruiter found their LinkedIn profile.
Applicant Tracking Systems (ATS) are software tools used by larger employers — banks, telecoms, international NGOs, and multinational companies — to automatically filter and rank incoming CV applications before a human ever reads them. If your CV does not pass the ATS filter, it will never reach a recruiter's desk regardless of how strong your experience is.
ATS systems work by parsing your CV text, extracting keywords, and matching them against the job description. A CV with a 70%+ keyword match is more likely to be surfaced to a recruiter than one with a 30% match. This is why generic CVs underperform — they are not matched to the specific language of each job posting.
Your CV gets you to the shortlist. Your LinkedIn profile and portfolio often determine whether you get the interview call. Treat these as extensions of your CV that give employers a richer picture of who you are as a developer.
Your LinkedIn headline should not just say "Software Developer" — it should say what kind of developer and what you are looking for: "Full-Stack Developer | React & Node.js | Open to Opportunities in Nairobi." Your About section should be your professional summary expanded to 3— 4 paragraphs. List all your experience, education, skills, and certifications — LinkedIn profiles with complete information rank higher in recruiter searches. Collect endorsements and recommendations from colleagues, managers, or clients.
A personal portfolio website is increasingly expected for frontend, full-stack, and UI/UX roles in Kenya. It does not need to be complex — a simple site with an about section, your projects with screenshots and links, your skills, and a contact form is sufficient. Deploy it on a custom domain (yourname.dev or yourname.com) using Vercel, Netlify, or GitHub Pages. The portfolio itself becomes a project that demonstrates your skills.
Many Kenyan tech job applications do not require a cover letter — the CV and a portfolio link are sufficient. However, when a cover letter is requested or when you are applying for a competitive role at a company you particularly want to join, a strong cover letter can significantly improve your chances. A weak or generic cover letter, on the other hand, actively harms your application.
Keep your cover letter to one page — three to four short paragraphs. The first paragraph should name the specific role and explain briefly why you are applying and why this particular company interests you (show that you have done research). The second paragraph should connect your most relevant experience and skills directly to the role's requirements. The third paragraph should highlight something specific — a project, an achievement, a skill — that is not immediately obvious from your CV. Close with a confident, professional sign-off.
’R Generic: "I am writing to apply for the software developer position at your esteemed company. I am a hardworking and dedicated professional with a passion for technology."
“& Specific: "I am applying for the Backend Engineer role at Cellulant because your work on pan-African payment infrastructure directly aligns with my experience building M-Pesa integrations and high-availability financial APIs in Node.js and Python. I have followed Cellulant's expansion into francophone Africa closely and would welcome the opportunity to contribute to that growth."
Proofread every word. Use tools like Grammarly or ask a friend to review. A typo in a developer's CV implies the same carelessness that produces bugs in code. Recruiters notice immediately.
"Hardworking team player," "fast learner," "passionate about technology" — these phrases appear on thousands of CVs and mean nothing without supporting evidence. Replace them with specific achievements and numbers.
Kenya's tech community is smaller than it seems. Claiming expert-level skills you do not have will be exposed in a technical interview or coding test and will permanently damage your reputation with that employer.
Canva and Novoresume templates look attractive but often fail ATS parsing and distract from content. A clean, simple layout where your experience and skills are easy to find outperforms any graphically complex design.
A CV that is not tailored to a specific role performs significantly worse than one that matches the job description. Even small changes — adjusting the summary, reordering bullet points, matching skill names — measurably improve your shortlisting rate.
For developer roles, a CV without a GitHub profile or portfolio is a missed opportunity. Recruiters actively click these links. An active GitHub profile with well-documented projects is often the deciding factor between two similar candidates.
Tailoring does not mean rewriting your entire CV from scratch for every application. It means making targeted, strategic adjustments that increase the relevance of your CV for a specific role. Most tailoring can be done in 15— 20 minutes once you have your base CV ready.
Start by reading the job description carefully and highlighting: the role title, the required technical skills (especially specific languages, frameworks, or tools), the experience level and years required, the industry or domain (fintech, healthcare, e-commerce), and any soft skills or working style attributes mentioned. Then make the following adjustments to your CV.
It's not required and generally not recommended for tech roles, especially when applying to international companies or startups. Most modern tech employers in Kenya are moving away from photos to reduce unconscious bias in screening. The exception is if a specific job advertisement explicitly requests a photo or if you are applying to a traditional corporate environment where it remains expected. When in doubt, leave it out — a photo adds no technical value and can only introduce irrelevant factors into the hiring decision.
Employment gaps are common and are not automatically disqualifying in Kenya's tech market. If the gap was due to studying, self-learning, working on personal projects, freelancing, family responsibilities, or health reasons, you can briefly note this either on your CV (e.g. "2022— 2023: Self-directed study in cloud computing, achieved AWS Certified Cloud Practitioner") or save the explanation for the interview. What you should not do is leave an unexplained multi-year gap with nothing to show — use the time to build something, complete a certification, or contribute to open source so the gap becomes a period of visible activity.
Yes — in most cases. Recruiters reviewing hundreds of applications actually prefer shorter CVs for junior candidates because they demonstrate the ability to prioritize relevant information. A junior developer with a two-page CV that is padded with irrelevant coursework, generic soft skills, and every small project ever attempted makes a worse impression than a tight, well-organized one-pager. Be ruthless: if a line does not strengthen your case for the specific role, cut it.
For tech roles in Kenya, the most active platforms in 2026 are LinkedIn (the most important — set up job alerts immediately), BrighterMonday Kenya, MyJobMag, Glassdoor Kenya, and Fuzu. For remote opportunities, also check Andela, Remote OK, We Work Remotely, and Toptal. Follow the careers pages of companies you want to work at directly — many Kenyan tech companies post roles on their own websites before listing them on job boards.
Certifications complement experience but rarely replace it. An AWS certification on its own does not make you a cloud engineer — but combined with hands-on projects or work experience using AWS, it validates and signals depth. For fresh graduates and career changers, certifications from Google, AWS, Microsoft, and Cisco carry genuine weight as proof of structured learning. For experienced developers, they are less important than demonstrated project and employment history, though they remain a useful differentiator for specific technical roles.
A great tech CV in Kenya is clear, specific, honest, and targeted. It leads with your strongest assets — whether that is years of fintech experience, a portfolio of compelling projects, or a strong set of in-demand technical skills. It speaks directly to the role you are applying for using the language of the job description. And it gives a recruiter everything they need to make a quick, positive decision in your favour.
Use the template and examples in this guide as your starting point. Build your base CV carefully, then treat it as a living document — tailored for every application, updated with every new project and achievement, and refined over time as you gather feedback from interviews. Combine it with an active LinkedIn profile, a live portfolio, and genuine engagement with Kenya's tech community, and you will be well positioned to land the role you are targeting.
Kenya's tech industry is growing fast. The opportunities are real. The competition is fierce. A strong CV is your first step to getting in the room — make it count.