I reviewed 47 portfolios this month. Here are the 5 patterns hurting every single one.
By Penguin — Founder, Penguin The Portfolio Builder
I run Penguin, a service that builds done-for-you portfolio websites. Over the last month I personally read 47 portfolios that came across my desk — applicants for our case-study reviews, free critiques I offered on LinkedIn, and the homepages of designers and developers who DM'd me cold. Most of them were technically fine.
Clean. Responsive. Modern fonts.
No broken images. And almost none of them would get the person hired. Here are the 5 patterns I saw on nearly every single portfolio that's hurting them right now — and what to do instead. 1.
The Wall of Skills You know the section. Twelve logos arranged on a grid. React, Node, TypeScript, Figma, Tailwind, Docker, GraphQL, MongoDB, Postgres, AWS, Jest, Git.
Sometimes there's a percentage bar next to each one. Tailwind: 87%. What does that mean?
Why it fails: A recruiter who's scanned 200 portfolios this week sees this and feels nothing. Logos prove you've heard of a tool. They don't prove you can ship.
Worse — a senior hiring manager reads "React 95%" and thinks no it isn't, because nobody's React is 95%, including mine. What to do instead: Move the skills wall to the footer. Or delete it.
Put a single line at the top of your portfolio that names the role you want and the outcome you produce. Then prove it with two or three case studies that show you doing that exact thing. Example, for a pharmacist transitioning into medical writing: Clinical pharmacist now writing CME content for medical education companies.
Three published articles, two ongoing retainers. Examples below. Fifteen words.
No grid. No percentages. The reader knows what you do and what comes next. 2.
The CV in a Webpage This one is the most common. The portfolio is structured exactly like a resume: header → summary → "Experience" with bullet points → "Education" → "Skills". Why it fails: If your portfolio is just a prettier resume, the reader's question is why am I reading this instead of the PDF you also attached?
Portfolios exist to do something a CV can't: show work. What to do instead: Lead with one project. Not a list of projects — one.
Give it a name, a one-paragraph context, a screenshot, and a short outcome. Then below, three more. The structure is Hero → Best Case Study → 2-3 Supporting Cases → About → Contact.
Notice what's missing: no "Experience" list. Your work is your experience. Job titles belong on LinkedIn. 3.
The Forgotten Case Study Half the portfolios I see have a "Projects" section. The reader clicks one expecting…