Design Systems
204 bites tagged Design Systems — interview questions with model answers, and 60-second explainers.
How do you merge a Figma branch and resolve component conflicts?
Review main changes, open conflict picker, compare side-by-side, accept or blend component edits, publish library updates. Figma branching and component conflict resolution.
How do you structure Figma pages for a new project and handoff?
What it tests: systems thinking and empathy for cross-functional workflows. A strong answer names a Cover page, separate WIP and Handoff pages, and a linked component library with consistent naming.
How do you translate Figma Smart Animate into CSS or JS?
Convert easing to cubic-bezier or library curves, match ms values, animate transform and opacity, escalate layout shifts to JS. Bridging design tools to code with fidelity.
How would you architect Figma components and styles for light and dark themes?
This tests token-based system thinking and Figma variable scoping. A strong answer maps primitives to semantic tokens, binds components to semantic variables, and switches modes at the page level.
How do you implement design tokens in Figma for developer handoff?
This tests design-code token architecture. Strong answer shows three-tier system—primitive, semantic, component—matching developer naming, synced via Tokens Studio or native Variables. Red flag: styles with no developer-facing names or single source of truth.
How would you prototype a shared currently playing state in Figma?
This tests global state via Figma variables. Use one string variable for the active track; bind list and miniplayer to it via component properties; wire taps to update the variable. Avoid duplicating state per frame or faking persistence with overlays.
How do Figma Variables and component properties enable theme switching?
Tests binding semantic variable collections to component layers for theme switching. Outline: create Light/Dark modes, apply variables to fills, spacing; override modes on instances. Red flag: separate masters per theme or using colors in component properties.
How would you structure a flexible data table component in Figma?
Tests atomic design and Figma component architecture using slots and booleans. Answer: build a base row with swappable cell slots, booleans for checkboxes, and variant states for hover and selected. Red flag: detached instances or manual overrides per row.
Use Boolean and Text properties to build a flexible card component
Boolean toggles image; Text properties override title and description; auto layout handles reflow. Figma properties to limit variants while keeping cards editable.
Explain the difference between a Main Component and an Instance in Figma
Tests your grasp of Figma's component architecture and update flow. A Main Component is the source of truth; an Instance is a linked copy inheriting its properties. Edits update Instances except overridden values.
How would you use Auto Layout for a complex data table?
Tests systems thinking in scalable component architecture. A strong answer nests Auto Layout frames: Hug for row height, Fill for column width, and component properties for variants. Red flag: manual resizing or flat frames without nested rows and cells.
When should you use Frames versus Groups in Figma?
This tests your grasp of Figma's layout primitives and constraint behavior. A strong answer: Frames own constraints, auto layout, and clip content; Groups only pass transforms to children.
How would you architect a Figma-to-code icon system?
Tests design-to-code systems thinking. Strong answers cover Figma variables as source of truth, automated API exports into transformed versioned packages, and strict naming taxonomy. Red flag: manual SVG exports and developers editing assets by hand.
How do you structure and maintain a Figma component library for scale?
This tests scalable Figma architecture bridging design and engineering. Strong answers cover atomic structure, variant booleans, auto-layout, and Dev Mode docs. Red flag: treating Figma as static mockups without properties or naming conventions.
How do you use boolean properties for optional icon and chevron?
This tests Figma boolean properties for avoiding variant explosion. A strong answer toggles icon and chevron visibility on one component for all four states. A red flag is creating variants for every permutation or manually hiding layers on instances.
How would you implement a light and dark mode theme switcher?
Tests scalable theming via Figma variable modes, not manual duplication. Create a color collection with Light and Dark modes, bind variables to component fills, then switch modes to toggle themes.
Difference between detaching and pushing overrides to main?
Tests component governance: detaching severs the link for local one-offs, while pushing overrides sends instance changes back to the main component globally. Strong answers contrast local versus library-wide scope and name specific scenarios.
How would you structure Figma files for a new design system?
Tests Figma memory limits and library publishing. Strong answers split files by type—tokens, icons, components—and publish each as shared libraries to limit memory and enable parallel ownership.
What is component nesting? Build a profile header from nested components.
Tests atomic design and system scalability. Answer: define nesting as instances inside a parent; describe a profile header using Avatar, Text, and Button instances; note base edits propagate globally. Red flag: one-off layers instead of reusable instances.
How do you let designers swap a component's icon without detaching?
Tests Figma component properties. Answer: apply an instance swap property to the nested icon, set preferred instances from your icon library, and keep it as a component instance. Red flag: suggesting boolean properties or detaching.
How would you structure a complex reusable Figma table with Auto Layout?
Tests nested Auto Layout and component properties for scalable Figma tables. Build atomic hug/fill cells in horizontal row Auto Layout, then stack rows vertically. Expose cell-type swaps via component properties. Red flag: manual resizing or variant bloat.
Figma Constraints vs Auto Layout: when are Constraints preferable?
This tests resizing logic in Figma. A strong answer states Auto Layout resizes frames to fit content, while Constraints make objects respond to parent frames. It then cites responsive containers, say fluid inputs.
Design a flexible Table component in Figma with slots
Tests Figma Slots to avoid variant bloat. Answer: Cell variants; Row as a horizontal Slot with zero padding for dividers/hover; Table as a vertical Slot for rows plus a header Slot; componentize the configured row for bulk edits.
How do you change a nested Button's state from a Card instance?
Tests knowledge of nested component properties in Figma. A strong answer adds a variant property to the nested Button inside the Card main component so its state appears in the Card instance panel.
Get Design Systems bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.