How Long Does It Take to Get a Tech Job From Zero? (No-Hype Answer)

You have seen the ads. "Become a software developer in 12 weeks." "Land your first tech job in 90 days." "From zero to hired in 3 months." These timelines exist for one reason: they sell courses. They are optimised for conversion rates, not honesty.

Here is what happens in reality when someone completes a 12-week bootcamp with no prior experience: they have a basic understanding of one or two technologies, a few guided projects on their GitHub, and no ability to build something from scratch without hand-holding. Some of them get hired quickly, usually because they had prior experience in a related field (IT, design, data), strong networks, or they landed a role where "developer" means something closer to "updates the company WordPress site."

There is nothing wrong with any of those outcomes. But calling it "zero to developer in 3 months" is like calling a driving school graduate a rally driver. You know where the pedals are. You are not ready for the Nairobi to Mombasa highway during peak season.

The 3-month timeline is not impossible. It is just not representative. Using it as your baseline plan is like planning your budget around winning the lottery.

If you can dedicate 30 to 40 hours per week to learning, here is what a realistic timeline looks like:

Months 1 to 2: Foundations. How the internet works. HTML, CSS, and basic JavaScript. Your first static websites. Command line basics. Git and version control. At this stage you are building muscle memory and mental models. You can make things appear on a screen, but you do not understand why things work the way they do. This is also where a structured course like Tech Foundations (KES 2,999) saves you from spending these months wandering between random YouTube videos.

Months 3 to 5: Core skills. JavaScript in depth. A front-end framework (React is the market standard). Back-end basics with Node.js. Databases. API design and consumption. You start building things that actually do something: a to-do app becomes a real application with a database, user input, and server logic.

Months 5 to 8: Applied skills and projects. Full-stack projects. Authentication. Payment integration (M-Pesa, Paystack). Deployment. You build portfolio projects that demonstrate you can ship real software, not just follow tutorials. This is where the African Stack knowledge becomes your differentiator.

Months 8 to 12: Job preparation and search. Portfolio polishing. CV writing. Interview preparation. Contributing to open source. Applying to jobs, freelancing, or both. The job search itself takes 1 to 4 months for most people.

Some people compress this. A few stretch it. But 6 to 12 months full-time is the honest range when you account for the time it takes concepts to actually settle in your head, which no amount of speed-watching can accelerate.

Most people in Africa cannot quit their job to study full-time. That is not a disadvantage. It just means the timeline is different.

At 10 to 15 hours per week, you cover the same material but spread over a longer period. The learning is not half as effective because you are doing half the hours. In some ways, part-time learning is more effective per hour because your brain has time between sessions to consolidate what you learned. The trade-off is simply calendar time.

Months 1 to 4: Foundations and core web technologies. You are doing evenings and weekends. Progress feels slow, but it is accumulating.

Months 4 to 9: JavaScript depth, React, back-end, databases. This is where most part-time learners hit the wall. The material gets harder just as the novelty wears off. Structure and accountability matter most here.

Months 9 to 14: Full-stack projects, African Stack integration, portfolio building. You are building real things now, and the gap between "I followed a tutorial" and "I built this from scratch" starts closing.

Months 14 to 18: Job preparation and search while continuing to build. Many part-time learners start freelancing small projects during this phase, which builds experience and income simultaneously.

Eighteen months sounds long. It is. But compare it to four years for a university degree. Compare it to the years you have already spent in a career you want to leave. Eighteen months of consistent part-time effort, starting today, means you could be in a different career by the end of 2027. That is real.

The range within these timelines is wide because people and circumstances vary. Here is what actually moves the needle:

Things that speed you up:

• Prior technical experience. If you work in IT, data entry, accounting with spreadsheets, or any role where you think in systems, you already have mental models that transfer. You will move through foundations faster.
• Consistent daily practice. One hour every day beats seven hours on Saturday. Your brain builds coding ability through repeated short sessions, not marathon cram days.
• Building projects early. Following tutorials feels productive but teaches you less than struggling to build something yourself. The sooner you start building your own projects (even ugly, broken ones), the faster you learn.
• Structured learning path. Knowing what to learn next eliminates the weeks people waste researching "what should I learn?" A clear curriculum, whether from a course or a well-planned self-study path, saves months of wandering.

Things that slow you down:

• Tutorial hopping. Watching five different React tutorials instead of building one React project. This feels like learning but is actually avoidance.
• Inconsistency. Two intense weeks followed by three weeks of nothing. Each restart costs you because you spend the first few days just remembering where you were.
• Learning in isolation. No community, no accountability partner, no one to ask when you are stuck for two days on something a more experienced person could resolve in ten minutes.
• Perfectionism. Wanting to understand everything perfectly before moving forward. In coding, you learn by doing, then understanding. Not the other way around.

One thing that can actually shorten your time to employment (even if it lengthens your learning) is specialising in the African Stack early.

The global developer market at the junior level is competitive. Thousands of people complete freeCodeCamp every month. But the number of developers who can integrate M-Pesa payments, build USSD interfaces, work with Paystack and Flutterwave, and deploy applications that work well on African mobile networks is much smaller.

If you are applying for the same generic "junior React developer" roles that every bootcamp graduate worldwide is applying for, the competition is fierce. If you are applying as someone who can build a full-stack application with M-Pesa checkout for a Kenyan startup, you are competing with a much smaller pool.

This is why the timeline investment in learning the African Stack pays off. It might add a month or two to your learning phase, but it can subtract two to four months from your job search because you are not competing in the most crowded lane.

The developer who knows React AND Daraja API is harder to find than the developer who only knows React. Kenyan and Nigerian employers know this. They will prioritise the candidate who can start building for their market on day one.

The timeline starts when you start. Not when you finish researching. Not when you find the "perfect" course. Not next month when things calm down at work. Today.

If you want to test the waters, create a free McTaba Academy account and preview the material. See if this is something your brain responds to. If you want a structured foundation that prevents the most common beginner mistakes and connects your learning to the African market from day one, Tech Foundations: Before You Code is KES 2,999 and covers everything you need before writing your first line of code.

Six months from now, you will be glad you started today. Or you will be in the same position, still reading articles about how long it takes. The timeline is the same either way. The only variable is when you begin.