IntermediateTECHNICAL
Describe a specific project where you created or extended a design system. How did you define components, states, and tokens, and what steps did you take to ensure consistency across multiple designers and developers?
UI/UX Designer
General

Sample Answer

On the "General Commerce Platform" redesign, I led the effort to extend our design system to support a new B2B checkout experience across web and mobile. We were using Figma and a React/TypeScript front end with a shared component library in Storybook. I started by auditing 40+ screens to identify divergent patterns in inputs, CTAs, and cards. From that, I defined a token taxonomy: color (semantic + functional: `color-bg-surface`, `color-text-error`), typography (heading/body scales), spacing (`space-4/8/12`), and radius/elevation. Then I rebuilt core components in Figma—Button, Input, Dropdown, Toast—with explicit properties and variants for size, hierarchy, and state (default, hover, focus-visible, disabled, error, loading). Each component had usage guidelines, accessibility notes (WCAG 2.1 AA contrast, focus states), and do/don’t examples. To ensure consistency, I partnered with a frontend lead to map Figma components to React components 1:1, using tokens exported via Style Dictionary into CSS variables. We set up a weekly "Design System Guild" with 6 designers and 4 engineers to review new patterns, plus a contribution checklist and change-log. Within two quarters, we reduced one-off components by 60%, cut design-to-dev QA bugs by 35%, and decreased average feature UI build time by ~25%.

Keywords

Mention specific tools and stack (e.g., Figma, React, Storybook, Style Dictionary)Explain how you defined tokens (color, type, spacing) and tied them to componentsDescribe component states and variants in concrete terms, including accessibilityShow collaboration process with developers and other designers (guilds, reviews, contribution model)Quantify impact (reduced inconsistencies, bugs, build time, or maintenance overhead)Highlight governance: documentation, change management, and naming conventions
Related Questions

Based on your hydrology and irrigation engineering background, explain how you would estimate the irrigation water requirement for a kharif crop in a semi-arid region of Gujarat. Walk me through each step: from reference evapotranspiration estimation, crop coefficient selection, effective rainfall calculation, to arriving at canal discharge for a given command area.

IntermediateTECHNICAL

In your civil engineering studies, what specific design coursework or project work did you complete related to irrigation channels or canals (e.g., design of lined/unlined canals, distributaries, minors)? Describe one such design in detail, including how you determined discharge, permissible velocity, section dimensions, and lining choice for Gujarat-type soil and climate conditions.

IntermediateTECHNICAL

Walk me through a recent multi-channel digital marketing campaign you managed end-to-end. How did you set objectives, choose channels, allocate budget, and measure success?

IntermediateBEHAVIORAL

In your resume you note improving or optimizing [a process, KPI, or metric]. What specific baseline metrics did you start from, what steps did you personally take, and how did you verify that the improvement was due to your changes rather than external factors?

IntermediatePROBLEM_SOLVING

On your resume you mention working on a cross-functional project (e.g., involving multiple teams or stakeholders). Describe a situation from that project where priorities conflicted—how did you navigate the trade-offs and what was the final outcome?

IntermediateSITUATIONAL