How to communicate clearly in product design interviews

That line has haunted me in all my past design interviews.

You know the feeling. You’re walking the interviewer through your case study, explaining your process, and halfway through you realize… you’ve lost the thread. You’re deep in showing high fidelity flows and usability tests, but you can’t remember what question you were even answering.

It happens to all of us.

Clear communication isn’t about sounding polished or using the right buzzwords. It’s about showing that you think clearly. And that’s exactly what interviewers are trying to gauge when they ask a question like, “Tell me about about a time when you solved a complex design problem.”

Step 1: Clear Thinking Before Clear Talking

When I first started interviewing for design roles, I used to prepare like I was memorizing a script. I’d rehearse my answers, polish my slides, maybe even color-code my case study deck.

But it didn’t always land.

If your thinking isn’t clear, the best slides in the world won’t save you.

Before you can speak clearly, you have to think clearly.

These days, I use a simple framework before any important conversation — whether it’s an interview, a design critique, or a whiteboard challenge.

Know your goal.
Know your audience.
Know how you’re going to say it.

It sounds obvious, but most people skip at least one of those.

1. Know Your Goal

In interviews, I used to think my goal was to explain my project. But that’s not it at all.

Your goal is to convince the interviewer that you think like a designer.

When you walk them through your work, what you’re really doing is showing how you approach problems, how you navigate ambiguity, and how you make tradeoffs when there isn’t one clear answer.

Before I start talking, I ask myself one question: What do I want them to remember about me when this interview ends?

Do I want them to see how I lead teams through messy problems?
Do I want them to understand how I balance user needs with business goals?
Do I want to show that I can communicate design decisions clearly across disciplines?

That simple question keeps me grounded. It stops me from wandering off into irrelevant details and helps me stay focused on what actually matters.

2. Know Your Audience

Empathy isn’t just for users. It’s for interviewers too.

A design manager, a PM, and a design director will all listen for different things. The PM might care about how you prioritize and measure impact. The design manager wants to know how you collaborate and give feedback. Leadership wants to understand how you think strategically and make design decisions that move the business forward.

The best thing you can do is adapt.

If you’re unsure, start by assuming they have no prior context. Don’t expect them to remember your case study or the jargon from your last company. Set the scene first.

For example, you could mention:
“This was a six-week project where I led the redesign of our onboarding flow. Our goal was to reduce drop-off during sign-up, and I partnered with a PM and a team of engineers to explore different solutions.”

It’s simple, clear, and instantly gets everyone on the same page.

And please, skip the jargon. Nobody’s impressed by phrases like ‘cross-functional ideation’ or ‘solution validation through iterative prototyping.’ Just say what you did. If you can’t explain it in plain English, you probably don’t understand it deeply enough (and that’s exactly what Feynman was getting at.)

3. Know How You’re Going to Say It

This is where structure saves you.

In an interview, structure is the difference between sounding thoughtful and sounding lost.

I like to think of my answers as small stories. Start with the context: What problem were you solving and why it mattered. Move into the process: What you did, how you approached it, who you worked with. Then finish with the outcome: What changed, what you learned, what you’d do differently next time.

That simple arc works for almost any question.

And when you’re done, make sure to land the plane. Don’t trail off into vague reflections. End with something intentional: “That project taught me how to align stakeholders early when the scope is ambiguous” or “That experience changed how I approach usability testing.” Interviewers remember candidates who can reflect and connect dots.

Bonus: Write It Down

Writing is thinking.

Before interviews, I write down short outlines of the projects I plan to talk about. I jot down the problem, the approach, the results, and one key lesson. Then I read it out loud. If it doesn’t sound natural, I rewrite it.

When you can explain your work clearly on paper, it naturally becomes easier to explain it out loud. You start to sound confident, but not rehearsed. You want to sound clear, but not robotic.

Three quick takeaways before you go

1. 
Start strong by grounding your interviewer before diving into details. It shows confidence and helps them follow your story from the start.
For example, you might say:

“We noticed a high drop-off during sign-up, so I led a five-week sprint with our PM and engineers to identify friction points and design a clearer, more intuitive onboarding flow.”

That one line tells them who you are, what you worked on, and why it mattered 

2. Speak to what they care about.
Adjust your language based on who’s in the room.
If it’s a PM, in the interview you could say:

“Our goal was to improve conversion by 10%, and we made tradeoffs between usability and development time to get there.”

Or it’s another designer:

"I explored three interaction patterns and ran quick usability tests to understand which felt more intuitive."

And if you're talking to a a director or VP

"The redesign increased sign-up completion by 14%, which directly supported our Q2 revenue target."

Same story, different framing 

3. Practice your stories out loud.
Don’t just write your answers, say them. You’ll immediately catch where your story drags or sounds unclear.
You can phrase your story like:

“One thing I learned from this project is how early alignment can prevent rework later.”
“Looking back, I would have involved our PM earlier to validate assumptions before designing.”

Those simple, reflective lines make you sound thoughtful and self-aware. Two traits every interviewer listens for.