Talk to people preparing for a design interview and you hear almost exactly the same sentence:
"I'm anxious because I don't know what they'll ask."
So everyone prepares the same way. Draw up expected questions for each portfolio project, write model answers, memorise them. Skim the list one more time the night before to steady the nerves.
Then in the actual interview, only one or two of the memorised questions come up. A deceptively simple question — "why did you design this screen this way?" — stops them cold, and the composure slips. The interviewer notices.
The problem is not a lack of preparation. It is that the unit of preparation is slightly wrong.
Questions feel frightening because you believe you cannot know what is coming. If every project and every company produces new random questions, the memorisation list is infinite — and memorising still leaves you anxious.
But collect question sheets from a range of design interviews and the wording differs while the intent is remarkably consistent. Different companies, different products, different interviewers.
Why?
Interviewers do not ask questions because they want to ask something novel. They ask to check the risks of hiring this designer.
So at the root of every question is the anxiety an interviewer carries when hiring a designer. And that anxiety narrows to three things.
Design outcomes rarely show up cleanly in numbers. The work looks good — but can this person articulate what change they created for the business or the user?
Figma changes, AI tools change, collaboration methods change. Is this someone who keeps moving and folds new things into their workflow?
Our domain will be new to them. Will they find their footing quickly rather than flounder in front of unfamiliar products and users?
The sentences get packaged differently at every company. Open them up and it is always one of these three.
That can sound abstract, so here is how it actually gets packaged — from a debrief of a product designer interview with a team building internal operations tools.
"On an internal tool that doesn't generate revenue directly, how would you define your contribution as a designer?"
It sounds tricky at first. "Internal tool," "revenue contribution" — it reads as a special situation. But it is simply anxiety 1, packaged. It asks: in a role where design outcomes do not show up as numbers, how will you define and demonstrate the impact you created?
It tests whether you can articulate impact in another language — operational efficiency, time saved, error rate reduction. Change the product name and this question appears anywhere.
"How have you folded AI tools like Claude Code or Figma plugins into your design workflow?"
That is anxiety 2. In an era of fast-moving tooling, it checks whether you absorb new things and apply them to your own process. A few years ago a different tool name filled that slot; next year another will. The point is not the tool but the disposition toward integrating new methods.
"You haven't worked in domains like CRM, support or policy before. What would you look at first to improve operational efficiency?"
Obviously anxiety 3. Watching where a designer starts in an unfamiliar domain reveals their entire approach to understanding users and problems. Someone who interviews frontline staff first and someone who dissects existing screens first work in fundamentally different ways.
All three questions wore that company's clothing. All three asked the same things.
The insight is simple. Well-prepared designers do not memorise questions. Memorising expected questions per project never ends, and they never come out the way you rehearsed.
Instead, they fill three boxes in advance with their own portfolio experience.
Fill those three with your own work and no rephrasing can pull you off balance. Unfamiliar wording just triggers recognition: ah, this is asking about box one — and you take it out of a drawer you already organised.
This is the moment design interview preparation shifts from memorising projects to organising your own design decisions. And it is far less anxiety-inducing: instead of clutching an infinitely expanding list, you walk in with three solid stories.
A design interview is not a test of improvising answers to unknown questions. It assesses how clearly this designer can explain the reasoning behind their decisions.
And that clarity does not come from making screens attractive. It comes only from someone who has organised their design work against the interviewer's three anxieties in advance.
The same principle applies in other disciplines — for the search marketing version, see The Worst Thing to Be in an SEO Job Interview Is Forgettable.
And on why the second anxiety — keeping pace with tooling — matters increasingly, see In the AI Era, a Designer's Value Comes From Judgment, Not Production.
Adapted from a piece originally published on Brunch by Woody of Woody Design Lab.
Because only one or two memorised questions actually come up. The issue is not insufficient preparation but preparing at the wrong unit — organise around the interviewer’s anxieties, not around individual questions.
Whether the designer can prove the impact of their design, whether they keep up with rapidly changing tools and methods, and whether they can adapt quickly to an unfamiliar product and domain.
It is anxiety one, packaged. It tests whether you can define and demonstrate impact in an alternative language — operational efficiency, time saved, error rate reduction — where design outcomes do not appear as revenue.
Three boxes filled from their own portfolio: a project where they defined and showed design impact, an experience applying a new tool or method to their workflow, and an account of orienting themselves in an unfamiliar domain.
To apply what you just read to your own site, start with a free audit of where things are now.
A strategist replies within 24 hours on business days.
A studio replaced designer, frontend and backend postings with a single product builder role. Dozens of interviews later, nobody was hired. What they changed.
From hotels to F&B to beauty to head of marketing at Sulbing: how volunteering for undefined work, learning the operational basics, and owning a signature widen a marketing career.
SEO skills are now the baseline. What gets you picked from 300 applicants is not competence but memorability — and you do not need to become famous.