Interview Questions for a UI Designer

Walk me through a screen in your portfolio and explain the typography, color, spacing, and layout decisions you made.

What to look for: A clear visual hierarchy rationale, type scale and contrast reasoning, intentional spacing, and decisions tied to brand and usability rather than taste alone.

How do you structure a scalable design system with reusable components and clear usage rules?

What to look for: Component variants and properties, design tokens, naming conventions, documentation of when to use what, and how it stays maintainable as the product grows.

How do you ensure your visual designs meet accessibility standards for contrast, hierarchy, and focus states?

What to look for: Knowledge of WCAG contrast ratios, visible focus indicators, not relying on color alone, and checking accessibility during design rather than after.

Describe your approach to designing responsive, adaptive layouts across device sizes.

What to look for: Breakpoint strategy, fluid versus fixed elements, content prioritization on small screens, and designing for real constraints rather than only desktop comps.

How do you specify interaction states, transitions, and micro-interactions so engineers implement them correctly?

What to look for: Documenting default, hover, active, disabled, error, and loading states, motion timing and easing, and purposeful micro-interactions that aid usability.

What do you include in a clean Figma handoff to make implementation faithful?

What to look for: Organized components, tokens, specs, redlines or auto-layout, edge cases, and partnering with engineers rather than throwing files over the wall.

Tell me about a design system you built or contributed to. What problem did it solve and how was it adopted?

What to look for: A real contribution, governance and adoption challenges, and measurable consistency or velocity gains for the team.

Describe a project where the final implementation drifted from your design. How did you handle it?

What to look for: Partnering with engineers, prioritizing which fidelity battles matter, and using a system or QA process to keep implementation faithful.

Give an example of feedback that significantly changed one of your designs. How did you respond?

What to look for: Openness to critique, separating ego from the work, and iterating toward a stronger outcome.

Tell me about a time you had to balance brand polish with a hard accessibility or technical constraint.

What to look for: A concrete trade-off, refusing to sacrifice accessibility for aesthetics, and a creative solution that satisfied both.

A stakeholder wants a low-contrast, on-trend look that fails accessibility checks. How do you respond?

What to look for: Educating on contrast standards, offering compliant alternatives that keep the aesthetic, and holding the accessibility line.

Your design system component doesn't cover a new pattern a team needs. What do you do?

What to look for: Deciding between a one-off and a new system component, documenting it, and avoiding fragmentation or duplicate components.

You're handed a wireframe from UX that won't translate cleanly into responsive visuals. How do you proceed?

What to look for: Collaborating with UX, proposing layout adjustments, and solving for small-screen behavior without losing the intent of the flow.

An engineer says a micro-interaction you specified is too costly to build. How do you handle it?

What to look for: Understanding the constraint, prioritizing the interactions that matter most, and proposing a simpler version that preserves the purpose.

How do you collaborate with UX designers to turn flows and wireframes into finished visuals?

What to look for: Respecting the UX intent, early alignment, and a shared language about hierarchy and interaction rather than reskinning in isolation.

How do you partner with engineers through handoff to ensure faithful implementation?

What to look for: Proactive specs, being available for questions, design QA against builds, and treating handoff as a conversation not a deliverable.

How do you keep a product visually consistent when multiple designers are contributing?

What to look for: Shared system, usage rules, design reviews, and tokens that enforce consistency across contributors.

How do you give and receive critique in a design review so the work gets stronger?

What to look for: Framing feedback against goals and principles, separating preference from problems, and staying open to critique of their own visuals without defensiveness.