How to Present a Digital Portfolio (What Hiring Panels Actually Say)

Every week someone asks me a version of the same question: "Do I present my portfolio site, or do I build a deck?" So I went digging through what people who actually sit on hiring panels say — Reddit's design communities, Blind threads from designers and engineers inside big tech, Exponent's interview coaching, and a few recruiter interviews. Here is the consensus, organized so you can act on it this week.

Nothing here is my opinion dressed up as research. Where a point came from a specific thread, the link is right there so you can read the room yourself.

Format and tools

• Use a slide deck, not a live website. Present with a dedicated deck. As one designer put it, "presenting a website comes off as extremely underprepared."
• Deck first, design file second. Support the deck by walking the panel through your working design file near the end, to show variations, concepts, and how you organize your work. (r/UXDesign)
• Avoid static-only PDFs for interactive work. PDFs handle motion badly and GIFs will not render, so PowerPoint, Keynote, or Google Slides is safer. (r/graphic_design)
• Live sites read as unprepared in formal rounds. A hiring manager on Blind said scrolling through a portfolio site "will come across badly" next to a deck built for the room. (Blind)
• Build in Figma if you want interactivity on hand. Some candidates build the deck itself in Figma so clickable prototypes are one click away. (Blind)
• Check company tooling norms first. Candidates flagged that some companies (Amazon came up specifically) restrict PowerPoint for walkthroughs. Ask your recruiter instead of assuming. (Blind)
• Bring a skeleton deck even to "informal" screens. When a recruiter frames the call as a conversation, a lightweight deck still gives you a spine and stops you from freezing. (Blind)

Structure and timing

• Keep case studies concise. In a 45-minute slot, target roughly 10 minutes per case study rather than 15: business context, the user or business problem, impact, then how you solved it. (r/UXDesign)
• Deck content is not website content. Do not read your online case study word-for-word. One idea per slide, and do not linger. (r/UXDesign)
• Lead with problem, then contribution, then impact. Name the problem, your specific contribution, what collaboration looked like, and how you explored the space. (r/UXDesign)
• Separate the screener deck from the onsite deck. Keep the portfolio site brief and interest-piquing; save the deep case-study decks for later rounds. (Blind)
• Match the format to the panel. Some design orgs run one 45 to 60 minute session with everyone who will later interview you, partly so the panel can judge presentation skill directly. (Org Design for Design Orgs, reader notes)
• A reusable structure for writing and content roles: intro, then challenge plus collaborators and KPIs per project, then content strategy and research rationale, then the actual screens and copy with short reasoning, then results, then what you would change. (Blind)

Visuals and interaction

• Make slides visual, not text-heavy. Panelists should be looking at supporting visuals while you narrate, not reading paragraphs. (r/UXDesign)
• Screen-record motion and interaction. Capture interactive work as a recording and embed it rather than demoing live. (r/UXDesign)
• Keep layouts consistent slide to slide. When elements stay put, the audience listens instead of re-orienting. (r/UXDesign)
• Invest real time in polish. Low-resolution or dated visuals are one of the fastest ways to lose credibility; senior candidates often spend as long on presentation as on the work. (Dribbble)

Delivery and narrative

• Build in plot twists. Show the wrong turns, the constraint that upended the plan, the moment the data surprised you. (r/UXDesign)
• Practice until it is automatic, then slow down. Rehearse each slide until you know roughly what you will say, and speak slower than feels natural. Some people practice at 0.75x their normal pace. (r/UXDesign)
• Show, do not just tell. Recruiters are more persuaded by thinking demonstrated through the work than by a list of skills described afterward. (Dribbble)
• Drive the room. Come with a plan to steer the conversation. Pause to check in or ask the panel a probing question instead of lecturing. (r/UXDesign)
• Close with a forward-looking question. Ask where, based on what they saw today, they think you could add the most value. It signals confidence and gives you real signal back. (r/UXDesign)
• Have a why for every visible decision. Panels probe why you made a visual, interaction, or structural choice, not just what it was. (Blind)

Handling questions and interruptions

• Set expectations up front. Say whether you want questions as you go or at the end, and put a "Questions?" slide after each project so interruptions have a landing point. (Blind)
• Answer the question that was actually asked. If a panelist jumps ahead, answer where they are and then bridge back. Dragging them back to your script compounds the confusion. (Blind)
• Keep answers tight under pressure. Favor short, direct answers plus an offer to go deeper. Rambling through interruptions reads as losing the room. (Blind)
• Read interruptions as engagement. Frequent questions usually mean the panel is invested in that slide, not that you are failing.

Content selection

• Show fewer, stronger case studies. Two or three, not a tour. Pick your most complete stories. (r/UXDesign)
• Start with the result, then show process. Open with the outcome, then walk backward through how the brief became that result. (r/graphic_design)
• Tailor the intro to the company. Use the opening to say why this company and this role. A generic intro wastes an easy point. (r/UXDesign)
• Anchor the deck with one large project. Choose something substantial enough to show the full arc, ideally where you helped shape strategy, and let a smaller project cover a skill the main one did not. (Exponent)
• Reusing a project across rounds is usually fine. Candidates confirmed with recruiters that the same case study can appear in a screen and again onsite, since audiences differ. Confirm rather than assume. (Blind)
• Credit team work honestly. Be explicit about your contribution and your title at the time. (SlideShare)

Field-specific notes

Product and UX design

A widely cited entry-level structure: introduction, then one large project covering the full process end to end, then an optional smaller project highlighting a specific skill. (Exponent)

Data science and analytics

Favor two or three deep projects over many shallow ones, each showing a different skill: cleaning, modeling, storytelling or deployment. Hiring managers rarely read your code line by line, so the write-up carries the weight. (Data science portfolio guide) Frame each project as a case study rather than a code dump, and prefer original or less-common datasets over the overused ones. (Built In)

UX writing and content strategy

Writing samples have less visual punch than UI screens, so structure the presentation around narrative: challenge, audience and tone research, the copy with short rationale, metrics, reflection. (Blind)

Practical extras

• Prepare for either format. Build the deck and get comfortable presenting from a live site, since expectations vary by company and even by interviewer. Treat a mismatch as a fit signal, not a personal failure. (r/UXDesign)
• Elevate with high-quality mockups. Strong mockups or photography meaningfully change how the same work reads. (r/graphic_design)
• Bring something physical to in-person rounds. One designer was advised to bring a tactile 3D concept rather than only screen visuals. (r/graphic_design)
• Read the room on "walkthrough" versus "presentation." If the recruiter wants conversational, bring a loose skeleton deck anyway. (Blind)
• Confirm logistics with your recruiter, not just peers. Platform restrictions, reusing projects, deck versus site: all of it varies by company. Crowd advice is a starting point; the recruiter gave the definitive answer in nearly every thread above.

Coach's note

If you only do three things: build the deck, cut to two case studies, and rehearse out loud until you stop reading your own slides. That covers most of what separates the walkthroughs that land from the ones that stall.

Working on your own portfolio presentation? Send me your deck or your career story and I will give you notes. I have mentored hundreds of people and I am trying to reach a thousand.

Sources consulted

Reddit (r/UXDesign, r/graphic_design), Blind design and engineering interview forums, Exponent, Dribbble Stories, Built In, and Org Design for Design Orgs via reader notes.