Who Should Join a Software & AI Engineering Program (And Who Shouldn't)
A software and AI engineering program works best for three groups: underemployed graduates who need structure and a portfolio, career switchers who want to move into tech quickly, and self-taught developers who have hit a ceiling and need production experience. It is not the right fit if you need an accredited degree, cannot commit 20 or more hours per week, already have professional engineering experience, or have no interest in building for African markets.
Three types of people who get the most out of this
After running multiple cohorts, we have a clear picture of who thrives in this program. It comes down to situation, not talent. Smart people fail when the program does not fit their circumstances. Average students succeed when it does.
The underemployed graduate
You finished university one to three years ago. Maybe you studied IT, business, or something unrelated to software. You have a job, but it pays poorly and does not use the skills you actually want to develop. You tried learning to code on your own. YouTube tutorials, FreeCodeCamp, maybe a Udemy course. You understand the basics but never built anything real. You got stuck, lost momentum, and started the cycle again a few months later.
What you need is not more tutorials. You need a deadline, a mentor, and a project that forces you to solve real problems under real constraints. The structure of a cohort provides all three.
If this sounds like your situation, the Software & AI Engineering program is built for you. Phase 1 starts from fundamentals, so you do not need prior coding knowledge to succeed.
The career switcher
You are in your late 20s or 30s, working in a field that no longer excites you. Teaching, banking, customer service, sales, marketing. You are drawn to tech because you see the opportunities and you want work that feels more intellectually engaging. But you worry that you are too late, too old, or too far from the industry to make the switch.
You are not. The age concern is the most common objection we hear, and the least valid. What matters is whether you can commit the time (20 to 25 hours per week) and whether you are comfortable being a beginner again.
The cohort structure helps career switchers specifically because it provides accountability. When you are switching careers on your own, it is easy to lose motivation during the hard weeks. When you have classmates, a mentor, and a deadline, dropping out is much harder.
The self-taught developer at a plateau
You can write code. You have built a few projects. You might even have done some freelance work. But you have never integrated a payment system, never shipped something to production that handles real traffic, and never worked in a structured engineering environment with code reviews, Git workflows, and deployment pipelines.
The gap between "I can build things" and "I can build things that businesses pay for" is real, and it is hard to close alone. You do not know what you do not know. A structured program exposes you to production-grade engineering practices, African Stack integrations you would never encounter in a tutorial, and AI engineering skills that are difficult to learn from scattered online resources.
If you are in this category, you will likely move through Phase 1 quickly and get the most value from Phases 2 through 5, where the projects become genuinely challenging.
Four types of people who should choose something else
We would rather turn you away than take your money for a program that does not fit your situation. Here is who should not join:
You need an accredited credential. Some employers require a degree for the role you want. Some visa processes require formal qualifications. If your goal depends on having an accredited certificate, attend a university. This program gives you skills and a portfolio, but it is not accredited.
You cannot commit 20 hours per week. The cohort has live classes five days a week plus independent project work. If your job, family, or other commitments mean you can only study a few hours on weekends, you will fall behind and likely drop out. The self-paced Academy course covers similar material without the time pressure.
You already have 2 or more years of professional experience. Phases 1 and 2 will bore you. The program is designed to take someone from zero (or near-zero) to production-ready. If you are already shipping code professionally, you are past the stage this program serves. Consider the self-paced course where you can skip ahead, or focus on the AI engineering content specifically.
You do not care about African markets. The entire curriculum is built around M-Pesa, USSD, WhatsApp Business API, and African business problems. If you want to build SaaS for the US market or work exclusively with international companies that use standard Western tooling, this program will feel irrelevant. A generic full-stack bootcamp would serve you better.
Common concerns that should NOT stop you
These are the worries we hear most from people who end up succeeding in the program:
"I am too old." We have had students in their 30s and 40s. Age is not a barrier. Your learning speed might differ from a 22-year-old's, but your life experience, discipline, and motivation usually compensate. The oldest students in our cohorts are often the most consistent.
"I am not smart enough for coding." Software engineering is a skill, not a talent. It responds to practice and repetition, not innate intelligence. If you can follow a recipe, troubleshoot a problem, and stay focused for a few hours at a time, you have enough to start.
"I tried before and failed." That usually means the format was wrong, not that you lack ability. Self-paced online courses have completion rates below 10% across the industry. If you failed at self-paced learning, it means you are normal. A structured cohort with deadlines and mentors is a different experience.
"I do not have a technical background." Phase 1 starts from HTML and CSS. We do not assume prior knowledge. Having a non-technical background is common among our students and has never been a predictor of failure.
A quick self-assessment
Answer honestly:
- Can you commit 20 to 25 hours per week for 30 weeks?
- Are you interested in building software for African businesses or users?
- Are you comfortable being a beginner and asking for help when stuck?
- Do you have a laptop and reliable internet access?
- Are you joining because you want skills and a portfolio, not because you want a certificate?
If you answered yes to all five, the program is likely a good fit. If you answered no to one or two, think carefully about which ones and whether they are dealbreakers. If you answered no to three or more, this is probably not the right time or program for you.
Not sure? Join the Discord and ask current students about their experience. They will give you a more honest answer than any webpage.
Key Takeaways
- ✓The program is designed for beginners and career switchers, not experienced engineers
- ✓You need 20+ hours per week available; if you cannot commit that, self-paced learning is a better option
- ✓Interest in building for African markets matters because the curriculum revolves around M-Pesa, WhatsApp, and USSD
- ✓Age does not disqualify you; motivation and time availability do
Frequently Asked Questions
- What is the minimum age to join?
- There is no strict minimum age, but the program is designed for adults who are ready to commit significant time. Most students are between 20 and 40 years old. If you are a high school graduate, the dedicated high school launchpad program might be a better starting point.
- Do I need my own laptop?
- Yes. You need a laptop (not a tablet or phone) with at least 8 GB of RAM and a reliable internet connection. The program does not provide hardware.
- Can I join from outside Kenya?
- Yes. The program runs online and is open to students from any country. The African Stack skills are most directly relevant if you plan to work in East or West Africa, but the full-stack and AI engineering skills are universally applicable.
- What if I realize the program is not for me after starting?
- Talk to your mentor. If you are struggling with the pace, they will work with you on a plan. If the program genuinely is not the right fit, it is better to acknowledge that early than to force through 30 weeks of frustration. Contact us to discuss options.
- I have a full-time job. Can I still do this?
- It depends on your job. The live classes and project work require roughly 20 to 25 hours per week. Some students manage it alongside a standard 9-to-5, especially if their job has predictable hours and they are disciplined with their evenings and weekends. Others find it very difficult. Be honest about your available time before committing.
- Is the program harder or easier than a university CS degree?
- Different. A CS degree covers theory (algorithms, discrete math, operating systems) across 3 to 4 years. This program skips the theory and focuses on applied, production-oriented skills across 30 weeks. The intensity per week is higher, but you are not studying abstract math. You are building real applications from month one.
Ready to build real-world apps?
Join the McTaba Labs full-stack marathon (4 months full-time · 6 months part-time). Learn M-Pesa, USSD, and WhatsApp engineering while shipping 8 production apps.
Apply to the McTaba Marathon