Website, PDF, or Deck? Build a Hiring-Ready Portfolio Packet

A Useful Way to Plan the Portfolio Packet

Designers often ask whether they need a website, a PDF, or a deck. That question is too small. The real hiring problem is that different people review your work in different contexts. A recruiter scans for fit. A hiring manager looks for enough proof to move you forward. A design lead looks for judgment. An interview panel listens for how you defend decisions when the room pushes back.

One artifact may not serve all of those moments equally well. A useful way to plan is as a packet: a few connected pieces that tell the same story at different depths.

The point is not to create more busywork. The point is to make the same evidence survive handoffs. If the story changes every time someone opens a different artifact, the packet is not doing its job.

The 2-Minute Reviewer Stress Test

Before you redesign anything, run the packet through a deliberately fast two-minute pass. This is a stress test, not a claim that every reviewer spends exactly two minutes. Do not read it like the designer who made it. Read it like someone trying to decide whether to move you forward between meetings.

This is where a lot of portfolios fail. They may look polished, but the reviewer cannot quickly tell what role the candidate wants, which project matters most, or what decision quality the work proves.

AI, visual polish, and "strategic" positioning do not replace visible judgment, role fit, UI competence, and evidence. If those signals are missing, the packet will feel impressive and still fail the hiring review.

If Your Portfolio Was AI-Built, the Review Bar Is Higher

AI can help you build a portfolio faster, but it can also make the packet feel strangely generic: polished layout, familiar icons, safe gradients, and confident copy that does not quite prove anything. That matters in hiring because reviewers are not only judging whether the site looks finished. They are judging whether the work shows taste, ownership, constraints, and decision quality.

If the site feels AI-built, do not just ask the tool to "make it more unique." Run a critique pass on the decisions and make authorship visible. Start with the AI-built app diagnostic to name the exact design smells, use the vibe-coded app guide for the broader pattern, then use browser fluency for designers to check whether the interface actually holds up outside the canvas. For the career angle, read why polished AI UI is becoming cheap.

What To Send at Each Hiring Stage

The packet works when each artifact has a clear moment. Do not send everything at once just because it exists. Send the smallest set that helps the next reviewer understand your fit and move you forward.

1. Website: Discovery and Application

When no format is specified, a simple website is often the lowest-friction artifact to link, skim, revisit, and compare. It also reveals more than your project content: navigation judgment, hierarchy, loading discipline, accessibility, mobile behavior, and whether your taste supports comprehension. Some employers will ask for a PDF, deck, or another format instead; follow that request.

If you are not sure whether the homepage is earning the click, run it through the portfolio checklist tool before rewriting every case study.

2. Recruiter Brief or PDF: Forwardable Role-Fit Proof

A recruiter brief is not a second portfolio. It is a short, forwardable summary that helps someone outside your exact discipline explain why you are worth a deeper look.

Use it when the first reviewer may not be a design lead, when your work is under NDA, when the application asks for attachments, or when you want to make the handoff from recruiter to hiring manager easier.

The mistake is over-designing the brief until it becomes a worse version of the website. Keep it simple. Its job is to carry the signal, not replace the source.

3. Case Study: Deeper Judgment and Evidence

The case study is where the reviewer should understand how you think. Screens matter, but the hiring signal is in the choices: what you prioritized, what you ruled out, what constraints mattered, and what changed because of your work.

If the case study reads like a process archive, tighten it with the case study structure guide. The goal is not to show every artifact. The goal is to prove your decisions were grounded.

4. Interview Deck: Live Narrative and Discussion

The interview deck is the artifact most designers under-prepare. A case study is read alone. A deck is experienced live. That means it needs pacing, conversational room, and slides that support your story instead of swallowing it.

Follow the employer's brief for timing and scope. It is also useful to practice a focused 10–15 minute version that can expand or contract as questions change the room. For a deeper walkthrough, use the portfolio interview presentation guide.

What Has to Stay Consistent Across the Packet

Each artifact has a different job, but they should all point to the same hiring story. The packet fails when the website says one thing, the PDF says another, and the interview deck reveals a third version of the candidate.

Consistency does not mean flattening a multidisciplinary practice. Interaction, UI, research, service design, and product strategy roles may need different proof. Adapt the packet to the role while keeping your ownership and strongest evidence accurate.

Common Packet Mistakes

Hiring-Ready Packet Checklist

Use this as a menu, not a requirement. Check only the pieces that your application or interview process actually needs.

If you want a faster diagnostic, use the portfolio checklist tool. If the packet is for an upcoming interview, also review the interview presentation guide.

Sources and Further Reading

Hiring processes vary by company, role, level, and reviewer. These sources support the audience and format principles in this guide without turning any one format into a universal rule.

• Nielsen Norman Group: UX Hiring—Insights from a Design Recruiter explains why the first reviewer may not be a designer and why application materials must work for their actual audience.
• Nielsen Norman Group: 5 Steps to Creating a UX-Design Portfolio compares web, PDF, and slide-deck formats and recommends matching the format to the hiring context.
• Nielsen Norman Group: User Experience Careers report documents the importance of thought process, reasoning, evidence, and business understanding in portfolio review.