How to build a portfolio that recruiters in Port Harcourt actually open

Recruiters spend an average of 30 seconds on a junior developer CV. Of those 30 seconds, maybe 5 are spent clicking through to your portfolio. Most portfolios lose them in the first second. Here is what wins.

The five-second test

Open your portfolio in a fresh tab. Look at the screen for five seconds. Can you tell:

Who I am?
What I do?
What I have built?
How to reach me?

If a recruiter cannot answer those four questions in five seconds, you have lost them. They will not scroll. They will close the tab and open the next CV.

What to put on the front page

In this order, above the fold:

Your name + a one-line headline ("Backend engineer focused on Python and APIs" beats "Aspiring developer learning new things").
Two or three project cards — title, one-sentence description, screenshot, "View live" + "Code" links.
A short bio paragraph (three sentences max).
Contact buttons — email, LinkedIn, GitHub. Visible. Not buried in a footer.

Everything else can live below the fold. Education, blog posts, awards. Above the fold is for the elevator pitch.

The projects that work

A portfolio with three deep projects beats one with twelve shallow ones every time. Each project should answer:

What problem does it solve?
What did you build, in plain English?
What technologies did you use, and why those?
What is one thing that was hard and how did you solve it?
Where can I see it running, and where can I read the code?

A live URL is non-negotiable. Hosting is essentially free now — Vercel, Netlify, Render — and a portfolio without live URLs reads as "I cannot finish."

Projects that do not work

Skip these:

Tutorial clones with no original additions. Recruiters have seen the Todo app a thousand times.
Calculators, weather apps, tip splitters. Indistinguishable from any other junior portfolio.
Half-finished projects. If it is not deployed and the code does not compile, it should not be on your portfolio.
Three different versions of the same idea. Show range.

What recruiters in Port Harcourt actually look for

Three signals in particular:

Local context. A project built for a real Port Harcourt problem stands out from the global noise. A logistics tracker for keke drivers. A school-management micro-app for a local secondary school. A market-rate tracker for foodstuffs in Mile 1. These convert.
Real users. Even five real users is more impressive than zero. Write down how you got them.
Iteration evidence. Commits over time. Issues closed. README updates. Shows you can stick with something past v1.

The GitHub side

A clean, public GitHub matters more than the portfolio site itself for many engineering managers. Treat it as a portfolio in its own right:

Pin your three best repos.
Each pinned repo has a real README — what it does, screenshot, how to run, what you learned.
No "first commit" repos at the top.
Green squares help, but only the recent ones. A flat year does not help; consistent activity over the last three months does.

The technical writing edge

A single decent technical post on your blog — "what I learned building X," "why I picked Y over Z" — is the cheapest way to stand out. Most junior developers do not write. Recruiters notice the ones who do because they show two things at once: communication skills and a willingness to think in public.

Common mistakes

Skills lists that include everything. "HTML, CSS, JS, React, Node, MongoDB, Python, Django, Flask, AWS, Docker, Kubernetes…" reads as "I have done a tutorial on each."
Stock-photo hero images that have nothing to do with you.
Three-paragraph bios about your journey of self-discovery.
Animation libraries that delay the page-paint.
Hiding your full name. The recruiter needs to be able to search for you.

Iterate in public

Your portfolio is never done. The version you ship next month should be better than what is up today. The version you ship in six months should be unrecognisable. Get it in front of two or three senior engineers, ask what they would cut, and cut it.