UX Designer
Interview Guide

Both matter but the balance varies by role. At product design roles (like Meta, Google, Spotify), strong visual craft is heavily weighted alongside process. At pure UX or research-focused roles, research rigor and synthesis skills are primary. For most product designer roles, you need both — process to solve the right problem, craft to execute it beautifully.

Include 3–4 case studies showing end-to-end process: problem definition, user research, synthesis, ideation, prototyping, testing, iteration, and measurable outcome. Each case study should tell a story of design thinking, not just show pretty screens. Highlight collaboration with PMs and engineers. Include work that shows you can handle constraints and complexity.

For a structured 45–60 minute interview: 20–30 minutes for your portfolio walk-through (2–3 projects), 10–15 minutes for a design exercise or case discussion, and 10–15 minutes for Q&A. Practice your portfolio presentation until you can do it in exactly 25 minutes — being concise shows respect for the interviewer's time and strong communication skills.

Basic HTML/CSS knowledge is valuable but not required for most UX roles. Being able to prototype in Figma, understand engineering constraints, and speak 'developer language' (responsive layouts, component states, accessibility) matters much more than actual coding. Companies prefer designers who work closely with engineers over designers who try to code everything themselves.