Student Portfolio Examples: We Opened Every One the Lists Cite

Search for student portfolio examples and you get lists of 18, 47, 10. The lists cite each other. Almost nobody clicks the links.

We did. Fifteen addresses from the two pages ranking first and second for this search, opened on 9 September 2026. Five did not load at all. Five belong to people whose own sites now describe them as employed professionals. Four are still student portfolios you can learn something from, and one does not say either way.

That gap matters, because a student copying a list is usually copying the polished page of somebody with four years of client work.

What happened when we opened every example

None of the lists mentions any of this. One of them carries a 2026 update date.

The dead links are worth a sentence on their own, because they tell you something about where to put a portfolio. A domain lapses when somebody stops paying for it, usually after graduation, when the address on every résumé they sent out stops answering. If you are choosing where your work lives, choose the thing that survives you forgetting about it.

The four still worth opening

Chosen for what they teach rather than for polish. Three are current students or recent graduates, one does not say, and each gets one thing right that the rest of this list gets wrong.

asmaa.dev handles the work it cannot show

The headline is a claim about output: "Building intelligent systems that turn data into decisions." Asmaa Abdul-Amin is partway through a data science degree and interning at the Johns Hopkins Applied Physics Laboratory, and the site says so plainly.

The part to copy is what happens on the project nobody is allowed to see. Instead of skipping it or vaguely gesturing at it, the page states that "detail here is limited to publicly released material" and moves on. The other projects carry the problem and the approach in writing.

Contact details go as far as a phone number. You may not want to publish yours, but the principle holds: somebody impressed by the page should not have to hunt for the way to say so.

kaylapadilla.org says what it is in the first sentence

"Graduate of USC's Master of Science in Entrepreneurship and Innovation program and UPenn alum, passionate about a career in tech, sports, and music."

Not elegant. Completely clear. Ten seconds on that page and you know the field, the level, and roughly what they want next, which is more than most portfolios manage in a full scroll.

Email and social links are open, and the site keeps Projects, Resume and Resources as separate sections rather than mixing everything into one feed.

timdp.ca commits to a category

"Designing for the physical and digital world," then thirteen pieces of industrial and digital design behind a filter, with an email in the header.

The filter is the interesting decision. Splitting physical from digital lets one portfolio serve two audiences without either of them wading through work they did not come for. If your output genuinely spans two fields, that beats apologising for the mix in an about paragraph.

What it does not do on the overview is tell you anything about any piece. You get an image and a title, so the writing has to be waiting behind the click.

vivek9patel.github.io is the interesting failure

The whole site is a working replica of an Ubuntu desktop. Windows, taskbar, settings, the lot. It is genuinely impressive, and as a demonstration of front-end skill it does more than any list of frameworks would.

It also opens on a lock screen. Before learning what Vivek Patel studies or has built, a visitor has to work out that they need to interact with a fake login. A recruiter with forty tabs open may not.

Worth copying: build one thing that proves the skill instead of listing the skill. Worth avoiding: putting that thing in front of the information a visitor came for. The same build with a plain first screen and the desktop one click in would lose nothing.

The five that grew up

Devansh Gandhi's site now opens "I'm Dev! Designer at Toast. Previously at Duolingo, DoorDash, and Meta." Sissi Wu's introduces "a User Experience Researcher with over 4 years of in hands experience in mixed-method research." Cristina Clerici holds a doctorate and works as a senior policy analyst. Nathan Koch has been an interaction designer since 2022. Isabel Ngan is a service designer at Accenture Song.

These are good portfolios. They are also the answer to a different question than the one you searched for. What you are looking at is what a portfolio becomes after several years of paid work, and the case studies that make it work are case studies about shipping products to millions of users.

Copy the structure by all means. Do not measure your coursework against a Duolingo project and conclude you have nothing to show.

One small thing to take from them, in the opposite direction: two of the five still have template placeholder text sitting in the footer, in one case the words "Your Custom Text Here". If that survives four years and a job at a recognisable company, it will survive on your page too, so check yours.

Three habits the good ones share

They say what they are in the first sentence. Field, level, direction. The portfolios that make you scroll to find out what somebody does are the ones you leave.

They are reachable. An email in the header or the first screen, not only in a contact page nobody opens. Five of these fifteen cannot be contacted at all right now, which is a strange thing for a job-seeking document to be.

They explain at least one piece in writing. The image proves you made something. The paragraph proves you decided something. For a student with no client roster, the second one is the entire pitch.

Showing work when there is no client work

This is the actual student problem, and the four portfolios above answer it three different ways.

Name the constraint and treat it as part of the story. A brief with no budget, no photographer and two weeks is a harder problem than one with all three, and saying so turns a small project into evidence of judgement.

Say what you are withholding rather than hiding the gap, the way asmaa.dev does with its restricted project. "I cannot show this, here is the problem it solved" reads as professional. A missing project with no explanation reads as a thin portfolio.

Build one real thing for a real situation. A local shop with no website, a friend's event, a tool you needed yourself. One genuine piece with a written outcome beats five course exercises, and it beats a redesign of a famous app that every reviewer has already seen a hundred times.

The portfolio walkthrough has the four lines to write per piece, if you want the format rather than the argument.

What kills it in the first five seconds

Placeholder text anywhere. "Street Address / City, State, Zip" in a footer says nobody has read this page since the template was chosen.

A first screen that does not say who you are. Whether the cause is an interactive gimmick or a bare name in a large typeface, the cost is the same.

No visible way to make contact. It is the one thing a portfolio has to do, and it fails more often than any design problem on this page.

An address that stops answering. Five of fifteen, on the day we checked.

Check this yourself

The two lists we worked from are SiteBuilderReport's 47 examples and Colorlib's 18. Open them, click through, and see what answers today. Our numbers are from 9 September 2026 and they will drift, which is exactly the point: a portfolio is a live thing at a live address, and being reachable is a feature you keep paying attention to.

Frequently asked questions