Spoke · Homepage patterns

UX portfolio homepage examples

The three homepage patterns recruiters engage with in 2026, ordered by frequency. Single-screen, grid-led, narrative. Operational annotation on what each pattern surfaces above the fold, what each requires the candidate to be confident about, and where each one tends to fail when implemented poorly.

Jamie Pow11 min readSpoke · Portfolio cluster

The 30-second recruiter scan

Recruiters spend between 10 and 30 seconds on a portfolio homepage before deciding whether to open a case study. The decision they're making is binary: pass this to the hiring manager, or don't. They are scanning for a small set of legible signals — seniority, named companies, specialism, contact mechanism — and missing any of them is enough to fail the screen.

Hiring managers, who arrive at the portfolio later in the process, behave differently. They open the homepage briefly, then go straight to a case study. The homepage matters less for hiring managers than the work itself. Which means the homepage's primary job is to survive the recruiter scan; the secondary job is to present cleanly to a hiring manager who's already decided to read.

The homepage is not where you tell hiring managers who you are. It's where you tell recruiters you're worth ten more minutes.

Three homepage patterns work consistently. Each suits a different kind of candidate and has different failure modes.

Single-screen homepage

The single-screen homepage is the most operational pattern. Everything fits above the fold on a 14-inch laptop. Name and role at the top, three to five case study cards with named companies in the middle, contact details at the bottom. No scroll required. The candidate's about page and any peripheral content live behind navigation.

Single-screen works exceptionally well for mid-level and senior candidates whose case studies do the heavy lifting. The constraint forces editorial discipline — anything that doesn't earn its place above the fold gets cut. The risk is that single-screen demands a level of restraint many designers find difficult; the temptation to add an animated headline or a design philosophy paragraph is hard to resist.

Single-screen failure modes: vague case study card titles that don't name the company or product; too many cards (more than five becomes a grid); empty space that reads as unfinished rather than confident. The single-screen homepage works when every element justifies its existence; when filler creeps in, the pattern collapses.

Grid-led homepage

The grid-led homepage leads with a visual grid of case study tiles. The candidate's name and role sit in a header strip; below, a grid of four to six visual tiles with named companies and project titles. This pattern works well for candidates with strong visual craft and recognisable shipped work.

Grid-led depends entirely on the visual quality of the tile imagery. Strong tiles — interesting compositions, real product screenshots, branded but not corporate — earn case study reads. Weak tiles — generic Dribbble-style mockups, isometric illustrations, abstract gradient backgrounds — actively damage credibility, because they signal a candidate who's prioritising portfolio aesthetics over product evidence.

The biggest grid-led failure is the absence of named companies and project titles. A grid of beautiful tiles without context reads as a Dribbble collection. Adding a one-line title and the named company under each tile costs nothing and resolves the failure. Candidates using this pattern should ensure the company name is visible on the grid without requiring a click.

Narrative homepage

The narrative homepage opens with a short paragraph — three to five sentences — articulating the candidate's specialism and point of view, then presents case study cards below. This pattern suits content designers, researchers, design strategists and senior candidates with a clear position on the discipline.

Narrative homepages live and die on the quality of the opening paragraph. Strong narrative paragraphs contain specific, verifiable claims: "I've spent eight years working on consumer fintech, mostly on the boundary between regulatory compliance and customer trust". Weak narrative paragraphs slide into mission-statement territory: "I believe great design solves problems and creates value". The first version is recruitable; the second is filler.

The test for whether your narrative paragraph works: would a recruiter scanning it understand your specialism and forward you to a relevant hiring manager? If yes, the paragraph is earning its place. If not, it should be cut and replaced with a single line of specialism signalling.

Patterns to avoid

Three patterns recur across portfolios that lose recruiters at the homepage scan.

The hero with a generic mission statement. "Designing meaningful experiences." "User-centred. Always." These statements communicate nothing about the candidate and consume the recruiter's first 5 seconds. Cut them.

Animated intros. Splash screens, loading animations, "scroll to enter" indicators. They delay content for performance rather than for content reasons. The recruiter's time budget doesn't accommodate decorative friction.

Homepages that hide case studies behind navigation. If the recruiter has to click "Work" to see case studies, the click costs you. The homepage should surface case study cards directly; navigation is for everything else.

The recommended above-the-fold stack

The above-the-fold stack

What to surface in the first screen

  1. Name and seniority signal. "Sarah Chen — Senior product designer — 8 years — Currently at Monzo".
  2. One-line specialism (optional). "Consumer fintech with a focus on first-time-use flows."
  3. Three to five case study cards. Each with named company, project title, one-line summary.
  4. Contact mechanism. Email or LinkedIn. Visible, not buried in footer.
  5. About link. Lightweight navigation to deeper context if the recruiter wants it.

This stack works across all three homepage patterns. The only variable is how it's visually composed.

For the full structural reference on portfolios at each seniority level, see UX portfolio examples. For the pre-publish operational pass, see the portfolio checklist. For case study structure inside the portfolio, see case study examples, the operational deep-dive companion. The portfolio guide is the pillar reference that ties everything together.

If you want a second pair of eyes on your homepage specifically — fast, paid review — independent reviewers on Fiverr can usually review a portfolio homepage in 24 hours for £30 to £60.

Frequently asked questions

What should a UX portfolio homepage include?

Above the fold: name, role and seniority signal, three to five case study cards with named companies and one-line summaries, contact mechanism. The recruiter scan is the constraint.

Should a UX portfolio homepage scroll?

Optional. Single-screen homepages work for mid and senior candidates. Scrolling homepages work when the candidate has a clear point of view to articulate. What fails is forcing the recruiter to scroll twice before seeing case study names.

Do UX portfolio homepages need a photo?

Optional and varies by region. Photos are common in UK and EU portfolios, less common in US. Presence or absence rarely changes recruiter outcomes.

Continue in the cluster