How to Build a UI/UX Portfolio That Gets You Hired in Nigeria

The Problem With Most Design Portfolios

I have reviewed hundreds of UI/UX portfolios from Nigerian designers. The pattern is almost always the same: a Behance page with three redesign concepts, all for foreign apps the applicant has never used, solving problems that do not exist for users they have never spoken to.

Hiring managers see through this instantly. A redesign of Instagram's interface tells me nothing about whether you can talk to users, synthesise research, make tradeoff decisions, or collaborate with engineers. It tells me you know Figma. That is table stakes.

Here is what actually gets you hired.

What a Strong Portfolio Contains

A Real Problem You Solved

Your best case study should document a problem you identified, research you conducted, decisions you made, and the outcome you achieved. It does not have to be a paid project. A student project where you interviewed 10 users in your neighbourhood about a payment app problem is more compelling than a polished Dribbble shot with no context.

Document the messy parts. Show your sketches. Show a design decision you made and why you rejected the alternatives. That is the work hiring managers want to see.

Your Process, Not Just Your Output

Every case study should answer five questions:

1. What was the problem and who had it?
2. How did you find out what was really going on?
3. What did you try that did not work?
4. What did you ship, and why that option?
5. What happened after — did it work?

If you cannot answer question 5 for any project, go back and pick a project where you can measure impact. Even something simple: "After the redesign, task completion time in user testing dropped from 4 minutes to 90 seconds."

Context About the Users

Nigerian users are not European users. Payment anxiety, low-bandwidth environments, multi-language households, distrust of new platforms, preference for WhatsApp over apps — these constraints shape design decisions. If your portfolio shows that you understand this, you immediately stand out from the 90% of applicants who design for an imaginary Western user.

Figma Skills That Actually Matter

Figma is the industry standard. You need to know it well enough that the tool disappears — meaning you spend your thinking time on the problem, not on figuring out how to make a component.

The specific skills that signal competence to hiring managers:

• Auto Layout. If your frames do not use Auto Layout, your designs will break the moment an engineer changes one word. Learn it until it is automatic.
• Component architecture. Build a small design system for every project. Even three components — a button, an input, a card — shows you think systemically.
• Prototyping for user testing. A prototype you can put in front of a real person and learn from is worth more than any static mockup. Know how to make interactions feel real enough for a usability test.
• Handoff. Inspect mode, spacing notes, naming conventions. Work as if the engineer receiving your file has zero context about your intentions.

Getting Your First Role

The fastest path to a first role in Nigeria is not job boards. It is building a real project for a real organisation — an NGO, a local business, a student union — and documenting it properly. Then reaching out directly to product managers and design leads on LinkedIn with a specific, short message that leads with the value of what you built, not with "I am looking for opportunities."

Three strong case studies and three direct outreach messages per week will get you further than 50 applications to jobs on Jobberman.