Tech Certifications vs Portfolio Projects: Which Gets You Hired in Kenya?

Collecting certificates feels productive. You finish a course, receive a PDF with your name on it, post it on LinkedIn, and get likes. It feels like progress.

But ask yourself: has a certificate ever been the reason someone got hired? In software development, the answer is almost always no.

Here is what usually happens. A developer spends three months and KES 15,000 to KES 30,000 earning an AWS certification or a Google IT Support certificate. They add it to their CV. They apply for developer jobs. The interviewer does not mention the certificate. They ask the developer to build something or solve a coding problem. The certificate is irrelevant to the evaluation.

This is not because certifications are scams. Some are genuinely valuable. But for most software development roles in Kenya, they are the wrong tool for the job. You are bringing a study guide to a building competition.

Certifications have real weight in specific tech domains. If your career path falls into one of these, pursue the relevant certs.

Cloud engineering. AWS Solutions Architect, Azure Administrator, Google Cloud Professional. Companies using cloud services want proof that you understand their platform. These certifications are often listed as requirements, not preferences, in job postings. Cloud providers also offer free training and exam vouchers.

Cybersecurity. CompTIA Security+, CEH, CISSP. Security roles deal with compliance and risk. Certifications in this field serve a regulatory purpose. They prove a baseline of knowledge that employers and auditors rely on.

DevOps and infrastructure. Kubernetes (CKA/CKAD), Terraform Associate, Docker. These certifications validate practical skills in tools that companies use at scale. They carry more weight than generic "IT" certifications.

Project management in tech. Scrum Master (CSM), PMP, SAFe certifications. If you are moving into tech project management or product roles, these certifications are commonly expected.

Notice what is not on this list: JavaScript certificates, React certificates, Python certificates, web development certificates. For these skills, employers evaluate your code, not your certificates.

Udemy, Coursera, LinkedIn Learning, and similar platforms issue certificates of completion. Let us be direct about what these are worth in the job market.

Almost nothing.

A Udemy certificate proves you watched a video course and possibly completed some exercises. It does not prove you can build anything independently. Every recruiter knows this. When they see "Udemy Certificate in React Development" on a CV, their reaction is not "impressive." It is "next."

Coursera certificates from universities (the Google IT Certificate, IBM Data Science Certificate, etc.) carry slightly more weight because of the brand association, but they still do not replace practical demonstration. A Coursera certificate next to three deployed React applications is fine. A Coursera certificate next to nothing is just a receipt.

This does not mean online courses are useless. They are excellent learning tools. Take the course. Learn the material. But skip the paid certificate at the end unless you specifically need it for a corporate checkbox. Put your money toward deploying your projects instead.

A portfolio project does something a certification cannot: it proves you can ship working software.

When a Nairobi startup is deciding between two candidates for a developer role, here is the evaluation:

Candidate A: Three Udemy certificates, a Coursera specialisation, and an AWS Cloud Practitioner badge. No deployed projects. No GitHub activity.

Candidate B: No certifications. Three deployed projects on GitHub. One is a full-stack app with M-Pesa integration. Another is a real-time dashboard. Green commit history showing consistent coding activity.

Candidate B gets the interview. Every time.

Why? Because the startup needs someone who can build features, fix bugs, and ship code. Candidate B has demonstrated all three. Candidate A has demonstrated the ability to complete online courses. These are different skills.

Your portfolio is evidence. Your certifications are claims. In any hiring decision, evidence beats claims.

If you have KES 15,000 to KES 30,000 to spend on your career development, here is a comparison of what you could do:

Option A: Buy a certification. Spend 2 to 3 months studying, take the exam, receive a PDF. You have a line on your CV.

Option B: Build two projects. Spend the same 2 to 3 months building. Use free resources to learn. Spend the money on a domain name (KES 1,000), hosting (free tier), and a better internet connection. You have two deployed applications, a stronger GitHub, and practical experience solving real problems.

Option C: Join a bootcamp. Save a bit more, join a structured program like McTaba Labs (KES 120,000 with instalment plans). Get 26 weeks of guided instruction, build 8 projects, and graduate with a complete portfolio. This is the certification and the portfolio combined into one investment.

If you are a software developer, Option B or C will advance your career faster than Option A. If you are going into cloud engineering or cybersecurity, Option A becomes valuable after you also have projects to show.

The order matters: build first, certify later. Not the other way around.

The strongest position is not "all portfolio" or "all certifications." It is a portfolio-first approach with strategic certifications added when they genuinely help.

Year one: Build 3 to 5 projects. Deploy them. Get your first developer job based on your portfolio and technical interview performance.

Year two: Once you are working and earning, evaluate whether a certification would open specific doors. If your company uses AWS heavily and an AWS certification would lead to a promotion or raise, pursue it. If not, keep building projects and deepening your skills.

Year three and beyond: Your work experience is your strongest credential. Certifications become optional enrichment rather than entry requirements.

The developers who get stuck are the ones who collect certificates before building anything, hoping that enough certificates will eventually equal competence. They do not. Competence comes from building. Certificates come from studying. They are related but not the same thing.