Portfolio walkthrough questions.
77 portfolio walkthroughquestions from the bank — open to read. Pick one and practice it out loud; a coach note comes back in seconds.
Learn the ideas first
All 77 questions
Walk me through a project where the original brief turned out to be the wrong problem to solve.Pick a project where user research surprised you. Walk me through what the surprise was and what you did with it.Walk me through a project where your first design wasn't your last. What changed and why?Walk me through a project where you and an engineer disagreed sharply. How did it resolve?Pick a project you're proud of and walk me through what you'd do differently if you started today.Walk me through a project where you had to design without much access to the actual users.Walk me through a project where the constraints — time, technology, or budget — fundamentally shaped your design.Pick a project where a PM pushed back on your design direction. Walk me through what happened next.Walk me through a project where the data and the designs disagreed. How did you make the call?Pick a project where the design shipped but the outcome was underwhelming. What was your read on why?Walk me through a project that involved a significant brand or design-system constraint. How did you push at the edges?Pick a project where you turned a vague request into a concrete design problem. Walk me through the framing.Walk me through a project where talking to users contradicted what the team assumed.Walk me through a project where you had to design across multiple teams who didn't all agree.Walk me through a project that started messy and ended clean. What got dropped along the way?Pick a project where you regret pushing too hard on a design opinion. What happened?Walk me through a project where the success metric was hard to define.Walk me through a project that started without any user research. What did you do to validate as you went?Walk me through a project where engineering told you something couldn't be built the way you'd designed it.Pick a project that required you to design for a system you didn't fully understand at the start.Walk me through a project where you learned something that changed how you approach design going forward.Walk me through a project where users were doing something with your product that the team didn't expect.Pick a project where the qualitative research and the quantitative metrics told different stories.Walk me through a project where the polish came last and the structure came first. Why that order?Walk me through a project where a stakeholder repeatedly tried to redirect the design. How did you handle it?Pick the project you're most proud of and walk me through its weaknesses.Walk me through a project that didn't ship. What was the design's part in that, and what was outside your control?Walk me through a project where accessibility shaped your decisions in a non-obvious way.Walk me through a project where you ran a small experiment to test a design hypothesis.Walk me through a project where you took critique well and used it to make the design better.Walk me through a project where you had to choose between two very different design directions. How did you decide?Pick a project where you had to explain your design thinking to non-designers. What approach did you take?Walk me through a project where you inherited someone else's design work. How did you approach it?Pick a project where the timeline forced you to cut scope. What did you prioritize and why?Walk me through a project where you got feedback late in the process that required significant changes. How did you respond?Pick a project where you had to design for a user group you weren't part of. How did you build understanding?Walk me through a project where your design had to work on multiple screen sizes or platforms. What was your approach?Pick a project where you made an assumption about users that you later wished you'd tested earlier. What happened?Walk me through a project where the PM had a clear vision but you saw potential issues. How did you navigate that?Pick a project where you wish you'd involved engineers earlier in the design process. What would have been different?Walk me through a recent project where AI tools produced early drafts — explorations, copy, code, anything. Where exactly does your judgment show up in what shipped?Here's the setup — a stakeholder told your team to 'add AI' to the product. Walk me through a time you turned that kind of mandate into a real user problem, or pushed back on it.Walk me through a project where you designed around output you couldn't fully predict — AI-generated content, recommendations, anything non-deterministic. How did you prototype it, and what did you do about the failure modes?Walk me through a project where you used AI to speed up research — synthesis, transcription, drafting a discussion guide. What did you still verify by hand, and where did the tool's read differ from yours?Pick a case study and tell it to me backwards: start with the measured outcome, then show how each design decision earned its place in that result.How would you structure a 20-minute portfolio presentation for a panel of a PM, an engineer, and a design director? What does each of them need to hear from the same project?Pick a project where the business goal pulled the design toward something you considered manipulative — a dark pattern, a buried opt-out, engineered urgency. Walk me through where you drew the line.Walk me through a contribution you made back to a design system other teams depend on — a component, a pattern, a doc. How did you make the case, and who pushed back?Pick a team project in your portfolio. Walk me through which decisions were yours, which weren't, and how you talk about the parts you didn't make.What would you look for in deciding which three projects make the cut for your portfolio? Walk me through why you picked the ones in front of me.A reviewer flips through your strongest piece and says 'a template and an AI assistant could have made this.' Defend the craft: show me two decisions in it that a tool wouldn't have made.Walk me through a case study where you can't share the numbers — NDA, no analytics, or the metrics never existed. How do you make the outcome credible anyway?Walk me through a project where you had to balance the needs of two very different user segments. How did you prioritize?Pick a project where you advocated for research but didn't get the time or budget. Walk me through how you designed anyway.Walk me through a project where you inherited someone else's design. What did you keep, what did you change, and why?Pick a project where engineering said your design was technically impossible. Walk me through the conversation and outcome.Walk me through a project where you now realize you optimized for the wrong metric. What would you measure today?Pick a project where you had to design for accessibility as a core requirement, not an afterthought. Walk me through your approach.Walk me through a project where legal, compliance, or regulatory requirements forced you to rethink your design.Pick a project where you ran usability testing and the results contradicted your intuition. Walk me through what you did.Walk me through a project where you had to design across multiple platforms or form factors. How did you maintain coherence?Pick a project where the PM wanted to ship fast and you felt the design wasn't ready. Walk me through how you handled it.Walk me through a project where you'd now involve a discipline or partner you didn't loop in originally. Who and why?Pick a project where you designed something users said they wanted, but they didn't actually use it. Walk me through your post-mortem.Walk me through a project where you had to make a design decision without consensus. How did you decide and communicate it?Pick a project where scope crept significantly during design. Walk me through how you managed it and what you learned.Walk me through a project where you designed for internal tools or operations teams. How did discovery differ from consumer work?Pick a project where you had to design with incomplete or contradictory business requirements. Walk me through how you moved forward.Walk me through a project where you collaborated with data science or machine learning teams. How did their work shape your design?Pick a project where you now wish you'd spent more time on onboarding or activation. Walk me through what you'd change.Walk me through a project where you designed a feature that was later sunset or removed. What was the reasoning and your take?Pick a project where you conducted research in a market or culture unfamiliar to you. Walk me through your approach.Walk me through a project where you had to design within a very short cycle—days, not weeks. What did you sacrifice and protect?Pick a project where you worked on a 0-to-1 product. Walk me through how you defined success before anything existed.Walk me through a project where you designed for trust or safety as a primary concern. How did that influence the experience?Pick a project where you had strong opinions but limited influence. Walk me through how you tried to shape the outcome.Walk me through a project where you designed something highly technical or complex. How did you make it approachable?