How to Switch into Tech in Nigeria
By Yemi Ogundairo on
If you have been thinking about how to switch into tech in Nigeria, the noise around you is probably loud. LinkedIn is full of "I learned to code in 3 months and now earn $5,000 a month" posts. Twitter is full of bootcamp ads. YouTube tutorials promise to teach you anything in under an hour. The truth, the one nobody seems to want to say out loud, is that switching into tech in Nigeria is doable and it works, but the path is longer and more deliberate than the highlight reel suggests.
This is a realistic 12-month roadmap, built from what we see actually working with people in our cohorts and our hiring partner network across Lagos, Abuja, Ibadan, Port Harcourt, and increasingly Ogun State.
Why "I want to switch into tech" needs a real definition first
Saying "tech" in 2026 covers everything from designing a mobile app interface to securing a bank's database. The first thing you owe yourself is a clearer answer to the question: tech doing what?
The four broad tracks that hire consistently in Nigeria right now are:
Product Design (UX/UI design): figuring out how software should look and feel before it gets built
Frontend Engineering: building the visible parts of websites and apps (React, Next.js, mobile)
Backend Engineering: building the invisible parts (APIs, databases, business logic)
DevOps and Cloud: keeping the infrastructure that runs everything alive and scaling
You can branch into Product Management, Data, Cybersecurity, and Machine Learning later, but those four are where the local job market has the deepest demand right now, and where junior salaries actually exist.
Before you spend a single hour learning anything, sit with yourself for an honest hour:
Do you enjoy how something looks and feels, and want to influence that? Product Design.
Do you light up when you see something visual come alive on a screen because of code you wrote? Frontend.
Do you find logic puzzles and systems thinking satisfying, and you don't particularly need to see the interface to feel rewarded? Backend.
Do you like the idea of automation, reliability, and infrastructure? DevOps.
If you are unsure, our Tech Training Programmes start with a foundation week designed specifically to help you pick the right track based on your actual aptitude, not just vibes.
Month by month: how to switch into tech in Nigeria in a year
This is the rhythm we see working. It assumes 12 to 15 hours per week (think two weekday evenings plus most of a Saturday). You can compress it if you have more time, but you cannot meaningfully expand it past 25 hours per week before diminishing returns set in.
Months 1 to 2: Foundations
This is where most people quit, and where most "Learn X in 60 minutes" videos do you a disservice. Spend these two months on:
The how-the-internet-actually-works fundamentals: DNS, HTTP, what a browser does, what a server is, what an API is, what a database is. You do not need to be deep, you need to be unconfused.
Your tools: VS Code, terminal basics, Git, GitHub. Get fluent enough that they fade into the background.
One foundation language for your track: HTML and CSS for design and frontend, Python or JavaScript for backend, Linux fundamentals for DevOps.
The mistake here is jumping straight into React, or Figma component libraries, or Kubernetes, before the underlying ideas are settled. You will move faster in months 3 to 6 if you slow down in months 1 to 2.
Months 3 to 6: Production-quality skills in one stack
This is where the track choice from month 1 starts paying off. Pick your stack and go deep:
Product Design: Figma, basic interaction design, design systems, accessibility, user research methods, end-to-end case study practice
Frontend: React, TypeScript, Tailwind or vanilla CSS, state management, API integration, deployment to Vercel or Netlify
Backend: Node.js or Python, Express or FastAPI, PostgreSQL, REST and GraphQL APIs, authentication, basic deployment
DevOps: Linux, Docker, CI/CD, AWS or Azure basics, infrastructure as code (Terraform), monitoring
The objective in this phase is not to memorise documentation. It is to build three small projects from scratch that you would not be embarrassed to show a hiring manager. For design, that's three end-to-end case studies. For engineering, that's three deployed, working applications with code you wrote and can defend in an interview.
Months 7 to 9: One substantial portfolio project
Skip the to-do app. Build something a real person could use:
A Nigerian-context tool: a savings tracker that integrates with Mono, a vendor directory for your local area, a tutor-finder, a logistics quote calculator
A clone with a twist: rebuild a familiar product but add one feature it does not have
A contribution to an existing open-source project, ideally one that has Nigerian or African maintainers
This is the project that hiring managers will actually look at. Most candidates have three half-finished side projects. The candidate with one polished, deployed, defendable project wins.
This is also where structured programmes earn their fee. [Our sponsored cohorts](/cohort-4) pair you with industry mentors for exactly this phase, because shipping a real project alone is harder than building one with a senior engineer reviewing your code weekly.
Months 10 to 12: Job hunt, applications, interviews
Most career switchers underweight this phase and treat it as an afterthought. It deserves three full months because:
Writing a CV that survives a Nigerian tech recruiter's 30-second scan is a learnable skill
Building a LinkedIn profile that gets you found is a learnable skill
Interview practice (technical screens, take-home tests, behavioural rounds) needs reps
Salary negotiation in the Nigerian market has its own quirks (Naira vs USD comp, equity literacy, remote vs local roles)
The portfolio piece almost everyone gets wrong
Your portfolio is not a list of projects. It is a story about how you think.
For design, this means: case studies that walk through the problem, the constraints, what you tried, what failed, and what shipped. Not just final-screen screenshots.
For engineering, this means: a GitHub profile where the README of every repository tells a reader in 30 seconds what the project does, how to run it, and which decisions were intentional. Not a graveyard of forks and abandoned tutorials.
You are not selling skills. You are selling the way you think under constraint. A hiring manager who reads a thoughtful case study or a well-written README will trust you to figure out a problem they cannot themselves describe yet.
Salary expectations, honestly
This part is awkward to write but more useful than the alternative. In Lagos in 2026:
Junior local-market roles (NGN paying companies, mostly): roughly NGN 300,000 to NGN 800,000 per month for design, frontend, and backend juniors with 6 to 12 months of experience or a strong bootcamp portfolio
Mid-tier local startups paying in USD: $700 to $1,500 per month for a strong junior to mid candidate
International remote roles: $1,500 to $4,000 per month for a mid-level engineer or designer, often higher for senior
These ranges shift fast. The number is less important than the path: most successful career switchers we see start at a local company for the first 12 to 24 months to get production experience, then move to USD-paying or remote roles once they have shipped real work.
Common failure modes when you switch into tech in Nigeria
The career switchers who do not make it usually fail for one of five reasons:
They never narrow down a track. Six months of "learning everything a little" beats nobody. Pick one, go deep.
They consume tutorials instead of building. A finished, deployed, bad project is more valuable than five tutorials watched.
They give up at the dip. Months 4 to 6 are unglamorous. Push through.
They learn in isolation. Without feedback from a senior, you reinforce your own bad habits.
They stop after they "know enough" but never deploy. Code on your laptop helps no-one. Deploy everything, even ugly versions.
When a structured programme makes sense
You can absolutely teach yourself tech in Nigeria. People do it every day. A structured programme is worth the cost (or the commitment, if it is sponsored) when:
You have tried self-learning for 2 to 3 months and have not maintained momentum
You are switching from a non-tech background and do not have a peer group already in the industry
You need accountability and live feedback, not just video courses
You want a shorter ramp to "ready to be hired" because of your financial timeline
Our Cohort 4 sponsored programmes are designed specifically around the month 3 to 9 part of this roadmap: foundations, stack depth, mentor-reviewed portfolio project. Tracks open for 2026 include Product Design, Product Management, Frontend Development, Backend Development, DevOps Engineering, and Cybersecurity.
The next step, whatever your path
If you are starting from zero today, this is the order:
This week: pick a track using the questions in the first section of this post
This month: commit to 12 to 15 hours per week and find a small accountability group
Next 3 months: ship something small and post about what you learned, publicly
Beyond: keep shipping, keep narrowing, keep showing your work
If you want a structured version of months 3 to 9 with mentorship and a portfolio project at the end, applications for Our Next Sponsored cohort are open. If you are not sure yet whether structured learning is for you, our team is happy to do a 20-minute call to help you think it through. Reach out and let's talk.
The path from zero to first tech job in Nigeria is roughly 12 months of consistent, focused work. Not 3 months. Not 5 years. The people who treat the timeline honestly and stop looking for a shortcut are the people who land the role.