Tech career roadmap for Nigerian undergraduates — what to do in each year

University takes four to five years. That is a lot of time. Most computing graduates in Nigeria emerge from it with a degree, no portfolio, and no clear sense of which sub-discipline they want to work in. They then spend another two years post-graduation building what they could have built during school.

This roadmap is for students who would rather not do that. It is opinionated. Adjust the months and the technologies, but keep the rhythm.

100-level — pick a language, ship something visible

Your only job in your first year is to prove to yourself that you can build things. The lecture content is not enough. Pick one language — Python is the safest bet — and use it to build something every other person in your class can see. A website for your hostel block, a Telegram bot for your study group, a script that scrapes JAMB results. The actual project does not matter. The act of finishing it does.

Open a GitHub account in your real name. Push everything you write, even when it is bad. Future-you, applying for SIWES, will be grateful.

200-level — pick a direction, narrow your reading

By the start of your second year you should have a rough idea whether you lean toward building user-facing things (web, mobile, design) or data-and-logic things (data, AI, backend systems). It is fine to be wrong about this — the point is to pick something and go deep enough to feel whether it suits you.

• If web: get fluent in HTML, CSS, JavaScript, then learn React. Build three or four small projects before you touch any other framework.
• If data: get fluent in Python plus pandas, NumPy, matplotlib. Recreate analyses you read about online from public datasets.
• If systems / cybersecurity: get fluent in Linux, networking basics, and either Python or Go. Set up a home lab using free cloud credits.

Read one technical book a semester. Not a tutorial — a book. Books carry the kind of structured thinking that random YouTube videos do not.

300-level — get paid, even if it is small

The transition from "person who learns" to "person who is paid to learn" is the largest single career step you will make. It happens any time someone sends you money in exchange for code you wrote. The amount does not matter. The transition does.

Three paths, in order of how much they will teach you:

• SIWES placement at a tech company that actually ships products.
• Freelance work — start with friends and family, then move to platforms (Upwork, Fiverr) or local agencies once you can quote rates.
• Open-source contributions to a project used by real engineers. Slower payoff than freelance, but the references you build are gold.

See: how to land a SIWES placement that actually teaches you something.

400-level — build the one thing that demonstrates your range

Your final-year project is going to happen anyway. Pick a topic where the academic supervisor needs are met but the project itself is also a real product you would put on your portfolio. A few examples that have worked:

• A real-time analytics dashboard for a real Port Harcourt business
• A computer-vision tool that does something useful for a specific community
• A learning-management micro-platform for your faculty
• A working clone of a commercial product, with all engineering trade-offs documented

Document the build publicly. A LinkedIn post a fortnight, a final write-up at submission. Recruiters reading your CV next year will look this up.

500-level (or NYSC) — convert the work into a job

By now you should have: a GitHub history that goes back years, two or three projects you can explain in fifteen minutes, at least one paid engagement, and a small network of engineers who know your name. Job applications now stop being cold and start being warm.

• Apply to the companies your SIWES coworkers moved on to.
• Apply to the engineering teams whose engineers you interacted with in open source.
• Apply to the companies your final-year project lecturer recommends.

The single most useful CV signal at this stage is not your CGPA. It is "here is a thing I built and shipped." Lead with that.

What this roadmap is not

It is not a guarantee. Markets change. Some of the technologies I named will be replaced before you graduate. The point is the rhythm — ship early, narrow your focus, get paid, build something real, convert. Adapt the inputs.

Related: what actually gets a Nigerian tech grad hired