Portfolio Review Checklist: A Hiring-Ready Self-Audit

How to Use the Checklist

1. 1. Choose a target. Use a real role, client type, or application brief. “Good portfolio” is too vague.
2. 2. Mark blockers, evidence gaps, and polish separately. A broken password is not the same priority as inconsistent spacing.
3. 3. Record what you observed. “Project role appears after three screens” is more actionable than “story feels off.”
4. 4. Fix the smallest high-impact problem first. Recheck the flow after each meaningful revision.
5. 5. Ask another person to repeat the story back. Their interpretation is evidence about what the portfolio communicates.

Quick-Pass Stress Test

Ask a fresh reader to scan the homepage and first project page briefly, then hide the screen. Can they answer:

• Who is this designer, and what kind of role or work are they pursuing?
• Which project appears strongest or most relevant, and why?
• What did the designer personally contribute?
• What should the reviewer do next?

This is a comprehension stress test, not a claim about how long every hiring reviewer spends. If the answers are wrong, fix the hierarchy or language that produced the wrong interpretation.

Projects and Case Studies

• □ Each project states the problem, setting, team, timeline, constraints, and your specific role.
• □ The opening summary lets a reader decide whether the project is relevant before entering the full story.
• □ Major artifacts are connected to a decision; process images are not included only to prove that a method happened.
• □ Alternatives, tradeoffs, critique, or iteration show how the direction changed.
• □ Outcomes distinguish product metrics, research findings, delivery signals, and reflection.
• □ Shipped, unshipped, student, speculative, and confidential work are labeled accurately.
• □ Images remain legible without forcing a reviewer to decode tiny interface text.

Navigation and Orientation

• □ The homepage makes the portfolio owner, design focus, and strongest next click clear.
• □ Navigation labels are familiar and describe their destinations.
• □ A reader can move between projects without repeatedly returning to the homepage.
• □ The current page, link states, and interactive controls are visually identifiable.
• □ Desktop and mobile navigation remain keyboard accessible and do not hide content.
• □ Resume, contact, and external links work and do not require unexpected permissions.

Visual Design and Writing

• □ Type size, line length, spacing, and contrast support sustained reading.
• □ Headings describe the case-study idea, not just a process phase such as “Research.”
• □ Captions explain why a visual matters; nearby prose does not repeat the same sentence.
• □ UI mockups are consistent, high enough resolution, and shown at a useful scale.
• □ Motion supports understanding and respects reduced-motion preferences.
• □ Copy is edited for concrete nouns, active verbs, and accurate ownership.
• □ Project names, roles, dates, and outcomes agree with the resume and LinkedIn profile.

Technical and Accessibility

• □ Every public route loads without broken media, dead links, console-blocking errors, or placeholder copy.
• □ The site works with keyboard navigation and shows a visible focus state.
• □ Pages use meaningful titles, one clear H1, logical headings, landmarks, and descriptive links.
• □ Informative images have useful alternatives; decorative images are ignored by assistive technology.
• □ Text and meaningful interface elements meet the intended contrast target.
• □ Content reflows at narrow widths and remains usable at 200% zoom.
• □ Images are responsively sized; the primary above-the-fold image is not lazy-loaded by default.
• □ Forms have labels, understandable errors, and a clear success state.

Role-Fit Pass

Review the site one last time beside the actual posting or brief:

• The first one or two projects carry the strongest relevant proof.
• The portfolio names the capabilities the role requires only when the work supports them.
• Transferable experience is translated into the new context without hiding the career path.
• The requested artifact and file format are included.
• Private or password-protected work includes clear, tested access instructions.
• The resume, portfolio, brief, and interview story reinforce the same positioning.

For format decisions, use the hiring-ready portfolio packet guide.

Sources and Further Reading

Hiring practices vary. These sources support the audience, evidence, and format principles behind the checklist rather than a fixed project count or review time.

• Nielsen Norman Group: UX Hiring—Insights from a Design Recruiter — audience and hiring-process context.
• Nielsen Norman Group: 5 Steps to Creating a UX-Design Portfolio — purpose, format, curation, and case-study structure.
• W3C: WCAG 2.2 — the accessibility baseline referenced in the technical checks.