1. LandOffer
  2. Blog
  3. All articles
  4. Turn a UX Portfolio Case Study into an Interview Presentation

Job search

Turn a UX Portfolio Case Study into an Interview Presentation

A complete six-part original fictional script, 25-minute declared meeting plan, simulated Q&A and actual finite timing/claim checks distinguish design evidence from unproven outcomes.

9 min readLandOffer team

Your UX portfolio case study already contains more material than a live interview can use. Turn it into a presentation by selecting a decision the panel can examine, explaining your contribution, and reserving time for questions. Use the case study as source material, then select what the panel needs to understand and question your reasoning.

This guide builds a complete fictional talk script, a planned segment ledger, and a simulated follow-up conversation. LandOffer publishes this guide and offers job-search tools. Public sources were checked October 21, 2026; the project, candidate, research observations, and interview brief below are invented. No real interview, user research, presentation rehearsal, or employer assessment was conducted.

A designer arranging a compact presentation sequence beside a longer portfolio notebook, with an empty chair for discussion.

Start with LandOffer’s recently posted jobs to identify the actual design responsibilities you want your case to demonstrate. Then use the employer’s interview instructions to set the scope.

Read the interview brief before choosing a structure

Atlassian’s design interview handbook distinguishes a hiring-manager case-study segment from a separate portfolio review. It describes a ten-minute case study plus ten-minute Q&A in the former, while the latter is a 45-minute presentation-and-discussion interview. It also asks candidates to identify their own contributions. Those are descriptions of Atlassian’s stages, not a universal presentation template.

GitLab’s product designer guidance describes an approximately 30-minute case-study walkthrough within the peer interview for specified reporting structures. It expects discussion throughout and says a formal presentation is not required. Its preparation advice includes the problem, role, process, rejected ideas, and results. Read the applicable role and invitation rather than transplanting one employer’s timing into another.

Ask about the total meeting length, uninterrupted speaking allowance, number of projects, expected audience, and whether questions interrupt the talk. Also clarify the permitted format and sharing restrictions. Build the structure around those answers instead of a generic “ten slides” rule.

NN/g’s public summary on interview portfolios distinguishes attracting an interview from supporting the interview itself. Here, the useful implication is to prepare material the panel can question, not only a polished page designed for independent reading.

Reduce the case to evidence and a consequential choice

Select a case where you can explain what was uncertain, which options you considered, what you personally changed, and what remains unproven. A substantial unfinished project can support that account if you describe its status accurately. A polished screen with an invented impact claim cannot.

The fictional brief for Nadia’s product design interview allows one project in a 25-minute meeting: nine minutes for the planned talk, twelve for questions, two for introductions and setup, and two minutes of contingency. These allocations are declared teaching assumptions, not an employer’s real instructions. Nadia’s case is HarborShelf, a fictional equipment-loan reservation prototype.

Her case file contains six evidence cards:

  • H1, scope: Nadia designed the reservation flow; a researcher planned the sessions, and an engineer advised on availability constraints.
  • H2, initial observation: three of five fictional participants mistook a selected date for a confirmed reservation in the first prototype.
  • H3, decision: Nadia compared immediate confirmation with a request-and-review flow; the engineer could not promise live inventory accuracy.
  • H4, failed iteration: an early “Request received” banner still left two of five fictional participants unsure whether pickup was confirmed.
  • H5, revision: Nadia separated requested and confirmed states, added a review step, and prepared an updated prototype. It has not been retested.
  • H6, limit: no implementation, production traffic, conversion measurement, accessibility audit, or business outcome is established.

Those invented observations support a design question and an iteration story. They do not establish a statistically reliable rate, improvement between equivalent studies, or product launch. Keep the evidence cards in appendix notes so you can answer follow-ups without adding an unsupported business metric.

Worked asset one: a complete spoken script with a planned pace

The following six passages form Nadia’s complete prepared script. Each passage has a visual cue and a time budget. The budgets include intended pauses to point out states and invite clarification; they are not measured delivery times. No slide deck or working prototype was rendered for this article.

0:00–1:00 — Context and contribution; cue: one flow overview, H1.

“Today I’ll show a reservation problem in HarborShelf, a fictional equipment-loan prototype. I designed the request flow and its status language. A researcher owned the session plan, and an engineer advised on availability constraints. My focus was helping a borrower understand whether equipment was merely requested or actually reserved. I’ll walk through the initial misunderstanding, a decision shaped by the inventory constraint, and an iteration that still failed. I’ll end with the revised flow and what we would need to learn next. Nothing in this case was shipped or measured in production.”

1:00–2:00 — Problem; cue: selected date beside final state, H2.

“In the first prototype, selecting a date made the next screen look settled. Three of five fictional participants treated that state as a confirmed reservation. The issue was not whether the calendar looked attractive; it was whether the interface implied a commitment the service could not yet make. I used that observation to focus the next design decision on the meaning of confirmation. I would not generalize this small example to all borrowers, and I have no baseline for missed pickups.”

2:00–4:00 — Decision and trade-off; cue: two alternative flows, H3.

“I considered immediate confirmation because it would make the interaction shorter and feel decisive. However, the engineer could not guarantee current inventory availability. A confirmation promise would therefore outrun the system’s known capability. I chose a request-and-review flow with an explicit later confirmation state. The cost is another step and possible waiting. The benefit we intended was a more truthful expectation, not a measured conversion gain. My responsibility was designing and explaining that trade-off; implementing availability logic and deciding service policy belonged to other owners. I would point to the two alternatives here so we can compare the promise each one makes.”

4:00–6:00 — Failure; cue: early banner and remaining ambiguity, H4.

“My first revision added a ‘Request received’ banner but left the surrounding layout too similar to confirmation. In the fictional follow-up observation, two of five participants still could not tell whether pickup was confirmed. I had changed the label without sufficiently changing the state explanation. That is the failure I want to make visible. These are small illustrative observations, not a controlled comparison with the first group, so I would not claim a reduction from three to two proved improvement. The result gave me a reason to revise the status model again, not permission to declare the issue solved.”

6:00–8:00 — Revision; cue: requested, review, confirmed sequence, H5.

“I separated the requested state from the confirmed state, placed the review step before submission, and made the next action explicit. The updated prototype tells the borrower that the request needs review and that a separate confirmation is required before pickup. I would walk through that distinction rather than read every label aloud. I prepared the revised flow; it has not been retested. Before recommending implementation, I would ask whether participants can explain their current status and next action without prompting, and I would review the wording and transition behavior with the responsible product and engineering partners.”

8:00–9:00 — Limits and handoff to discussion; cue: evidence and open questions, H6.

“The completed work is the revised prototype and the rationale connecting it to the observed misunderstanding. The open work is validation of that revision, accessibility review, implementation, and any production evaluation. I cannot claim fewer support contacts or higher completion from these materials. The main lesson is that a confirmation message has to match the service’s actual commitment. I would welcome questions about the rejected immediate-confirmation option, the failed banner, or how I would test the revised states.”

Preserve the discussion when the pace changes

Nadia’s planned speaking segments total nine minutes. Together with twelve minutes of questions, two minutes of setup, and two minutes of contingency, they occupy the declared 25-minute slot. The executed local arithmetic check verified the allocation; delivery duration still requires an actual spoken rehearsal.

If an interviewer uses three minutes asking about the inventory constraint during the talk, Nadia should acknowledge the time and offer a shorter route. Her prepared bridge is: “That question connects to my rejected option. To keep room for discussion, I can summarize the revised states and the remaining validation in two minutes, then return to the alternatives.”

Ask before revising the allocation, and retain the failed iteration when choosing what to shorten. Under this fictional brief, one option is to use the two contingency minutes and shorten the remaining planned narration by one minute, preserving the twelve-minute question reserve. That is a revised plan requiring the interviewer’s agreement, not an automatic entitlement to time.

A presentation notebook with a clear decision path and separate question cards, leaving space for follow-up discussion.

Worked asset two: a completed simulated follow-up

This dialogue is an original fictional teaching conversation, not a transcript, employer rubric, or recommended answer to a private assessment. Each answer stays within the same fictional case evidence when the interviewer probes further.

Interviewer: “Why not confirm immediately and cancel later if equipment is unavailable?”

Nadia: “That was the immediate-confirmation option in H3. It reduces visible steps but makes a promise before availability is established. I chose request-and-review because the stated technical constraint did not support that promise. I would discuss the cancellation cost with the service owner before treating the shorter flow as better.”

Interviewer: “Did your change improve task success?”

Nadia: “I cannot establish that. H4 records continuing confusion in a small fictional observation, and H5 has not been retested. I can show the design change and its rationale. A success claim needs an appropriate evaluation of the revised flow and a defined task outcome.”

Interviewer: “Which part did you personally own?”

Nadia: “I designed the flow, compared the options, revised the status treatment, and documented the rationale. The researcher owned the session plan. The engineer advised on feasibility. I did not build the availability service or authorize its operating policy.”

Interviewer: “What would make you reverse your decision?”

Nadia: “Reliable availability and an approved immediate-reservation policy would change the constraint. I would then compare a shorter confirmation flow against the remaining borrower needs. I would not preserve an extra review step solely because it appears in my portfolio.”

Interviewer: “What is the most important unresolved issue?”

Nadia: “Whether borrowers can correctly distinguish requested from confirmed in the revised prototype. I would define that question before choosing a method. Accessibility and implementation are also unresolved; I cannot imply the prototype passed either review.”

Check timing and claim traceability before rehearsal

The local exercise linked all six planned segments to H1–H6 and checked three approved claims: Nadia designed the flow, a failed iteration remained confusing, and the revised prototype was not retested. It rejected added claims of production launch, conversion lift, and completed accessibility validation because the invented evidence did not support them.

It also verified the contingency calculation: a three-minute interruption minus two contingency minutes requires one minute less narration if the twelve-minute question reserve is preserved. These checks assess a declared plan and finite fictional claim set. They are not a presentation score, a usability study, a real rehearsal, or evidence that the script will fit every speaker.

Next, rehearse aloud using the actual brief. Time the opening and transitions, note where you need to point to an artifact, and practice the short route. If your first run overruns, remove a less important detail rather than deleting who did the work or what remains unknown. Keep appendix material retrievable without opening an entire design file and searching through unrelated work.

Before sharing, confirm that you may show the selected material. A public portfolio page does not automatically make every underlying research record or internal file appropriate for an interview. The example here uses wholly invented material and requires no private evidence.

Use LandOffer’s current design opportunities to choose the responsibility your next case should illuminate. Choose one decision you can explain, identify its supporting artifact, and reserve time for the panel to question it.

Sources and Further Reading