Kenyan Developer CV vs Portfolio: What Wins?

The Question Every Kenyan Developer Asks

When you apply for a junior developer job in Kenya, what should you send: a CV or a portfolio? It is the wrong question. You should send both — but they play completely different roles, and most applicants get that backwards. The CV gets you screened; the portfolio gets you hired. Hiring managers use the CV to decide whether to reject you and the portfolio to decide whether to call you. This guide explains how to win at each stage.

It builds on the ultimate portfolio guide, which covers building the portfolio itself. Here we focus on the comparison: what recruiters actually look at, and how to avoid the mistakes that kill applications.

What Recruiters Actually Read

The uncomfortable truth is that your CV gets about six seconds of attention the first time through. Recruiters scan for three things in that window:

Role-relevant experience — has this person done anything like the job?

Concrete numbers and outcomes — not "worked on projects" but "cut page load time by 40%."

Signals of reliability — clear dates, no gaps that look unexplained, correct contact details.

Everything else — fonts, colors, fancy templates — is noise. A clean, one-page CV in a plain format beats a two-page design masterpiece every time.

What the Portfolio Does That the CV Cannot

A CV is a claim; a portfolio is evidence. Anyone can write "proficient in React" on a CV. A portfolio proves it by showing the projects, the code, and the decisions behind them. This matters extra in Kenya, where hiring managers often face hundreds of applicants for a single junior role and need a fast way to separate real builders from paper applicants.

The strongest portfolios show three things:

Deployed projects — links that actually load, not screenshots or PDFs.

Readable code — a GitHub profile with clean, committed, documented work.

Process — short write-ups explaining why you built something the way you did.

The developer portfolio guide walks through each. Notice that none of these require you to be senior — juniors who can show real deployed work are rare and valuable.

The Mistake That Kills Kenyan Applications

The single biggest application killer we see is the "summary paragraph" CV that describes skills but shows no evidence — plus a portfolio that links to broken or unresponsive projects. Together they say: someone who describes work but cannot ship it. Fixing this is simple but takes discipline: before you apply anywhere, deploy one clean project, test the link on a phone, and put it first on the CV.

How They Work Together

Use the CV to make the screening pass, and the portfolio to win the interview. Concretely:

The CV leads with a one-line summary: "Junior full-stack developer; 3 deployed MERN projects" — not a paragraph of adjectives.

Every bullet with a number, and every project on the CV links to its live URL or repo.

The portfolio is linked from the top of the CV — always clickable, never a QR code that fails to scan.

This exact strategy is what our talent team looks for when vetting developers for client placements: evidence over claims, every time.

A Practical Checklist Before You Apply

[ ] CV is one page, plain formatting, no typos

[ ] Each bullet states an outcome with a number where possible

[ ] Top three projects are deployed and tested on mobile

[ ] Portfolio links work from the CV, and from a fresh browser

[ ] GitHub profile is clean: sensible README, no node_modules committed

When your portfolio is solid, the next hurdle is the interview itself. The technical interview prep guide covers the questions Kenyan employers actually ask, and how to get hired as a junior developer maps the full process from application to offer.