You can build a tech career with a non tech degree. Plenty of people working in software, data, product and support studied English, economics, biochemistry, law, mass communication or something else entirely. What employers need from you is evidence that you can do the job, and you can build that evidence yourself.
That does not mean a degree is irrelevant. Some employers filter by degree, and some roles (machine learning research, for example) lean heavily on maths. But for most entry routes, skills, projects and how you present them matter more than your course title. This guide explains how to choose a role, build credible proof and turn your degree into an advantage rather than an apology.
Do tech companies really hire people without computer science degrees?
Many do, especially for roles where practical skill is easy to test. A frontend developer can show a working website. A data analyst can show a dashboard. A QA engineer can show test plans and bug reports. Those artefacts often say more than a transcript.
Some organisations, including certain banks, government agencies and large corporates, still list specific degrees in their job adverts. You will meet those filters. The answer is to apply widely, use referrals where you can and target companies that judge skills directly.
Which tech roles suit your degree?
Your degree shapes how you think. Use that.
- Economics, statistics, maths or accounting: data analysis, business analysis, product analytics.
- Sciences (biology, chemistry, physics): data analysis, QA, and with extra maths, machine learning later. You already understand experiments and evidence.
- Engineering (non-software): backend development, DevOps, systems administration. You are used to systems thinking.
- English, languages, communications: technical writing, content design, product management, technical support.
- Law and political science: security governance and compliance, product management, business analysis.
- Psychology and sociology: user research, UX design, product management.
- Fine arts and design: UI design, frontend development.
These are tendencies, not rules. An English graduate can become an excellent backend engineer. What matters is how you think and what you enjoy doing all day. If you are not sure, take the free TechDNA assessment. It measures eight traits, including analytical reasoning, visual thinking and communication, and ranks your fit across nine roles.
For a broader view of the options, read our guide on which tech career is right for me.
How do you build tech skills without a tech degree?
You have three broad routes: teaching yourself, joining a bootcamp, or a structured course or programme. Each has trade-offs around cost, pace and accountability. Our guide on bootcamp vs self-taught vs degree compares them.
Whichever route you choose, the learning order is similar:
- Foundations. How computers, the internet and operating systems work. Harvard CS50 is a respected free option, and TechLearnX offers free foundation courses on computing, Linux, programming and Git.
- Core skills for one role. Use roadmap.sh to see what a role expects, and pick resources like freeCodeCamp, The Odin Project or Kaggle Learn.
- Projects. Apply what you learn to real problems.
- Professional tools. Git and GitHub, a code editor, and the specific tools your role uses.
Focus on one role. Spreading your time across five different paths is the fastest way to feel busy and make little progress.
How do you prove your skills to employers?
A degree is a signal. Without the "right" one, you need other signals.
Build a portfolio
Three solid projects beat ten tutorial copies. Each project should solve a clear problem, be explained in a short write-up and live somewhere public, such as GitHub or a personal site.
Connect projects to your degree
This is where a non-tech degree becomes an advantage. A pharmacy graduate who builds a medication reminder app, or an agriculture graduate who analyses crop price data, stands out. You understand the domain, and you can talk about real users.
Show your learning in public
Write short posts about what you are learning. Share projects on LinkedIn. Contribute to open source, even with documentation fixes. This builds a trail that recruiters can follow.
Use role challenges and assessments
Structured tests help you see gaps. TechDNA's role challenges are 20-question knowledge tests for a specific role and level, useful for checking whether you are ready before you apply.
How should you explain your degree in interviews?
Interviewers will ask, "Why tech, when you studied X?" Have a clear, honest answer ready. A good answer has three parts:
- What drew you to tech. Keep it specific and true.
- What you have done about it. Courses, projects, practice.
- How your degree helps. For example, a microbiology graduate might say their lab work taught them careful documentation and testing ideas systematically, which they now use when debugging.
Avoid apologising for your degree. You are not a weaker candidate. You are a candidate with a different background who has done the work.
What about NYSC and early career?
If you are about to start or are currently doing NYSC, the service year can be useful learning time, depending on your posting. Some corps members study in the evenings, build projects and look for tech-related places of primary assignment. A focused routine during the service year can give you a real head start.
Wherever you are, plan around the realities: unreliable power, the cost of data and sometimes limited laptop access. Download materials when you can, practise offline where possible and set a weekly routine you can keep.
Common mistakes non-tech graduates make
- Waiting for permission. Nobody hands out "approved to switch" letters. Start learning now.
- Thinking a certificate replaces skill. Certificates can help, but projects and practical tests matter more.
- Choosing a role only because it seems popular. Pick one that fits how you think and what you enjoy.
- Hiding the degree. Use it. Domain knowledge is valuable.
- Applying only to jobs that list "BSc Computer Science". Many roles are more flexible than the advert suggests, and many companies skip degree requirements entirely.
A simple first week
If you want to start today, try this:
- Day 1: Read about three roles that might fit your degree.
- Day 2: Take the TechDNA assessment and note your top role matches.
- Day 3: Look at the roadmap.sh page for your top role.
- Days 4 to 6: Start one free foundation course and finish the first module.
- Day 7: Write down a small project idea that connects your degree to that role.
It is a small start, but momentum matters more than a perfect plan.
Frequently asked questions
Can I get a tech job with a degree in arts or humanities?
Yes. Arts and humanities graduates work in technical writing, product management, UX, support, QA and software development. You will need to build technical skills and a portfolio, and your communication skills will often give you an edge.
Should I go back to university for a computer science degree?
For most entry-level roles, it is not necessary. A second degree costs time and money, and many employers will judge you on skills and projects instead. It can make sense for research-heavy roles or if you want deep theoretical grounding.
Will employers reject me because of my degree?
Some will, especially organisations with strict degree requirements. Many others will not, particularly companies that test skills directly. Apply widely, build referrals and let your portfolio speak.
Which tech role is easiest to enter with a non-tech degree?
Roles like technical support, QA and data analysis are often more accessible because the entry skills are easier to demonstrate. "Easiest" still means real effort, and the best role is the one that matches how you think.
Your degree does not decide your future in tech, but your skills and fit do. Take the free TechDNA assessment to see which roles suit you, along with course recommendations for where to start.