Do Tech Employers Care About Certificates or Just Skills? (Honest Answer)

Let us talk about where the certificate obsession comes from, because understanding it helps you break free from it.

In many African education systems, the certificate is the goal. You study for KCSE, you get a certificate. You complete university, you get a degree. You apply for a government job, they check your certificates. The entire system trains you to believe that the document proving you did something is more important than the thing you actually learned. That conditioning runs deep.

So when people start learning to code, they naturally apply the same logic. "I will take this free course and get a certificate. Then another. Then another. Eventually I will have enough certificates to prove I am a developer." Some people accumulate 15, 20, even 30 certificates from Coursera, freeCodeCamp, Udemy, and Google before they ever apply for a single job.

Here is the problem. When they finally apply, the hiring manager at a tech company does not look at those certificates. They look at the portfolio link. They look at the GitHub profile. They ask the candidate to build something during the interview. And the candidate with 30 certificates but no deployed projects has nothing to show.

This is not because certificates are inherently bad. It is because certificates answer the wrong question. The hiring manager is not asking "did this person sit through a course?" They are asking "can this person build things that work?" A certificate cannot answer that question. A live, deployed project can.

We talk to hiring managers and CTOs across the Kenyan and Nigerian tech markets regularly. Here is what they consistently tell us matters, in rough order of importance:

1. Portfolio of deployed work. Can you show me something you built? Is it live? Can I click on it? Does it actually work? This is the first filter. If you have deployed projects with real functionality, you pass. If you do not, nothing else on your application can save you.

2. GitHub activity. Not the number of repositories, but the quality and consistency. Do you have meaningful projects with clear code structure? Are your commit messages readable? Do you have regular activity over weeks and months, or did you push everything in one weekend? Hiring managers check contribution graphs.

3. Interview performance. Can you explain what you built and why? Can you work through a problem you have not seen before? Can you read someone else's code and make sense of it? Can you communicate technical ideas clearly? These are the skills that get tested in interviews, and no certificate prepares you for them. Building things does.

4. Relevant technical skills. Do you know the stack they use? For most companies in Kenya, that means React or similar on the front end, Node.js or Python on the back end, and a database. For local-facing companies, M-Pesa or payment integration experience is a major bonus.

5. Evidence of problem-solving ability. Did you build something that solves a real problem? Did you make interesting technical decisions? Can you talk about trade-offs? This is what separates "I followed a tutorial" from "I can think through problems."

Way down the list: certificates. Most hiring managers barely glance at the certificates section of a CV. Some actively ignore it. One CTO we spoke with said, "When I see a CV that leads with certificates instead of projects, I assume this person has been learning but not building. That is a red flag."

We are not saying certificates are always useless. There are specific situations where they carry weight. Knowing which situations helps you be strategic about where you invest your time.

Government and parastatal jobs. If you are applying for a tech role at a government agency, county government, or parastatal in Kenya, certificates and degrees often function as hard requirements. The HR department has a checklist, and if you do not have the right papers, your application is filtered out before a technical person ever sees it. In this hiring environment, certificates matter because bureaucracy requires them.

Large corporate HR departments. Some large banks, telecoms, and multinational corporations in Africa have HR processes that require specific certifications as filters. If Safaricom's HR requires a certain certification for a role, you need it regardless of how strong your portfolio is. Check the job requirements carefully. If a specific certificate is listed as "required" (not "preferred"), take it seriously.

Vendor-specific enterprise roles. If you want to work as an AWS Solutions Architect, a Google Cloud Engineer, or a Cisco network specialist, the vendor certifications matter because they signal deep platform-specific knowledge. These certifications are expensive and rigorous, and they carry real weight in enterprise hiring.

Immigration and work permits. If you are applying for a work visa in another country, certain certifications and degrees can strengthen your application. This is a bureaucratic requirement, not a reflection of your skill, but it is real.

Your own learning structure. A good structured course (whether it gives a certificate or not) can keep you on track, provide a curriculum that makes sense, and fill gaps you did not know you had. The value is in the learning and the projects you build during the course, not in the PDF you download at the end.

For everything else, your portfolio does the talking.

Let us make this concrete. Here are two hypothetical candidates applying for the same junior developer role at a Nairobi tech startup.

Candidate A: Has completed 12 online courses. Holds certificates from Coursera (Google IT Support), freeCodeCamp (Responsive Web Design, JavaScript), Udemy (Complete Web Developer, React, Node.js), and several others. Total certificates: 12. Deployed projects: 0. GitHub: exists but has only forked repositories and tutorial code. Cannot demonstrate M-Pesa integration or any live application.

Candidate B: Completed one structured programme. Has 5 deployed applications on live URLs: a restaurant ordering system with M-Pesa payment, an event booking platform, a blog CMS with admin dashboard, a personal finance tracker, and a WhatsApp-integrated customer support tool. GitHub shows consistent commits over 4 months. Can explain every architectural decision in each project. Total certificates: 1 (programme completion).

Every hiring manager we have spoken to would interview Candidate B. Many would not even call Candidate A. The certificates are a record of sitting through content. The portfolio is proof of doing the work.

The uncomfortable truth: time spent collecting certificates is often time not spent building things. Every 40-hour Udemy course you complete without building and deploying a real project afterward is 40 hours that moved you sideways instead of forward. The course was useful for learning. But the learning only matters if it turns into something you can show.

Here is the framework that works, whether you are self-taught, in a bootcamp, or taking online courses:

Learn a concept or technology. Take a course, read documentation, watch a tutorial. This is the input phase. Courses and certificates live here, and they are useful here.

Build something with it immediately. Do not move to the next course. Take what you just learned and build a real project. Not a tutorial clone. Something that solves a real problem, even a small one.

Deploy it to a live URL. Push it to Vercel, Railway, or whatever hosting works for your stack. Make it accessible to anyone with a web browser. If deployment feels like a gap in your skills, our Deployment & Going Live course (KES 4,999) walks you through the entire process.

Add it to your portfolio and GitHub. Write a README. Pin the repository. Add the live URL to your portfolio page. This project is now evidence of your skill.

Then move to the next thing. Now you can take the next course or learn the next technology. But only after you have converted the last round of learning into a deployed project.

This cycle means that every month of learning produces tangible output. After 6 months, you have a portfolio of deployed work that speaks for itself. The certificates from the courses you took along the way are a footnote, not the headline.

If you want to add the skill that local employers and freelance clients value most, the M-Pesa Integration for Developers course (KES 9,999) teaches you Daraja STK Push from scratch. Build it into one of your projects and you immediately stand out from every candidate who only has front-end work in their portfolio.

We are not anti-certificate. We are anti-certificate-collecting as a substitute for building. If you are going to invest in certificates, be strategic about which ones you choose.

Certificates worth considering:

• AWS Cloud Practitioner or Solutions Architect. If you want to work in cloud infrastructure or for companies that use AWS heavily. The Cloud Practitioner is entry-level and relatively affordable. The Solutions Architect is more advanced and carries genuine weight in enterprise hiring.
• Google Cloud Professional certifications. Similar value to AWS certs, particularly if your target employers use Google Cloud.
• Meta (Facebook) Front-End or Back-End Developer certificates on Coursera. These include projects, and the Meta name carries some recognition in corporate HR settings.
• Structured programme completions that include portfolio work. A certificate from a programme where you built and deployed real projects carries more weight than one from a programme where you only watched videos and passed quizzes.

Certificates you can skip:

• Generic "Introduction to Programming" certificates from any platform. These prove you clicked through a beginner course. They add nothing to your application.
• Stacking multiple certificates for the same technology (three different React certificates do not make you three times as qualified).
• Free certificates from platforms where the certificate is the product they use to get your email. These have no hiring signal.

The test: before taking any course for its certificate, ask yourself, "Will I build and deploy something real during or immediately after this course?" If yes, the course is worth your time (the certificate is a bonus). If no, you are collecting paper instead of building evidence.

If you have been spending most of your time collecting certificates, here is how to pivot:

Stop taking new courses until you have built something from each course you have already completed. Go through your certificate list. For each one, ask: did I build and deploy a project using what I learned? If not, that is your next move. Not another course. A project.

Deploy your existing projects. If you have projects sitting on your local machine that you never deployed, get them online this week. A project that exists only on localhost is invisible to employers. The Deployment course (KES 4,999) will get you past this hurdle.

Add M-Pesa integration to at least one project. If you are targeting the Kenyan or East African market, this is the highest-signal addition you can make to your portfolio. The M-Pesa Integration course (KES 9,999) gives you everything you need.

Clean up your GitHub. Pin your best repositories. Write README files for each. Make sure your commit history shows consistent activity. This is your real credential.

Rewrite your CV to lead with projects, not certificates. The first thing a hiring manager should see is a link to your portfolio and your deployed work, not a list of courses you completed.

If you want the most direct path to a portfolio that makes certificates irrelevant, the McTaba 6-month Full-Stack Developer path (KES 120,000) is built around this principle. You graduate with 15+ deployed applications, including M-Pesa integration. Your portfolio speaks louder than any certificate. That is the point.

For specific guidance on what your portfolio should include, read our guide on what a developer portfolio needs to get you hired in 2026.