Full-stack Portfolio Examples

Short answer

What does a full-stack portfolio need?

Full-stack reviewers want one project you took all the way to production, not two halves that never met.

The underlying structure is the same for every role — one clear claim, two or three verifiable projects, a GitHub profile that supports them, and a CV that links to both. What changes for full-stack work is the emphasis, and which projects are worth featuring.

Worked examples

Beginner: One deployed project, documented properly

Second-year student. Three university assignments, no personal projects, nothing deployed. Applying for a first summer internship.

Alex Moreau — front-end developer
Second-year computer science student. I build web applications in TypeScript and React. Looking for a summer 2027 internship.

Projects shown: Module Deadline Tracker, Library Lending System.

The ten-second read. A second-year student who ships things and understands why concurrency matters. Worth a first-round conversation.

Read the full breakdown

Intermediate: Three projects with a consistent back-end story

Final-year student with a part-time support job. Several assignments and one side project. Applying for graduate back-end roles.

Priya Raman — back-end developer
Final-year computer science student. I build APIs and data pipelines in Python and Go. Available from July 2027.

Projects shown: Society Events Platform, Log Analyser, devkit.

The ten-second read. A final-year student with a clear back-end direction and evidence of engineering judgement, not just completed features.

Read the full breakdown

Projects that work for full-stack roles

Five briefs from the library that produce the kind of evidence full-stack reviewers look for:

Module Deadline Tracker — Coursework deadlines live across four different university systems, an email thread and a lecturer's slide. Students miss submissions they knew about a fortnight earlier. (1–2 weekends)
Recipe Cost Calculator — Students cooking on a budget have no idea what a meal actually costs per portion, so food shopping is guesswork and money disappears. (1–2 weekends)
Shared House Expense Splitter — Housemates track shared costs in a group chat and a note on the fridge. By the end of term nobody agrees who owes what. (2 weekends)
Spaced-Repetition Flashcards — Revising by re-reading notes is close to useless, and the good spaced-repetition tools have a steep learning curve for one module's worth of revision. (2 weekends)
URL Shortener with Analytics — You want short links you control, with click statistics, without handing your traffic data to a third party. (1–2 weekends)

Full specifications for these and the rest are on the full-stack projects page.