UX Fundamentals interview questions
UX Fundamentals questions a UX / UI designer can be asked, from first job to senior. Open one to see the strongest answer and why it works.
A PM asks for a “modern settings page.” First move?
The strongest answer: Name the job a person is trying to finish and what is in the way — I do not open a moodboard first
Why it works: Exactly. The job first. Trends, copies, and invented scores skip the person.
- Frame the job before pixels.
- Do not start in a trend file.
- Do not copy a competitor as the brief.
- No invented usability score.
What is a mental model, and what goes wrong when the interface disagrees with one?
The strongest answer: It is what a person already expects this thing to do; when the UI disagrees they hesitate, undo, or blame themselves — so I either match the expectation or teach it plainly
Why it works: Right — expectation first, and where you must break it, say so in the interface rather than in a help centre.
- Match what people already expect.
- Ask what they expect first.
- Match it, or teach it visibly.
- Never patch it with a tooltip.
How do you start a critique?
The strongest answer: With the job and the question you want help on — not “be nice” and not a roast of the typeface
Why it works: Exactly. Job and question. Font roasts, silence, and votes skip the work.
- State the job and the question.
- Critique the path, not the person.
- Do not roast the type first.
- Do not vote on who is best.
Growth wants a pre-ticked marketing box buried in the signup. What do you do?
The strongest answer: No — that is a dark pattern; I will design an honest opt-in — I do not “just ship the tick”
Why it works: Exactly. Refuse the pattern. Burials and win-if-worse A/Bs are how you become the case study.
- Refuse pre-ticked consent.
- Design an honest opt-in.
- Do not bury the untick.
- Conversion ≠ permission to trick.
What should a junior case study show?
The strongest answer: The problem, what you tried, what you changed, and what you still do not know — not a gallery of pretty frames
Why it works: Exactly. A story with a leftover. Galleries, invented 40%, and stolen work are how you fail the interview later.
- Problem, tries, change, leftover.
- Not a pretty gallery.
- No invented 40% lift.
- Do not show work you cannot show.
You liked another product’s empty state. Honest move?
The strongest answer: Learn the job it does, then write ours — I do not screenshot-trace it into the file as if I invented it
Why it works: Exactly. Learn the job. Tracing, recolouring, and unlicensed paste are how you fail a review and a lawyer.
- Learn the job; write yours.
- Do not trace into the portfolio as original.
- A recolour is still a copy.
- Do not paste unlicensed art.
A cookie banner covers the page and the reject control is a tiny grey X. What is that?
The strongest answer: A dark pattern — I give reject equal weight and a clear label, I do not bury it to “hit consent %”
Why it works: Exactly. Equal, labelled reject. “Everyone,” portfolio-as-clever, and smaller-X A/Bs are the pattern.
- Reject must be equal and labelled.
- Buried X is a dark pattern.
- Do not put tricks in the portfolio as craft.
- Do not A/B a smaller reject.
What belongs in a problem frame besides a user quote?
The strongest answer: The job, the constraint, and what we will not solve — a quote alone is a poster
Why it works: Exactly. Job, constraint, non-goal. Posters, unread maps, and invented 9.2s are décor.
- Job + constraint + non-goal.
- A quote is not a frame.
- Do not write an unread novel map.
- No invented pain score.
A settings screen shows forty controls in one flat list, and support says people cannot find the two they came for.
How do you cut the load without removing anything?
The strongest answer: Group by the job, give the rare controls sensible defaults and collapse them, and put the two people come for first — the same forty settings, fewer decisions at once
Why it works: Exactly — load is about how many choices are live at once, not how many exist.
- Fewer live choices, not fewer features.
- Group by the job.
- Default and collapse the rare ones.
- Surface what people came for.
What rule makes critique useful?
The strongest answer: We speak to the work against the job, and the designer names the question — I do not let it become a taste pile-on
Why it works: Exactly. Job and a named question. Loud, only-nice, and emoji votes skip the decision.
- Work against the job.
- Designer names the question.
- No taste pile-on.
- No emoji-vote-and-leave.
Your case study has no leftover. What is missing?
The strongest answer: What you still do not know, and what you would not claim — a victory lap is an ad
Why it works: Exactly. Leftover and claims you will not make. Hero shots, borrowed 35%, and stolen credit fail a senior read.
- Include leftover and non-claims.
- Victory-only is an ad.
- No borrowed lift %.
- Credit your teammates.
A director joins critique and redesigns live. What do you do?
The strongest answer: Park the live redesign, return to the question, and book a decision with the job on the table — I do not draw their taste in the room to soothe
Why it works: Exactly. Return to the question. Soothe-draw, exile, and invented quotes fail the work and the relationship.
- Park live redesign; return to the question.
- Decide against the job.
- Do not soothe-draw.
- Do not invent a user quote.
How do you run a framing workshop that is not a sticky-note party?
The strongest answer: A job, a constraint, and a non-goal on one page they mark — I do not end with 200 stickies and no sentence
Why it works: Exactly. One marked sentence. Sticky parties, colour votes, and invented pain scores are décor.
- One page: job, constraint, non-goal.
- They mark it.
- Do not end in a sticky pile.
- No invented pain score.
Critique has become a compliment circle. What do you change?
The strongest answer: The prompt: a question the work could fail — I do not add a second meeting called “real critique”
Why it works: Exactly. A fail-able question. Shame, cancel, and winner boards kill the room.
- Ask a question the work could fail.
- Do not add a second “real” critique.
- Do not shame.
- Do not run a winner board.
Growth wants confirm-shaming on cancel. Your line?
The strongest answer: No — I will design a clear cancel and an honest reason to stay — I do not A/B which insult converts
Why it works: Exactly. Clear cancel, honest stay. Insults, bot-mazes, and portfolio-as-craft are the pattern.
- Refuse confirm-shaming.
- Clear cancel + honest stay.
- Do not bot-maze cancel.
- Do not file tricks as craft.
A candidate’s case is all mockups and a 50% lift. What do you probe?
The strongest answer: What they measured, who else did the work, and what they would not claim now — I do not hire the 50%
Why it works: Exactly. Probe the claim and the credit. Hiring the 50%, asking for more, and Dribbble-only staff fiction.
- Probe measure, credit, non-claims.
- Do not hire a lift %.
- Do not ask for a bigger %.
- Shots ≠ a case.
When do you run an ethics pass on a flow?
The strongest answer: When it takes money, consent, or attention we did not earn — I do not wait for a journalist
Why it works: Exactly. Money, consent, attention. Legal-PDFs, A/B-as-ethics, and post-launch blogs are late.
- Pass flows that take money, consent, or attention.
- Do not wait for the press.
- Legal ≠ the pass.
- A/B ≠ ethics.
A workshop is a status dump. What do you do as facilitator?
The strongest answer: Put a decision or a frame on the wall and time-box talk — I do not add another hour so everyone can monologue
Why it works: Exactly. A decision on the wall. Longer, meta-align, and forever-cancel miss the job.
- Decision or frame on the wall.
- Time-box talk.
- Do not lengthen monologues.
- Do not add a meta-workshop.
Delivery has started. Do you stop framing?
The strongest answer: No — a thin stream can still kill a slice — I do not pretend the PRD ended learning
Why it works: Exactly. Thin stream, kill right. Phases, nice-only, and vanity heatmaps ship a dead bet.
- Keep a thin discovery stream.
- It may kill a slice.
- PRD ≠ end of learning.
- Do not replace users with vanity.
What do you standardise across eight product design teams?
The strongest answer: How a problem is framed, critiqued, and handed off — I do not standardise every Figma plugin
Why it works: Exactly. Frame, critique, handoff. Plugins, central approvers, and novels are queues and shelves.
- Standardise frame / critique / handoff.
- Let plugins differ.
- Do not approve every frame.
- Do not write a shelf novel.
What does a staff designer add to strategy that a slide deck does not?
The strongest answer: Who we will disappoint, in a moment you can see — I do not decorate a strategy we have not chosen
Why it works: Exactly. A visible disappointment. Pretty decks, motion titles, and invented sizes skip the choice.
- Show whom we disappoint, in a moment.
- Do not decorate an unchosen strategy.
- Pretty ≠ framed.
- No invented opportunity size.
How do you teach critique so it survives a reorg?
The strongest answer: A written ritual: job, question, decision — I do not rely on one charismatic facilitator
Why it works: Exactly. A ritual you can hand on. Cults, roasts, and tool scores die or injure.
- Write job / question / decision.
- Do not rely on one facilitator.
- Do not roast.
- Do not replace critique with a tool score.
What ethics bar do you set for the design org?
The strongest answer: No dark patterns, no fake outcome numbers, no hidden cancel — a growth target is not a waiver
Why it works: Exactly. Patterns, honesty, cancel. Legal-minimum, A/B-as-ethics, and 6pt PDFs are how you become the case study.
- Ban dark patterns and hidden cancel.
- No fake outcome numbers.
- Legal ≠ enough.
- A/B ≠ ethics.
The company’s design site is a shot gallery. What do you change?
The strongest answer: Cases with problems, leftovers, and credit — I do not hire with a moodboard of shots
Why it works: Exactly. Stories with leftovers. More shots, invented 2×, and hidden leftovers hire the wrong people.
- Publish problems, leftovers, credit.
- Do not hire from a shot gallery.
- No invented 2× impact.
- Do not hide leftovers.
A growth lead says “everyone uses these patterns.” Your staff answer?
The strongest answer: We do not — I will write the ban and the honest alternative, I do not keep a secret playbook of tricks
Why it works: Exactly. A written ban and an alternative. Everyone, free-users-only, and best-practice files are how you become the pattern.
- Write the ban and the honest alternative.
- Everyone ≠ a licence.
- Do not trick free users only.
- Do not file tricks as best practice.
What do you hire for if not “can Figma”?
The strongest answer: Framing, a11y judgement, a clean no to a dark pattern, and a leftover in the case — I do not hire for shot volume
Why it works: Exactly. Frame, a11y, no, leftover. Shot volume, never-no, and invented certification percentiles hire theatre.
- Hire framing, a11y, clean no, leftover.
- Not shot volume.
- Not never-no to growth.
- No invented certification percentile.
Careers wants “top-decile design org.” What do you do?
The strongest answer: Take it off unless we have a method I will defend — I do not keep a costume rank to hire
Why it works: Exactly. Method or delete. Safer ranks and sourceless industry are still costumes.
- No costume ranks.
- Method or delete.
- Safer invented ranks are still invented.
- No sourceless industry cite.
Give the one sentence you want a staff design interview to end on.
The strongest answer: If a person tried the job, we own the empty, the error, the name of the control, and the leftover — not a pretty frame
Why it works: Exactly. The moment and the leftover. Tools, PM-only, and invented percentiles are not a throat.
- Own empty, error, name, leftover.
- Not a pretty frame.
- Not only the PM’s throat.
- No invented industry percentile.
A partner wants your onboarding to harvest contacts by default. What do you do?
The strongest answer: Refuse, write why, and do not offer a “research mode” that does the same thing — a default harvest is a dark pattern
Why it works: Exactly. Some jobs you do not take. Tiny unticks, power-user wink, and later-maybe are the pattern.
- Refuse default contact harvest.
- Write it down.
- No wink SKU.
- Maybe-later ≠ a policy.
A candidate says they “aligned everyone.” What do you still want?
The strongest answer: Who we disappointed in the UI, and what we stopped decorating — alignment without a cut is a meeting
Why it works: Exactly. A cut you can see. Nobody-sad, longer workshops, and invented 100% hide the lack of a frame.
- Who we disappointed, what we stopped.
- Alignment without a cut is a meeting.
- Do not aim for nobody-sad.
- No invented 100% satisfaction.