Is 18 Too Young to Start a Tech Career? Is 30 Too Old?

At 18, you scroll Twitter and see 16-year-olds building apps, and you feel like you already missed the bus.

At 30, you scroll LinkedIn and see 22-year-old "senior developers" with three years of experience, and you feel like you waited too long.

Both feelings are real. Both are misleading.

The 16-year-olds on Twitter are statistical outliers posted specifically because they are unusual. If every teenager could build production apps, nobody would write an article about it. The 22-year-old senior developer probably started coding at 14 and has a very different story than their job title suggests.

Your only relevant question is: can I learn to code, build projects, and become employable? The answer to that question does not depend on your age. It depends on your effort.

Time. You have it. If you start learning at 18 and spend a year on it, you are 19 with a year of coding experience. By 22, you have more practical experience than most CS graduates who just finished university. Time is your biggest asset. Do not waste it.

Energy. You can study for hours. Your brain absorbs new information faster than a 30-year-old brain (though the difference is smaller than people think). Late night coding sessions are physically easier when you are young.

Low financial pressure. Many 18-year-olds in Kenya are living at home with parents covering basic expenses. This gives you a runway that older learners do not have. Use it wisely.

What works against you at 18:

Discipline. Be honest. Are you going to study coding for 4 hours every day when your friends are on TikTok and WhatsApp? Self-discipline at 18 is hard. It is not impossible, but it requires more deliberate effort than at 30. A bootcamp or structured program helps because it imposes discipline externally.

Resources. Not every 18-year-old has a laptop or reliable internet. If your family cannot afford a computer, you need a plan to access one. Cyber cafes, school computer labs, community centres, or saving up for a used laptop.

Context. You may not have work experience or life experience to draw on. This makes it harder to build projects that solve real problems because you have seen fewer real problems. Focus on learning the craft first. The context will come.

Maturity. You know how to show up and do the work even when it is boring. You have held jobs, met deadlines, and managed responsibilities. This discipline transfers directly to learning to code.

Domain knowledge. You have worked in an industry. You understand business problems that 18-year-olds have never encountered. A commerce graduate at 28 who learns to code can build fintech tools that a 20-year-old CS student would not think of. Your past career is not wasted. It is context.

Motivation. You are not learning to code because it sounds cool. You are learning because you need a better income, a more fulfilling career, or both. That kind of motivation is harder to quit on than teenage curiosity.

What works against you at 25 to 30:

Financial obligations. Rent. Food. Family. You cannot study full-time for six months if you have bills to pay. You need a plan: savings to cover the transition period, a part-time job alongside learning, or a bootcamp with instalment plans that fits around your schedule.

Ego. Being a beginner again at 30 is humbling. You were competent in your previous career. Now you cannot centre a div. That emotional drop is real and it makes people quit. Accept the discomfort. It lasts three months, not forever.

Speed anxiety. You feel pressure to learn fast because you are "behind." This pressure causes people to skip fundamentals, rush through courses, and build nothing properly. Slow down. Six months invested properly beats twelve months of panic-learning.

No. But let us be realistic about the tradeoffs.

At 35+, you have deep domain expertise, professional networks, and life experience that younger developers cannot match. You also have more financial obligations, potentially a family to support, and less tolerance for low starting salaries.

The path that works best for 35+ career changers is usually hybrid. Learn to code while keeping your current income source. Build projects on evenings and weekends. Transition gradually, perhaps starting with freelance work or a part-time tech role before going full-time.

The tech industry itself does not have a hard age ceiling. Remote companies hiring from Kenya evaluate code, not birth certificates. Some of the most respected developers in open-source communities started their tech careers in their 30s and 40s.

What does get harder with age: starting at the very bottom of the salary ladder. A KES 35,000 per month junior developer salary is acceptable at 22 and difficult at 38 with a family. Plan your transition so you can skip the lowest-paid entry points, perhaps by freelancing at higher rates or leveraging your domain expertise to target mid-level tech roles in your industry.

Startup founders and technical leads in Nairobi generally do not care about your age. They care about three things:

1. Can you pass the technical interview?
2. Will you fit into the team?
3. Can you ship code reliably?

A 35-year-old career switcher who passes the technical test, communicates clearly, and has a portfolio of deployed projects will get hired over a 22-year-old with a CS degree and no portfolio. We see this happen regularly.

The only context where age can work against you is at companies that explicitly target "fresh graduates" for internship programs. These programs are designed for 21 to 24-year-olds and the salary reflects that. But you do not want those roles anyway. You want a position that values your full experience, not just your coding ability.

Remote companies are the most age-neutral. They never meet you in person. They evaluate your code, your communication, and your availability. Your age is invisible to the process.

The only wrong age to start a tech career is the age at which you decide not to start.

At 18, you have time but need discipline. Get it through a bootcamp, a study group, or a mentor.

At 25, you have some experience and some savings. Use both wisely. Give yourself six months of focused effort.

At 30, you have deep experience and strong motivation. Channel them into building things that combine your domain knowledge with new tech skills.

At 35+, you have everything except time to waste. Plan your transition carefully, build strategically, and leverage every advantage your years have given you.

McTaba Labs accepts students of all ages. Our youngest marathoners have been 18. Our oldest have been in their late 30s. The cohort is better for the mix. 26 weeks, 8 production-grade apps, the African Stack. KES 120,000 with M-Pesa instalment plans.

Whatever your age, the maths is simple. Six months from now, you will be six months older regardless. The question is whether you will also be a developer.