Visual Design Fundamentals

A candidate who can say "I used a 4-point grid" is describing a choice. A candidate who can say "I used an 8-point grid because it maps cleanly onto our 4px-base design tokens and every spacing value a developer needs is a value they can already see in the spec" is describing a reason. Visual design interview questions rarely test whether you know the vocabulary — type scale, contrast, grid, hierarchy — because that vocabulary is Google-able in five minutes. They test whether you can justify a specific number: why 1.5 line-height and not 1.1, why 8px increments and not "whatever looks right," why this particular red for an error state. Interviewers who've shipped product can tell the difference between memorized terminology and a designer who has actually made these tradeoffs under a deadline.

This subject is #7 in the UI/UX Design Interview track. It builds directly on ux-vs-ui-and-the-design-process's framing that UI is a lever on UX, not a separate discipline — everything here is that lever made concrete: the specific typographic, chromatic, and spatial decisions that either serve the underlying experience or actively work against it. It sets up three later subjects explicitly: accessibility-and-inclusive-design (which turns "contrast matters" into exact WCAG ratios and legal requirements), design-systems-components-and-dev-handoff (which turns "constrained scale" into shipped design tokens), and responsive-and-mobile-design (which turns "grid" into breakpoints and fluid layout).

The throughline across every section below is the same: visual design decisions that look like taste are, when you push on them, decisions with a functional justification — and a candidate who can supply that justification on demand is the one who gets hired over the candidate who can only supply the vocabulary.