SIWES placement in 2026 — what Nigerian students should know

The Students Industrial Work Experience Scheme is one of the few moments in your university journey where the institution actively gets out of your way and asks you to go learn from the working world. How you spend those six months can be the difference between starting your career at year zero and starting it two years ahead.

This guide is for students in their pre-SIWES year (typically 300-level for most computing programmes) who want to land somewhere that actually advances their career — not just a "letter signed" formality.

Why SIWES matters more than students think

Most students treat SIWES as something to survive. That instinct is wrong. The placement is the single largest formal stretch of professional exposure most Nigerian undergraduates ever get before their first full-time job. Six months is enough time to:

• Ship something real that you can show in an interview
• Build relationships with engineers who can refer you later
• Test whether the career path you assumed you wanted is actually for you
• Earn a small income, often for the first time

Students who use the six months intentionally graduate with a portfolio, a network, and a clear idea of which direction to push their final-year project. Students who don't graduate looking exactly like everyone else.

Where to look — beyond the noticeboard

Your faculty SIWES coordinator will give you a list. Use it, but don't stop there. The most useful placements rarely come through the formal channel. In order of return on effort:

• Local tech academies and bootcamps. Places that already train people to ship code are well-set up to mentor a SIWES student into shipping code too. SmartHub Academy in Port Harcourt is one example — students on placement here work on real client projects rather than fetching tea.
• Small product companies. A five-person startup will give you more responsibility than a 500-person company. You'll touch the codebase your first week.
• Agencies and consultancies. Agencies churn through many clients per year, which means six months exposes you to four or five different stacks rather than one.
• Direct outreach to engineering teams on LinkedIn. Cold outreach has a low hit rate, but the hit you do land is usually exceptional. Write to the engineering manager, not HR.

What to ask before you accept

A placement that wastes six months of your life is worse than no placement. Before you sign anything, ask:

• What will I actually be working on, week by week?
• Who is my technical mentor and how much time will they spend with me?
• Will I commit code to the production repo or work on a parallel sandbox?
• At the end of six months, what will I be able to put on my CV that I can't already?

If the answers are vague — "you'll learn a lot," "we'll figure it out when you arrive" — keep looking. The places worth your time have a real answer.

How to make the six months count

Whichever placement you land, three habits will turn it into a career accelerator:

• Keep a weekly log. Friday evening, write down what you shipped, what blocked you, and one thing you learned. By month six this is the rough draft of your CV bullets.
• Ask for code review on everything. Senior engineers reading your code, then explaining why they would have done it differently, is the single most valuable training you will ever receive. It is also free.
• Build one thing outside the office. A side project — even small — gives you something you fully own to show prospective employers. Your office work belongs to your employer; your side project belongs to you.

The SIWES financial reality

Most placements pay a stipend. Most stipends are small. Build your budget assuming N20,000–N50,000 a month and treat anything above that as a bonus. If the placement pays nothing at all and you can afford it, the right places are still worth it — but check whether the placement is genuinely teaching you something. Unpaid plus useless is a no.

Beyond the placement letter

At the end of six months, your university will ask for a logbook and an employer signature. Submit those. But also walk out with: a public GitHub commit history under your name, two references you can call by phone, and a story you can tell in 60 seconds about something you built. Those three things matter more in your career than your CGPA.

Related: a year-by-year roadmap for Nigerian tech undergraduates