Switching Careers Into Tech After 30 in Kenya

If you are reading this, you are probably a teacher, an accountant, a marketer, a nurse, a bank teller, or someone in another profession who looks at tech and sees better pay, more flexibility, and a growing industry. Those observations are correct.

Here is what is also true:

• The transition takes time. You will not become a developer in 30 days, regardless of what any advert promises. Plan for 12 to 24 months of learning, building, and job hunting.
• You will feel behind. You will sit in a class or online forum with 22-year-olds who seem to understand things instantly. They do not. They are just more comfortable with the lingo. Your ability to learn is intact. Your ability to focus, manage your time, and persist through frustration is probably stronger than theirs.
• The financial transition is real. For months or even a year, you may earn less than you did before. This requires planning, not just optimism.
• Your age is not the barrier you think it is. The Kenyan tech industry cares about what you can build. If you can build a working application and communicate clearly, your age is irrelevant to most employers. The few who discriminate by age are not companies you want to work for anyway.

With those realities on the table, here is how to make the switch.

Career switchers often feel like they are starting from scratch. You are not. Your previous career gave you skills that many junior developers lack.

What you bring from your previous career:

• Domain knowledge. If you were an accountant, you understand financial systems, invoicing, tax calculations, and reporting. A fintech company building accounting software would love a developer who actually understands accounting. Your domain knowledge makes you more valuable, not less.
• Communication skills. You have spent years talking to clients, writing reports, presenting to managers, and navigating office politics. Junior developers fresh from university often struggle with these. You already have them.
• Problem-solving maturity. You have faced problems in your career that required creative solutions with limited resources. This is exactly what software development is: solving problems with constraints. The problems are different, but the mental muscle is the same.
• Reliability. You know how to show up, meet deadlines, and handle responsibility. Employers value this. Being the developer who delivers on time is more valuable than being the developer who knows 10 frameworks but misses deadlines.

How to leverage these in your transition:

• Build projects in your domain. If you come from healthcare, build a patient record system. If you come from education, build a school management tool. If you come from retail, build an inventory tracker with M-Pesa payment integration.
• Target employers in your domain. A health-tech startup hiring a junior developer will value your nursing background. A fintech company will value your banking experience. You are not just another junior developer. You are a junior developer who understands their users.

As a career switcher, your biggest constraint is probably not ability. It is time. You are likely working a full-time job, possibly supporting a family, and trying to learn in the margins of your day.

Realistic learning options:

Option 1: Bootcamp (intense, fastest path)

• Duration: 3 to 6 months. Some are full-time (9 AM to 5 PM), which means you may need to leave your current job or take unpaid leave. Part-time bootcamps (evenings and weekends) let you keep earning while you learn.
• Advantages: structured curriculum, deadlines, peers, career support.
• Consideration: cost varies from free (income-share) to KES 50,000 to KES 200,000+. Factor this into your financial plan.

Option 2: Self-study with a structured curriculum (slower, cheapest)

• Duration: 9 to 18 months at 1 to 2 hours per day.
• Use a structured path like The Odin Project, freeCodeCamp, or Full Stack Open. Avoid the trap of randomly jumping between YouTube tutorials.
• Advantages: free or very cheap, flexible schedule.
• Challenge: requires iron discipline. No one checks if you showed up. No one pushes you to finish. You are accountable only to yourself.

Option 3: Hybrid (bootcamp evenings + self-study)

• Enrol in an evening or weekend bootcamp for structure and accountability. Supplement with self-study during the week.
• This is the most common approach for career switchers in Kenya. You keep your income, get structured learning, and build at your own pace between sessions.

What to focus on first:

• JavaScript and web development is the fastest path to employment in Kenya. The demand is there, the tools are free, and you can see results quickly (a webpage in your browser).
• Python is a good second choice, especially if you are interested in data analysis, automation, or backend development.
• Do not try to learn five languages at once. One language, learned deeply, is enough to get hired.

This is the part that most "career switch into tech" articles skip, and it is the part that matters most for people with real financial responsibilities.

The financial reality:

• If you are learning part-time while working, your income stays the same during the learning phase. But you will likely need to invest money in a bootcamp, internet, and potentially a laptop.
• If you leave your job to study full-time, you need savings to cover 6 to 12 months of expenses. This includes rent, food, transport, school fees (if you have children), data bundles, and loan repayments.
• Your first tech job may pay less than your current career, at least initially. Be financially prepared for this. The salary growth in tech tends to be steeper than most other industries, but the starting point for a career switcher may be lower than your current earnings.

Practical steps:

1. Build a transition fund. Before you make any drastic moves, save 3 to 6 months of living expenses. This gives you a buffer for the learning period and the job hunt that follows.
2. Keep earning while you learn. Unless you have significant savings, do not quit your job on day one. Learn in the evenings and weekends. It is slower but financially safer.
3. Reduce expenses. Look at your monthly budget honestly. Can you cut non-essential spending during the transition? Every shilling saved extends your runway.
4. Start freelancing early. Even basic web development skills (HTML, CSS, a simple WordPress site) can earn you freelance income within 3 to 4 months of starting. Use this to supplement your income and build a portfolio simultaneously.
5. Talk to your family. If you have a spouse, dependents, or parents who rely on your income, involve them in the decision. The transition affects them too. Their support (or lack of it) will significantly impact your ability to focus on learning.

This timeline assumes you are learning part-time (1.5 to 2 hours per day on weekdays, more on weekends) while keeping your current job.

Months 1 to 3: Foundation

• Learn HTML, CSS, and basic JavaScript.
• Build 2 to 3 small projects (a personal website, a simple calculator, a to-do list).
• Set up your GitHub account and start pushing code.
• Join a dev community (GDG Nairobi, a WhatsApp or Telegram group).

Months 4 to 6: Building capability

• Learn a framework (React is the safest bet for the Kenyan job market).
• Learn backend basics (Node.js + Express, or Python + Flask).
• Learn basic SQL and database concepts.
• Start your first "real" project: something that solves a problem in your domain.

Months 7 to 9: Portfolio building

• Build 2 to 3 portfolio-quality projects. Deploy them. Write READMEs.
• Build your portfolio website.
• Set up your LinkedIn and GitHub profiles properly.
• Start attending meetups and connecting with people in the industry.

Months 10 to 12: Job hunting

• Write your CV (tailored for tech).
• Start applying. Target 5+ applications per week.
• Practice interview questions (both technical and behavioral).
• Take freelance projects if they come your way.
• Keep learning and building while you apply. Your portfolio should improve every week.

Months 12 to 18: Landing and settling

• Land your first role (full-time, contract, or meaningful freelance engagement).
• Survive the first 3 months on the job. Ask questions. Ship small wins. Learn the codebase.
• Begin planning your growth: what skills to deepen, what to learn next.

Some people move faster. Some take longer. The timeline depends on your available time, your learning speed, and the job market when you start applying. Do not compare your pace to others. Consistency beats speed.

Career-switching articles are usually relentlessly positive. Here are the parts that are hard, because you deserve to know what you are getting into.

• Identity shift. You have been a teacher, an accountant, a marketer for years. That identity is comfortable. Becoming a "student" again, especially one who does not understand basic concepts that 20-year-olds seem to grasp easily, is humbling. This phase passes, but it is uncomfortable.
• Social pressure. In Kenya, career stability is valued. When you tell your family or friends you are "learning to code," some will be supportive. Others will think you are going through a phase. Some will actively discourage you. Prepare for this and lean on the people who support you.
• The dip. Around month 3 to 4, many people hit a motivational wall. The initial excitement fades. JavaScript is harder than the first tutorial made it seem. You cannot build what you imagined. This is the point where most people quit. If you push through this dip, the other side is where real capability begins.
• Imposter syndrome. Even after you land a job, you may feel like you do not belong. Every developer feels this at some point. Career switchers feel it more intensely because they are comparing themselves to people who have been coding since secondary school. Remember: you were hired because someone believed you could do the job. Trust that assessment.
• Financial stress during the transition. If your current job pays the bills and your future tech salary is uncertain, the anxiety is real. This is why financial planning matters so much. Do not romanticize the "burn the boats" approach. Be strategic.

None of these challenges are insurmountable. But being aware of them helps you prepare, and preparation is what separates people who complete the transition from those who start and stop.