How To Talk About Your Design Work In An Interview

A strong portfolio gets a designer into the interview room. What gets said in that room decides whether the portfolio actually lands the job. Plenty of talented designers struggle here, not because their work is weak, but because they have never practiced explaining it out loud to someone who was not there when the decisions were made.

Lead With the Problem, Not the Visuals

The instinct for most designers is to start describing a project by talking about the look: the color palette, the typography, the overall style. Interviewers who review design work regularly have seen hundreds of attractive layouts, and a strong visual on its own tells them very little about how a candidate thinks. Starting instead with the actual problem the project needed to solve, who it was for and what was broken or missing before the design work began, gives the interviewer something far more useful to evaluate.

This framing also naturally sets up everything that follows. Once the problem is clear, the design decisions stop sounding like personal taste and start sounding like responses to a specific constraint, which is exactly the impression a candidate wants to leave. This same shift in framing is why building a design portfolio that gets noticed consistently points back to context and reasoning rather than polish alone.

Explain the Decisions, Not Just the Outcome

A common weak spot is describing only what ended up in the final design without explaining what else was considered and rejected along the way. Saying "I chose a two column layout" is far less convincing than saying "I tried a single column layout first, but user testing showed people missed the secondary content entirely, so I moved to two columns and tracked whether that improved engagement."

The second version does something important: it shows the reasoning process, acknowledges that the first attempt was not perfect, and demonstrates that the final choice was earned through iteration rather than guessed correctly on the first try. Interviewers are generally far more interested in how a candidate arrives at a decision than in the decision itself, since that process is what will actually show up on the job.

Be Honest About What Did Not Work

Every portfolio project has a part that did not go as planned, a deadline that got cut short, a stakeholder request that conflicted with the research, a solution that looked good in testing but needed to be scrapped once real constraints appeared. Candidates who present every project as a flawless success story tend to come across as either inexperienced or unwilling to acknowledge mistakes, and experienced interviewers notice the gap quickly.

Talking honestly about a compromise or a failed attempt, and explaining what was learned from it, tends to build more trust than a polished story with no rough edges at all. This is a direct extension of the honesty that makes a design portfolio actually work in the first place: the projects that read as believable rather than performed are the ones that leave the strongest impression.

Practice the Short Version First

Most interview settings do not allow for a ten minute walk through every single project in the portfolio. Each piece needs a version that can be told in roughly ninety seconds: the problem, the key decision, and the measurable or observed outcome. Practicing this short version out loud, ideally with another person listening, exposes the parts that ramble or lose the thread long before the actual interview does.

Having the short version ready does not mean the longer story disappears. It means the candidate controls the pacing, delivering the quick summary first and then expanding on whichever part the interviewer actually wants to hear more about, rather than front loading every detail and hoping the interviewer stays engaged through all of it.

Answer the Question That Was Actually Asked

A surprisingly common interview mistake is using every question as an opportunity to return to a favorite rehearsed story, even when it does not quite answer what was asked. If an interviewer asks specifically about handling disagreement with a stakeholder, pivoting to a general story about creative process instead of addressing the actual question leaves the impression that the candidate was not really listening.

Staying flexible and genuinely responding to the specific question, even if it means improvising rather than falling back on a rehearsed answer, reads as far more credible than a smooth but slightly off topic response.

Confidence Without Overselling

There is a narrow but important line between speaking confidently about design work and overselling it. Describing a project's actual impact, a measured improvement, a specific piece of positive feedback, a clear before and after, lands better than vague claims about transforming an entire product single handedly. Interviewers who have reviewed many candidates can usually tell the difference between a grounded, specific claim and an inflated one, and the inflated version tends to invite harder follow up questions than the candidate is prepared to answer.

Talking about design work well is its own skill, separate from the design work itself, and like any skill it improves with deliberate practice rather than hoping it goes well on the day. A candidate who has rehearsed the problem, the decisions, the honest setbacks and the short version of each project walks into the room with far less to worry about than one relying on the portfolio alone to do all the talking.