Back to Blog
Tech

Bootcamp vs Self-Taught vs University

MctabaMctaba
6/10/2026
7 min read
Bootcamp vs Self-Taught vs University

A straight-talking guide for anyone trying to find their way into tech in Nairobi.

If you’ve ever tried breaking into tech in Kenya, you’ve probably asked yourself this:
University? Bootcamp? Just figure it out on YouTube?

The honest answer is that it depends on your budget, your learning style, how fast you need to move, and what you can build before you start applying. Because in Kenya's job market, employers are not hiring your route they are hiring your ability to do the work.

Here is a plain breakdown of all three paths so you can make a choice that actually fits your situation.

 Why the Market Matters

PHOTO: HackHouse Africa community space where startups and tech builders work together

Kenya's tech scene is genuinely growing. The ICT sector contributes around 8.4% to GDP, and Nairobi pulls in serious startup investment across fintech, healthtech, agritech, and logistics. The jobs are real.

But so is the competition. Universities produce thousands of CS graduates every year. Bootcamps have added to that number. And remote work means you are sometimes up against developers from other countries for the same role.

What cuts through all of it is visible proof that you can build things. A deployed project beats a transcript. A GitHub history beats a certificate. The path matters less than what it produces.

 

University

A CS or IT degree from the University of Nairobi, JKUAT, Strathmore, or similar still holds real weight in Kenya. Anyone who tells you degrees are dead has probably never tried applying to Safaricom.

 Where it works for you:

•       Big corporates, banks, government agencies, and NGOs often filter CVs by degree before a human reads them. The credential gets you past that gate.

•       Four years builds theoretical depth . Algorithms, data structures, operating systems. That foundation matters for senior roles later.

•       Campus networks, faculty connections, and university hackathons lead to internships and referrals that are hard to replicate outside campus.

 

Where it works against you:

•       Three to four years is a long runway. Tech moves fast. Tools taught in first year can feel dated before you graduate.

•       Most Kenyan programmes are still theory-heavy and project-light. Many graduates finish with strong grades and thin portfolios, which is a genuinely frustrating combination.

•       The cost and time commitment is significant compared to faster alternatives.

University works best when you treat it as a starting point rather than a finish line. The graduates who get hired quickly are the ones who spent those years building things outside of class too.

 

Bootcamps

Bootcamps exist to answer one question: how do we get you employable? That focus is both the appeal and the risk.

 What bootcamps do well:

•       Speed. A good bootcamp compresses months of learning into weeks. You are building things from day one, not warming up for half a year.

•       Structure. Deadlines, instructors, and cohort energy keep you moving. If left alone with a YouTube playlist you might disappear, and a bootcamp rescues you from that fate.

•       Career support. The better programmes include CV prep, mock interviews, and employer introductions.

 

Where they fall short:

•       Quality varies a lot. Some programmes are excellent. Others charge high fees for outdated content and minimal support. The name alone is not enough. Look at what graduates actually got.

•       If the whole cohort builds the same tutorial project, nobody stands out. You need to build something original on top of what the programme gives you.

•       Bootcamps skip deep theory to move fast. That is fine for entry-level work but can become a ceiling if you want to grow into senior or architecture roles.

 

A bootcamp certificate without real projects behind it is a weak signal. That same certificate backed by deployed work and good interview prep is a completely different thing.

 

Self-Teaching

Self-teaching is the most open path. You can start tonight, for free, with just internet access. For the right person it is genuinely powerful. For the wrong person it is how two years go by watching tutorials without ever applying anywhere.

 

What works about it:

•       Free or close to it. Platforms like freeCodeCamp, The Odin Project, and CS50 offer serious technical education without tuition.

•       You control the pace. Go fast on things you absorb quickly, slow down when something needs real time. Nobody rushes you past a concept you have not actually understood.

•       You can specialise deeply. Self-taught learners often go further in specific areas like API integrations, data pipelines, or mobile development than structured programmes allow.

•       Your output becomes your credential. A GitHub full of real projects is competitive with any certificate if the work is solid.

 

What makes it hard:

•       Discipline is not optional. Without external pressure, most people slow down or stop. Pure solo self-teaching has a high dropout rate and the statistics back that up.

•       It is easy to spend months on things that do not match what Kenyan employers actually hire for. Without guidance you can build a generic portfolio and have no clear next step.

•       Some companies will filter you out at the CV stage without a formal credential. Less of an issue at startups and agencies, but it is still real at larger organisations.

 

Self-teaching works best when paired with community. Nairobi has developer meetups, WhatsApp groups, GDG events, and hackathons. The self-taught developers who break through are the ones who learned, built, showed up, and connected. Not just the ones who learned.

 

What Employers Actually Look For

Most technical hiring managers in Nairobi do not open your CV and ask which path you took. They ask whether you can solve a problem, write something that works, and explain your thinking clearly.

The strongest junior candidates right now tend to arrive with:

•       Two to four projects that are deployed and publicly accessible, not just screenshots in a PDF.

•       A GitHub profile with a real commit history, not one big push the night before sending applications.

•       At least one project tied to a real Kenyan business problem. An M-Pesa integration, a Daraja API demo, a local inventory tool. These land differently than a generic to-do app.

•       The ability to explain what they built, why they made certain choices, and what they would do differently.

 

So Which One Should You Pick?

Go with university if

•       You are younger, have the time, and are targeting large employers where degree filters are real.

•       You want deep theory and a long-term credential.

•       You are willing to combine studies with serious side projects and internships.

 

Go with a bootcamp if

•       You are switching careers and need structure and accountability to get moving.

•       You have found a programme with a genuinely strong track record.

•       You are committed to building original work beyond what the curriculum assigns.

 

Go self-taught if

•       You are highly disciplined and can hold yourself to a consistent schedule.

•       You are targeting startups or remote work where portfolio matters more than credentials.

•       You are active in tech communities and have people to learn alongside.

 

Many people also combine paths. A short bootcamp to get started, then self-teaching to specialise. University alongside freelance projects. One targeted course to close a specific gap. The boundaries are not strict. The point is to keep moving.

 

Mistakes Worth Avoiding

•       Treating a degree or certificate as the destination. It is the starting point. Building proof starts there.

•       Watching courses without building anything. It feels productive. It does not create evidence of capability.

•       Building the same projects as everyone else from the same programme. Add local context and original thinking.

•       Only applying online and never engaging with the tech community. That limits your visibility and closes referral doors.

•       Waiting until you feel ready. That feeling does not come. Apply when you have core skills and a few solid projects.

 

A Note on Mctaba

If you want structured, practical learning tied to what employers actually hire for, Mctaba is worth exploring.

The focus is on building real output rather than completing modules for the sake of it. It is designed for learners who want bootcamp-level accountability with the flexibility of self-paced study, which works well for people in Nairobi who are juggling work, family, and a career switch at the same time.

You can find self-paced courses matched to the skills in this guide at academy.mctaba.com, whether that is web development, data, or other in-demand paths. The goal is skills you can actually show.

 

Final Word

The debate between these three paths is real but also a bit of a distraction. The real question is simpler: which path, given who you are right now, gets you to strong skills and visible proof the fastest?

University gives credentials and depth but takes time. Bootcamps give speed and structure but require choosing wisely and doing more than the curriculum asks. Self-teaching gives flexibility but demands real discipline and community to work.

None of them guarantee a job. All of them can get you one if you do the work that actually matters.

Build things. Show your work. Keep going.