Can you get into tech from a non-tech degree?
Yes. Many working developers, designers, and product managers in Kenya do not have CS degrees. Tech hiring tests what you can do, not what you studied. If you can build a product, contribute to a codebase, or design an interface, employers will consider you. Your skills and portfolio get you the job.
Why non-tech graduates get hired in tech
Tech companies need more than programmers. They need people who understand the problems software solves. A business graduate who can code understands both the customer and the product. A journalism graduate who builds data visualisations brings storytelling to data. A law graduate who understands technology can work in compliance and policy.
Even for pure programming roles, skills matter more than the degree. A portfolio with three deployed projects proves more than a CS degree with no GitHub profile. Employers who hire based on demonstrated ability (which is most tech companies in Kenya) do not filter by degree subject.
The exception: some large corporations and government bodies require a CS-related degree for specific roles. For these, your degree title matters. For startups, agencies, and most private companies, your work matters more.
What to learn and in what order
If you want to work in tech from a non-tech degree, pick one path and go deep. Do not try to learn everything at once.
Web development (fastest to employability): HTML, CSS, JavaScript. Then a framework (React or Next.js). Build three websites. This path gets you freelance-ready in three to six months and job-ready in a year.
UI/UX design (if you think visually): Learn Figma. Study design principles. Build ten mockups for real products. This path requires no coding and leads to roles at agencies and product companies.
Data analysis (if you like numbers): Excel (advanced), SQL, Python basics, data visualisation. This path suits business and economics graduates who want to stay adjacent to their degree.
Product management (if you like strategy): No coding required, but understanding how software is built helps. Study product thinking, user research, and project management frameworks. Build side projects to understand the development process.
The semester coding plan works for non-tech students too. Adjust the pace to fit your schedule alongside your actual degree coursework.
Building proof that you belong in tech
Without a tech degree, you need stronger proof that you can do the work. Here is how to build it:
Projects. Build things. Deploy them. Link to them. A portfolio with real projects is the strongest evidence you can present. Each project is a conversation starter in interviews.
Contributions. Contribute to open-source projects, build tools for campus clubs, or volunteer tech skills at a local NGO. These demonstrate that you can work on real problems in real contexts.
Community. Join tech clubs and attend meetups. Being visible in the tech community introduces you to people who hire. Many opportunities come through connections, not job boards.
Certificates. Relevant certificates (Google, AWS, freeCodeCamp) add credibility to your CV. They are not substitutes for projects, but they complement them.
The combination of projects, community, and certificates builds a case that is hard for employers to ignore, regardless of your degree.
Your non-tech degree is an advantage, not a handicap
A developer who studied economics understands pricing models and market dynamics. A developer who studied communications writes better documentation and product copy. A developer who studied law understands data protection regulations. These are genuine advantages in a tech team full of CS graduates.
Do not hide your degree. Frame it as a strength. "I studied journalism and taught myself web development. I bring both storytelling and technical skills to product work." This is a compelling pitch that a pure CS graduate cannot make.
Tech teams benefit from different perspectives because products serve different kinds of users. Your non-tech background gives you a different lens on problems. Use it.
What to do this week
- Pick one tech path (web dev, design, data, product) that interests you and commit to it for this semester.
- Start one structured learning resource (freeCodeCamp, The Odin Project, Google UX Design certificate) this week.
- Build one small project within the next month and push it to GitHub.
- Join one tech community or club on campus to connect with students who are already in tech.
Frequently Asked Questions
- Do I need to transfer to a CS degree?
- No. Finish your current degree and build tech skills alongside it. Transferring costs time and money. You can reach the same destination by combining your existing degree with focused self-study and projects.
- How long does it take to become employable in tech?
- For web development or design, six months to a year of consistent study and building. For data roles, about the same. These timelines assume you are spending ten to fifteen hours per week on learning and projects. More time means faster progress.
- Will employers take me seriously without a CS degree?
- The ones worth working for will. Startups and product companies hire based on skills. If your portfolio shows you can build and ship, they do not care about the degree subject. Large corporations are more rigid, but even there, demonstrated skills open doors.
Related articles
Should you learn to code in first year if your course is not computer science?
Whether to learn coding in first year if you are studying a non-CS course at a Kenyan university. A clear verdict with a practical starting point.
Extra certificates during a degree: which add value in Kenya and which are noise
Which extra certificates add value during a degree in Kenya and which are noise. A ranked list for students who want credentials that employers notice.
Learning to code in first year: a semester-by-semester plan that fits around lectures
A realistic semester-by-semester plan for learning to code at a Kenyan university. Fits around lectures, works on any budget, starts from zero.