A portfolio presentation is not a scrolling case study with a microphone attached.
In an interview, the reviewer interrupts. They ask why research changed the direction, want to revisit an early concept, or skip ahead to the outcome. You may have 30 minutes instead of 45. The deck has to support a conversation while still making your contribution unmistakable.
Pitchdeck lets designers create presentations in Figma, add notes and interactive content, present from a browser, and export to PowerPoint, Google Slides, Keynote, or PDF. For portfolio interviews, that range matters because the live presentation and the leave-behind should not necessarily be the same artifact.
This topic is distinct from How to Build Client Presentations in Figma and Presentation Handoff Checklist for Designers. Client presentations seek approval, while general handoff focuses on reliable delivery. A portfolio deck has a different job: help an interviewer understand how you think, what you owned, and what changed because of your work.
Choose evidence before polishing slides
Start by writing the questions your deck must answer:
- What problem was the team solving?
- What was your specific role?
- Which constraint materially shaped the work?
- What decision did you make, and what evidence supported it?
- How did the final result differ from the starting point?
- What would you change now?
Then gather evidence for those answers.
Useful evidence may include:
- an early flow that exposed a bad assumption
- a research pattern that changed priorities
- two competing design directions
- the system or component decision behind the final screens
- a measurable result, when you can substantiate it
- a candid reflection on what did not work
Do not fill the deck with every polished screen you produced. A smaller set of evidence with clear reasoning is more persuasive than a gallery that leaves the interviewer to infer your contribution.
Give each case study one argument
A strong case-study section usually has one memorable claim:
I simplified a confusing setup flow by changing the information model before redesigning the interface.
or:
I helped a campaign team produce local variants without fragmenting the visual system.
That claim becomes the filter for what belongs in the deck.
If a slide does not help establish the problem, decision, evidence, or outcome, move it to an appendix. This is especially important when several designers contributed to the project. The deck should not imply sole ownership, but it also should not hide your actual work behind “we” on every slide.
Design for interruption
Interview decks need stronger navigation than linear conference talks.
Build obvious section markers for:
- context
- your role
- the key decision
- the final direction
- outcome and reflection
Keep an appendix for detailed flows, research artifacts, and alternate explorations. If an interviewer asks a deep question, you can jump there without derailing the main story.
Pitchdeck supports clickable links and web presentations, which makes this kind of non-linear navigation practical. Use it sparingly. The interviewer should feel that you are answering their question, not operating a complicated prototype.
Use speaker notes for the facts you might blur under pressure
Do not put every detail on the slide.
Speaker notes are useful for:
- the exact scope of your contribution
- dates or team composition
- a concise definition of an internal term
- the source of a result or metric
- a reminder of what is confidential
- the transition to the next point
Notes are not a script. If every sentence is written out, delivery often becomes stiff. Use them to protect accuracy and keep the story moving.
Decide what the interviewer receives
The live deck may contain:
- animated transitions
- embedded video
- speaker-led context
- appendix routes
- details covered by your verbal explanation
The leave-behind has to stand alone.
Choose the format based on the recipient:
- A web link is useful when you want controlled sharing and a polished browser experience.
- PDF is dependable for a compact, read-only follow-up.
- PowerPoint, Keynote, or Google Slides exports make sense only when the recipient has a reason to edit or present the material.
Which Figma Presentation Export Format Should You Use? goes deeper on that decision.
Before sharing, remove hidden notes, confidential appendix material, internal links, and anything that depended on your narration to avoid being misleading.
Rehearse three versions
Prepare the same case study at three lengths:
- two minutes: problem, role, decision, outcome
- eight minutes: enough evidence to show your reasoning
- fifteen minutes: the full version with tradeoffs and reflection
This prevents the common failure where the first project consumes the whole interview.
When rehearsing, test the transitions created by questions:
- Can you jump to the final result early?
- Can you return to the narrative without confusion?
- Can you explain your ownership in one sentence?
- Can you finish cleanly if time is cut?
The deck should make those moves easy.
Portfolio deck signoff checklist
Before the interview, confirm:
- every case study has one clear argument
- your role is explicit and accurate
- confidential material is removed or masked
- results are sourced and not overstated
- key screens are readable on a shared video-call window
- videos have a static fallback
- section navigation and appendix links work
- the leave-behind makes sense without narration
- a local PDF exists in case the network fails
Where Pitchdeck helps
Pitchdeck is valuable because a portfolio deck has to work in several modes: prepared story, interrupted conversation, browser presentation, and post-interview follow-up.
The plugin handles presentation and export mechanics without requiring the designer to rebuild the work outside Figma. The designer still has to make the harder choices: what evidence matters, how ownership is described, and which details the audience can safely receive.
Build the deck around those choices first. Then use Pitchdeck to make the conversation flexible, the delivery dependable, and the follow-up appropriate for the person reviewing your work.
Read as Markdown Related resource index Site index for AI agents
Pro Bundle