Skip to main content
VirtualInterview.ai

Specialist Interviews

Design Portfolio Presentation: Structure, Timing, Critique

In a design portfolio presentation interview you present one to three past projects to the hiring team and then take their questions. The slot can be a 10-minute case study or most of a 45-minute review. The panel judges how you frame a problem, which decisions you made and why, what your part was, and how clearly you tell it.

By VirtualInterview.ai Team10 min read

What is a design portfolio presentation interview?

For UX, product and graphic designers it is usually the round that carries the most weight. The panel can already see the work, so what they are listening to is the reasoning behind it. NN/g’s portfolio advice puts it in one line: “Don’t just show me the finished product.”[2] They want the problem, your part in it, how you got from the first idea to the last, and whether it worked.

This guide covers the format, choosing projects, a structure for each case study with a time budget, the questions that come during and after, the critique round many loops add, and how to rehearse it out loud.

How long is a portfolio presentation, and who is in the room?

Formats vary by company, so ask. One employer that publishes its whole process is Atlassian: a 10-minute case study inside the hiring manager interview, then a 45-minute portfolio review, then two 30-minute follow-ups.

Atlassian’s design interview process, from its published guide
StageLengthWhat happens
Recruiter screen30 minBackground, skills and goals
Hiring manager interview60 min30 min of scenario questions, then a 10-minute case study (materials sent in advance) with 10 minutes of Q&A, then about 5 minutes for your questions
Portfolio review45 minYour presentation of your best work, then Q&A led by the hiring manager
Portfolio follow-up2 × 30 minQuestions on what you presented: product thinking, then craft excellence, both within 24 hours
Triad interviewSenior IC and manager rolesEngineering and product counterparts: trade-offs, the role of design, collaboration
Values interview45 minConversational, answered with STAR

Two details in that guide are worth copying for any loop.[1] In the portfolio review, individual contributors should expect a deep dive into the details of their choices, while management candidates are asked how they led the team and shaped the result. And the follow-ups ask about what you presented, so anything you say in the review can come back an hour or a day later. Keep a note of the claims you made.

Ask the recruiter who will be in the room. A panel of designers will want the craft detail; if a product manager or an engineer is there, bring the business outcome and the technical constraint forward in each case study.

Which projects should you present?

Two or three recent projects for a 45-minute review, one for a 10-minute slot. Pick for the job you want: the craft they hire for, a hard problem, and work where your own decisions are clear.

NN/g recommends three to five projects as detailed case studies in the portfolio, and puts quality over quantity.[2] Atlassian asks for recent work, preferably from the past three to four years.[1] For the talk itself, choose from that set:

  • One project that is closest to the job: same kind of product, users or medium.
  • One with a real constraint or a failed first idea, because that is where the questions are most interesting.
  • For senior roles, one where you shaped the problem or led others, not only the screens.

Leave out projects where you cannot say what you decided. A beautiful project you mostly watched will fall apart at “what was your part?”

How should you structure each case study?

Problem, your role and the constraints, what you learned, the options you killed, the decision, the outcome, and what you would change. Seven beats, in that order, for every project.

Atlassian lists what it wants from each project: your approach, the core problems you were solving, time management, collaboration, success metrics and learnings.[1] NN/g’s list overlaps: the problem, your role and who you worked with, how you reached the solution, the challenges and the concepts you abandoned, the impact on users and the business, and what you learned.[2] The seven beats below cover both.

  1. The problem, in one sentence, and why it mattered to the users and the business.
  2. Your role, the team, and the constraints: time, technology, brand, budget, legal.
  3. What you learned before designing, from research, data, support tickets or the people doing the task.
  4. The options you explored, including the ones you killed and why. This is where judgment shows.
  5. The decision, shown on the final design, with the one detail that carries it.
  6. The outcome: the measure you set and what it did, or what you saw if there was no measure.
  7. What you would change now.

Opening a case study in under a minute

“This is the returns flow for an online furniture shop. Customers had to phone to return anything, and returns were a third of all support calls. I was the only designer on a team of four engineers and a PM, and we had eight weeks and no budget for a new courier integration. The interesting part is that our first idea, a fully self-serve return, was the wrong one, and I’ll show you why.”

The example is invented. It gives the problem, the size of it, your role, the constraint and a reason to keep listening, in five sentences.

How do you time a portfolio presentation?

Budget minutes per beat, rehearse with a clock, and decide in advance what you cut when you run long. Most candidates overspend on the final screens and run out of time for the decision and the outcome.

The budget below is this guide’s suggestion, not a published standard. The heaviest share goes to the options you explored, because that is where panels learn how you think.

A time budget per case study (this guide’s suggestion)
Beat10-minute case study20-minute case study
The problem and why it mattered1 min2 min
Your role, the team and the constraints1 min2 min
What you learned before designing1.5 min3 min
Options you explored and the ones you killed2.5 min5 min
The decision, shown on the final design2 min4 min
The outcome for users and the business1 min2 min
What you would change1 min2 min

For a 45-minute review with Q&A at the end, two 15-minute case studies and 15 minutes of questions is a workable split. Mark two places in each deck where you can skip ahead if questions eat your time, usually the research detail and a second set of screens. Keep the outcome and what you would change, whatever else goes: they are what the follow-up questions go after.

What questions come during and after the presentation?

In a live review people interrupt, and the same few questions come up again and again. Answer the one you were asked in a sentence or two, then bridge back to where you were.

Portfolio review questions and what a good answer does
QuestionWhat a good answer does
“What was your part in this?”Name your decisions and your artefacts plainly, then credit others by name or role. “I led the flow and the prototype; the visual system was our brand designer’s.”
“Why didn’t you do X?”Say whether you considered it. If yes, why it lost. If no, say so and what you would expect it to change. Defending an option you never weighed sounds worse than admitting it.
“How did you know it worked?”The measure you set before launch, what it showed, and over what period. With no data, say what you would measure and what you saw qualitatively.
“What did engineering push back on?”A real constraint and how the design changed because of it. This is a collaboration question disguised as a craft one.
“What would you change now?”One specific change with a reason. “Nothing” fails; a list of ten sounds like you never finished.
“Who disagreed with this decision?”A person or team, their argument fairly stated, and how it was settled.

Atlassian notes that most projects are collaborations and asks candidates to be upfront about their specific contributions.[1] Turning every “we” into “I” sounds forced. Give the team the result and claim the decisions that were yours.

“What was your part?”

“The research plan and the return flow were mine; I ran the five customer calls with our support lead. The PM owned the business case, and our engineer suggested printing labels at the courier instead of at home, which turned out to be the key change. I designed the flow around that idea and tested it with the support team before we built it.”

When you are interrupted mid-slide, answer, then use a short bridge such as “That’s why the next decision was…” to get back. If the question is about something two slides ahead, say “I’ll show that in a minute” and do.

Should you present a deck or your Figma files?

A deck built for the talk. Keep the source files open in another tab in case someone asks for a detail.

Atlassian’s guide advises putting the portfolio together thoughtfully rather than jumping between existing PDFs or sharing entire Figma files, and points out that the presentation itself is a design: typography, how much text sits on each page, how you frame the images.[1] A practical standard is one idea per slide, a title that states the point (“Self-serve returns confused older customers”), screens big enough to read, and before-and-after pairs where a change matters.

Graphic designers presenting print or brand work should show the work in context (on the shelf, on the street, on the phone) as well as flat, because the panel will ask how it performed where people saw it.

How do you answer a design critique or app critique interview?

Start with who the product is for and what it is trying to do, then say what works, the biggest problem and why, one change you would make, and how you would test it. Judge against the goal, not your taste.

NN/g defines a design critique as analysing a design and giving feedback on whether it meets its objectives, and stresses that it does not mean simply judging a design.[3] It also separates standalone critiques, held only to improve a design, from design reviews. In an interview, a critique round usually hands you an app or a site and asks for your view. The order below is this guide’s frame for saying it aloud:

  1. The user and the goal you assume, stated out loud, with a question to check it.
  2. What works, specifically, and why it works for that user.
  3. The biggest problem, tied to the goal: where a user would get stuck or give up.
  4. One change you would make, with what it might cost.
  5. How you would know it helped: a test, a metric or a few user sessions.

A spoken critique of a city parking app

“I’ll assume the main user is a driver who has just parked and wants to pay in under a minute, often in the rain. Is that right? What works: the app remembers my car and finds my zone from my location, so the common case is two taps. The biggest problem is extending a session. The reminder arrives, but extending means opening the app and finding the session again, and someone in a meeting won’t. I’d add an extend button to the notification itself. The cost is that the payment needs confirming without the full screen, so I’d check that with the payments team. I’d measure how often sessions expire within ten minutes of a reminder, before and after.”

The example is invented. Each judgment in it goes back to the user and goal stated in the first sentence, which is NN/g’s point. “I don’t like the colours” only belongs in a critique if you can say which user it fails and how.

How do you present a portfolio remotely?

Share one window, not your whole screen, have a PDF backup, and check the call before it starts.

  • Present from one file in one window so notifications and other tabs stay private.
  • Send or have ready a PDF version in case screen sharing fails.
  • Pause after each case study and ask if there are questions, because remote panels interrupt less and save them up.
  • Look at the camera for the opening and the outcome of each project, even if you look at the slides in between.
  • Join a few minutes early to test sharing in the meeting tool the company uses.

What mistakes cost candidates in a portfolio presentation?

Most come from presenting the work instead of the decisions behind it.

  • Walking through final screens in order with no problem, constraint or rejected option.
  • Spending half the time on the first project and rushing the second.
  • Saying “we” throughout, so nobody can tell what you decided.
  • No outcome, or an outcome claimed without a measure or a period.
  • Defending every detail when a question points to a real flaw.
  • A critique that starts with personal taste instead of the user and the goal.

How do you rehearse a portfolio presentation out loud?

Rehearse one case study at a time as a talk of up to 10 minutes, then take questions on it. Then rehearse the follow-up questions in a job interview, and the critique by talking through an app you use.

In presentation practice you describe the talk (the topic, the audience, such as “a hiring manager and two senior product designers”, and the people in the room who matter), and you can upload your deck or notes. You deliver up to 10 minutes without being interrupted, then a moderator opens questions from different kinds of askers: a domain expert who tests the detail behind a claim, a sceptic who challenges your headline result, and someone at the back with a wandering question you have to steer back. The questions come from what you actually said. The report scores structure (25%), delivery (25%), handling audience questions (30%) and message clarity (20%), and the verdict is “Ready to present”, “Nearly there” or “Needs rehearsal”. You can start a presentation practice session.

Two limits matter. It does not interrupt you mid-talk the way a hiring manager might, and its audience asks about the talk, not about your career. So rehearse each case study there, then run a job interview with the role set to your design title for “what was your part?”, “what would you change?” and the behavioural questions. You can start a job interview for a product designer. The interviewer cannot see your work, so describe it as you would to someone on a phone call; if the description is clear without the slides, the presentation will be clearer with them.

No session shows you an app to critique. Pick an app you use, run the five-step critique above aloud in five minutes, and record it. Delivery feedback in practice sessions is speech-based: speaking pace, filler words (in English answers) and pauses, measured from your spoken answer, and there is no facial-expression, eye-contact or posture analysis: the camera is only your self-view. For role-specific questions, see the UX designer mock interview and the graphic designer mock interview; for handling the questions after any talk, the presentation Q&A tips.

Frequently asked questions

Short, direct answers to the questions people ask most often about this topic. Each answer stands on its own, so you can jump straight to the one you need.

How long should a design portfolio presentation be?

Match the slot you are given and leave room for questions. Atlassian, for example, asks for a 10-minute case study inside its hiring manager interview and a longer presentation in a 45-minute portfolio review that ends with Q&A. If you are not told, ask the recruiter how long you present and how long the questions run.

How many projects should I present?

Two or three in a 45-minute review, one in a 10 to 15 minute slot. NN/g recommends three to five detailed case studies in the portfolio itself. Have the others ready in case the panel asks, and choose recent work: Atlassian asks for projects from the past three to four years.

Should I present from Figma or from slides?

From a built presentation. Atlassian advises putting the portfolio together thoughtfully rather than jumping between existing PDFs or sharing whole Figma files, and says the design of the presentation itself is judged. Keep a file open in case someone asks to see a detail.

What if my best work is under NDA?

Ask the former employer what you may show, then remove names, data and anything identifying. You can describe the problem, your process and your decisions without showing the confidential screens. Say at the start that parts are redacted, so the panel does not wonder why.

What is a design critique interview?

A round where you are shown a product, often a well-known app, and asked what works, what does not and what you would change. NN/g defines a critique as analysing whether a design meets its objectives, so start by stating the user and the goal before judging anything.

Can I rehearse a portfolio presentation with AI?

Yes, one case study at a time. Presentation practice lets you deliver up to 10 minutes uninterrupted and then answers audience questions about what you said. The free plan is 2 interviews a month, free account, no card.

Sources

The studies, statutes and primary pages this guide relies on. Numbers in square brackets in the text link here; where a claim has no number, it is our own guidance from running practice interviews.

  1. How to nail your design interview. Atlassian Careers
  2. 5 Steps to Creating a UX-Design Portfolio. Nielsen Norman Group (Rachel Krause), 2019-08-04
  3. Design Critiques: Encourage a Positive Culture to Improve Products. Nielsen Norman Group (Sarah Gibbons), 2016-10-23

How answers are scored and which data we publish: data and research · methodology

Continue reading

All guides