An interview opening is short, so the cost of the wrong example is the time it takes from a stronger one. When an interviewer says “Walk me through your resume,” decide which work best explains why your experience fits this role. A principal designer discussing a hands-on design position, for instance, may lead with a difficult product decision rather than the chronology of every title. The right emphasis changes when your most relevant work is older, your recent role has a different focus, or a transition needs explaining.
Treat your answer as a guided account of your work. Start with the experience that establishes your direction, spend the most time on evidence relevant to this interview, and end with why this role is a sensible next step. The questions below help you decide what earns that time.
Is your most recent work also your strongest match?
If yes, give that work the most detail. Name the problem you were responsible for, a decision you made, and what changed as a result. For a designer, “I led the redesign of an onboarding flow” is less revealing than explaining why you simplified a confusing choice and how you assessed the revised flow. Keep earlier roles brief unless they establish a skill the current work does not show.
If your strongest match is an older project, mention your recent position first so the chronology remains clear, then spend more time on the earlier work. You can say, “My current role sharpened how I work across teams, while the clearest example of the research and interaction design this position calls for comes from my previous project.” Choose the older example because it fits the role, not simply because it is your favorite.
Does a career change need one sentence of context?
If your resume moves between functions or industries, give the interviewer a short reason for the transition before describing the relevant work. Without that bridge, they may spend your answer trying to reconstruct the timeline. A designer who moved from content design into interaction design can name the shift and point to the projects that made it credible.
If the progression is already clear, skip the explanation and use the time for evidence. Avoid defending every move or narrating why you left each position. The transition sentence has done enough when the interviewer can follow how your earlier work connects to what you do today.
Can you support the accomplishment you want to lead with?
If you can explain your specific ownership, the important decision, and the outcome, put that accomplishment near the center of your answer. A strong example gives the interviewer a natural follow-up. You should be able to discuss the constraints, alternatives, and how you know the work helped, even if your opening version takes only a few sentences.
If the result is difficult to verify or belongs mainly to a larger team, narrow the claim. Say what you personally contributed and describe the outcome at the level the evidence supports. A credible account of a design decision that improved clarity can serve you better than an impressive-sounding metric whose source you cannot explain. Prepare a different lead example when you cannot separate your part from the team’s.
Once you choose an example, this guide to answering the greatest accomplishment question shows how to develop it into a full interview response.
Is this conversation focused on your craft or your collaboration?
For a craft-focused conversation, lead with the work itself: the problem, competing options, your decision, and how you evaluated it. For a cross-functional interview, give more space to the disagreement or dependency you helped resolve. You can use the same project in both conversations, but the opening detail should match what that interviewer can usefully explore.
When the interview focus is unclear, choose an example that supports both angles. State the work and your contribution plainly, then pause rather than filling the opening with every detail. A concise account leaves room for the interviewer to ask about the part they care about most.
How will you keep your answer grounded in real work?
Pick two or three accomplishments you can explain without a script. For each, note your ownership, a decision, the result, and any limits on what you can claim. Practice connecting those examples into a short spoken timeline, then adjust the emphasis for each conversation. Do not store confidential designs, restricted company documents, or customer details in a personal tool; a summary of your contribution is enough to prepare.
If those details are scattered across past projects, organize your interview work examples in ImpactLogr. You can draw from the same evidence for a concise introduction and the deeper questions that follow.