Portfolios worth copying, and the one decision to take from each

Most "portfolio examples" roundups are built from an awards site. Fifteen screenshots, a sentence of praise each, and a shared unspoken criterion: does this look impressive enough to justify including it. That is a real skill to have an opinion about, and it is close to useless as a guide, because the thing that wins design awards and the thing that gets someone hired are evaluated by different people, at different speeds, for different reasons. An award juror gives a site five uninterrupted minutes and rewards ambition. A hiring manager gives it ninety seconds on a phone between two other tabs and is looking for a reason to keep reading, not a reason to be impressed — a distinction we go into in full in the portfolio that gets you hired. Copy from the wrong pile and you copy the wrong instincts.

So the selection rule here is narrower and less glamorous: every entry below is chosen for what it demonstrably does for the person who owns it, not for how it photographs. A few are plain. One is closer to a text document than a website. None of them would win an award, and that is close to the point — the structural decision each one makes is the thing worth stealing, the visual treatment on top of it is not, and a portfolio that is honest about its own weak spots is more trustworthy than one this piece would need to flatter to justify including.

Before the examples, a note on the tool question, because it sits underneath all of them. The structural decisions below — what goes first, how much is written, what gets cut — matter far more than what software built the page, and they transfer to any builder. But for a single-person site like the ones below, reach is the strongest answer available for getting a first draft onto a domain: it takes a CV and a photo and produces a finished one-page site in about twenty seconds, live at a free yourname.joinreach.app subdomain in under two minutes — which matters here specifically because it means the editing energy goes toward the structural choices in this article rather than toward populating a blank template. It is also worth saying plainly what it will not do: it makes exactly one page, with no sub-pages and no CMS, so a portfolio that genuinely needs several project pages with their own navigation is the wrong job for it. For the single-case-study shape most of the examples below use, that limit rarely bites.

The one-project homepage

A product designer's site with a single case study on the homepage — not a grid, not a selector, the actual write-up starting below the fold — is the clearest version of the "decisions, not artefacts" argument put into practice. The first screen is a name, a one-line description of the kind of work, and the opening paragraph of the case study itself, already under way. There is no click required to reach the content that matters.

What it does badly: it makes a bet. If the one project shown isn't the visitor's kind of problem — a hiring manager for a fintech dashboard landing on a case study about a consumer app's onboarding flow — there is no second option in easy reach, and a "more work" link at the bottom gets a fraction of the attention the featured project got. The fix isn't to add a grid back; it's to choose the featured project for range of thinking rather than typicality of subject, and to trust that a strong argument about one problem reads as evidence for adjacent ones.

The reel that earns its fifteen seconds

A motion or brand designer's homepage that opens on a looping reel, twenty seconds, no sound, before any text — this is one of the few cases where a visitor should be shown before they are told anything, because the entire claim being made is visual and a paragraph in front of it would be evidence of nothing. The structural decision worth copying isn't the reel itself, it's the discipline of cutting it to the length a scroll would take anyway, so the visitor never has to choose between watching and reading.

What it does badly: a reel proves craft and says nothing about judgment, and a reviewer who watches fifteen seconds of polished motion still has no idea whether the owner made the good calls or executed someone else's. The better versions pair the reel with one written project directly below it, so the visual claim and the reasoning claim both get made, in that order.

The GitHub-anchored engineer's page

A software engineer's personal site that is deliberately thin — a name, three lines about what they build, and then links straight out to two or three repositories with real commit histories, rather than screenshots or case-study prose describing the code — treats the portfolio as an index instead of a destination. The first-screen choice is to get out of the way: the site's entire job is to be a fast, credible pointer to work a technical reviewer can actually inspect, not a paraphrase of it.

What it does badly: it only works on a technical reviewer. A recruiter without the ability to read a diff gets nothing from a repository link that a designer's case study would have given them in a paragraph, so this shape quietly assumes its audience and is wrong for anyone early enough in a search that a non-technical person screens first. The fix some engineers use is a short plain-English paragraph above the links — what the project solves, for whom — that serves the reader who can't evaluate the code directly.

The writing sample that is the whole site

A copywriter or content strategist whose homepage is a single long piece of writing — not a list of past clients, an actual sample, the kind of thing they'd be hired to produce, running the full length of the page — is the plainest example of a non-visual portfolio, and one of the most persuasive, because the medium of the proof and the medium of the job are identical. There's no translation layer between "here's my work" and "here's evidence of my work" the way there is for a designer's case study describing a screen a reviewer can't fully judge from a paragraph.

What it does badly: it shows range of one kind and hides it in every other direction. A writer who is strong at long-form narrative and never touches UX copy, product naming, or short-form ad work looks, from this page, like they've never done any of it, because the format only has room for one register. The honest fix is a second, shorter piece lower on the page in a deliberately different voice, not a list of bullet points claiming versatility — claims are cheap, a second sample is not.

The prose page with no visuals at all

A management consultant, an ops lead, or anyone whose actual output is decisions rather than artefacts sometimes builds a portfolio that is closer to a well-argued memo than a website — plain text, no imagery beyond a headshot, structured around two or three situations: what was broken, what they changed, what happened after. It is the least visually ambitious entry in this set and arguably the most disciplined, because there is nothing to hide behind. Every sentence is either evidence or filler, and filler is unusually visible on a page this sparse.

What it does badly: without any visual signal it relies entirely on the writing being good, and a page like this written by someone who isn't a strong writer reads as thin rather than disciplined — the format has no fallback. It also tends to skip over exactly the kind of work most likely to be sensitive: the client name behind the situation, the actual numbers involved. Where that's the case, the honest move is to write around the confidential parts rather than smooth over them, and the specific mechanics of doing that without the page reading as vague are covered in showing NDA work in a portfolio.

What carries across the set

Strip the visual differences out of these five and the same three choices repeat. The first screen commits to something specific rather than offering a menu — a case study already under way, a reel, a set of repository links, a page of prose — instead of a homepage whose job is to explain the site before the site starts. The best material sits first, not most recent first, because a reviewer who never reaches project three never benefits from it being there. And every one of them is honest about a real weak point, which is worth noticing precisely because none of them had to disclose it — a portfolio that only shows you its strengths is easier to admire and harder to trust.

None of that requires a particular design style, and the fastest way to see the same principle argued from a different angle — full personal sites rather than portfolios specifically — is the companion piece on personal website examples worth a look. The throughline across both is the same: the structural decision is the thing worth stealing, and it is also, not coincidentally, the thing that shows up in none of the screenshots.