UI Designer Interview Questions

UI focuses on the visual and interactive surface — typography, layout, colour, components, states. UX focuses on the problem and flow — research, information architecture, usability. In practice many roles combine both under the Product Designer title, and pure UI roles are most common at larger organisations with dedicated researchers, or in agency work. Read the responsibilities rather than the title: if the posting emphasises research and discovery it is a UX role regardless of what it is called.

High-craft work with visible reasoning. Show the typographic scale and spacing system you used, not just finished screens; show component sets with their states and variants; show a before and after where you fixed a hierarchy problem and can articulate why the new version works. Reviewers are assessing craft directly, so quality of execution matters more here than in UX portfolios — but decoration without rationale reads as styling rather than design.

Enough to not ship something excluding people, and it is increasingly asked about directly. The practical minimum is colour contrast ratios and how to check them, focus states and visible focus indicators, touch target sizing, and not using colour alone to convey meaning. A common interview question is what you do when the brand palette fails AA contrast — a strong answer involves adjusting values for interface use while preserving brand identity, rather than either ignoring it or refusing to work.

Not to build production interfaces, but understanding how CSS layout actually behaves makes your designs far more likely to ship as intended. Knowing what flexbox and grid can do, how components handle overflow and long content, and what is expensive to build changes the designs you produce. Designers who hand over compositions that cannot responsively survive real content are the ones engineers quietly redesign.