Somebody messages us almost every month with a version of the same question. They're in their late twenties or early thirties, working in banking, or admin, or teaching, or sales — something stable, something their family is proud of, something that isn't tech. And they've decided they want to switch. Usually there's a specific trigger: a friend who "did a bootcamp and now works remote for a company in Canada," a YouTube video that made frontend development look approachable, a layoff scare that made the idea of "a skill I can sell anywhere" suddenly urgent. They want to know where to start.
We're going to answer that question honestly, which means telling you some things the bootcamp ads won't.
The Part Nobody Puts in the Marketing
The tech-transition industry — bootcamps, "learn to code in 3 months" courses, the entire ecosystem selling this dream — has a strong incentive to make the path sound faster and more certain than it is. That's not a conspiracy theory; it's just how selling a course works. The reality is less dramatic and more useful to know upfront: most people who successfully transition into tech in Nigeria take somewhere between one and two years from "decided to switch" to "getting paid to do this full-time." Some faster, plenty slower. Almost nobody does it in three months, and the people online claiming they did are usually leaving out the six months of prior self-study before the bootcamp, or the fact that "got a job" meant an unpaid internship, or that they had a technical friend quietly fixing their portfolio project the week before interviews.
We're not saying this to discourage you. We're saying it because the single biggest reason we've watched people quit this transition isn't that the material was too hard. It's that they expected a sprint and found themselves three months in, still confused by basic concepts, comparing themselves to a timeline that was never real to begin with.
Step One: Pick a Lane Before You Pick a Course
Here's where most people go wrong before they've even started — they pick a course before they've picked a direction, and end up half-learning three different things because "tech" isn't one skill, it's a hundred different jobs wearing the same trench coat.
Broadly, if you're coming in with zero technical background, three lanes tend to be the most realistic entry points in the Nigerian market right now: frontend web development (building the parts of websites and apps people interact with), data-related roles (data analysis, which leans more on Excel and SQL than programming, and is often underrated as an entry point because it's less crowded than "developer"), and product or project-adjacent roles (product management, QA testing, technical support) that need you to understand tech without necessarily writing code all day. Each of these has a different learning curve, different starting salary expectations, and a different amount of time before you're employable. Pick based on what you're actually good at already — if you were strong in structured, detail-heavy work, QA or data analysis might suit you faster than frontend development, which rewards a slightly different kind of thinking.
Step Two: Learn in Public, Not in Private
This is the piece of advice we'd put above almost everything else, and it's the one people resist most, because it feels exposing. Don't learn quietly for six months and then reveal a finished portfolio. Post what you're building as you build it — even the ugly, half-broken version. Ask questions in Nigerian tech communities (there are active, generous ones — Andela's alumni network, She Code Africa, various tech Twitter/X and WhatsApp communities built around Lagos, Abuja, and Port Harcourt tech meetups) instead of only searching Google and YouTube in isolation.
There are two reasons this matters more than people expect. First, the tech job market in Nigeria — like most places — runs substantially on referral and reputation, not just applications into a black hole. Being visibly present, asking good questions, helping other beginners once you're slightly ahead of them, puts you in front of people who will eventually mention you when their team is hiring. Second, learning alone means you don't know what you don't know. Someone slightly ahead of you will catch the misunderstanding that would otherwise cost you weeks.
Step Three: Build Something Real, Not Just Tutorial Projects
Every self-taught developer's portfolio has the same three projects in it — a to-do list app, a weather app, a clone of a well-known website. Recruiters and hiring developers have seen these thousands of times, and they signal "I followed a tutorial," not "I can solve a problem." What actually stands out, even from someone with six months of experience, is one project that solves a real, specific, slightly messy problem — ideally for a real person or small business, even if you're doing it for free or cheap at first.
We've hired people, and we know developers at other Nigerian companies who've done the same, on the strength of one genuinely useful project over a portfolio full of technically competent but generic tutorial clones. Build the booking system for your cousin's salon. Build the simple inventory tracker your uncle's shop actually needs. It'll be uglier than a tutorial project and worth ten times more on a CV, because it proves you can take an ambiguous, real problem and ship something that works.
Step Four: Get Comfortable With the Awkward Middle
There's a stretch in this journey — usually somewhere between month four and month nine, depending on the person — where you know enough to be dangerous and not enough to be useful. You can build small things but can't yet debug confidently when something breaks in a way the tutorial never covered. This is the stretch where most people quit, not because they've hit a wall they can't get past, but because they've lost the feeling of visible progress that carried them through the earlier, easier stuff.
If we're honest about what separates the people who make it through from the people who don't, it's less about raw talent than about who kept showing up during this specific, unglamorous stretch — the stretch with no visible wins, where the only thing moving forward is a slowly shrinking pile of things you don't understand yet. This is speculation based on what we've observed, not a rigorously tested claim, but it's consistent enough across the career switchers we've watched that we're comfortable saying it plainly: persistence through the boring middle matters more than which course or bootcamp you picked.
Step Five: Apply Before You Feel Ready
The last piece, and maybe the most counterintuitive one: start applying for junior roles, internships, and freelance gigs well before you feel ready. "Ready" is a moving target that keeps receding the more you learn — every new skill reveals three more gaps you didn't know existed, and if you wait until the gaps disappear, you'll wait forever. Apply when you can build something functional, even if you'd be embarrassed to show a senior developer the code behind it. The application and interview process itself — including the rejections — will teach you faster than another month of solo studying, because it exposes you to exactly what employers are actually looking for instead of what you assume they're looking for.
None of this is a shortcut, and we're not going to pretend it is. But it's a realistic path, walked by enough people we've watched do it — some through us, some through others in the Nigerian tech scene — that we're confident it works if you commit to the actual timeline instead of the marketed one. The people who make this transition successfully aren't usually the most naturally talented. They're the ones who picked a lane, showed their work, built something real, and kept going through the stretch where nothing felt like it was happening.
