A UI design interview is mostly you talking through your own screens while someone pokes holes in them. The questions below come from portfolio reviews, app critiques and whiteboard exercises, and each one tells you what the interviewer is really listening for. Prepare stories, not definitions.
This is the whole interview in miniature. They want to see if you can tell a clear story about a problem, your decisions and the result without drowning them in screens.
Most UI roles live inside a system. They want to know if you add to it carefully or just detach instances and make one-offs.
Handoff friction is constant. They're checking whether you treat engineers as partners or as people who got it wrong.
Accessibility separates designers who have shipped to real users from those who've only made mockups. Many teams are also under legal pressure to get it right.
This tests whether you notice details and can explain them in design language without being cruel or vague.
Responsive work is where many portfolios fall apart. They want to know you think in layouts that flex, not fixed frames.
This is core craft for a UI designer. They want a system behind your taste, not just taste.
Empty, loading, error and disabled states are where real products look broken. Designers who cover them save engineers guesswork.
Design reviews are blunt. They're checking whether you can defend a decision without getting defensive.
Deadlines cut design work constantly. They want to know you can ship a simpler version without losing quality.
It shows your taste and whether you study other products with an eye for why they work.
They want proof you've actually used it and thought about it as a designer.
Ask at least two. It shows you're picking them too.
