What is a design system and why do teams use one?
What the interviewer wants to hear
- Shared library of components, patterns, tokens and guidelines
- Used by both design and engineering
- Brings consistency and speed
- Needs documentation, ownership and maintenance
Model answer
A design system is a shared set of reusable components, patterns, design tokens and guidelines that both designers and developers use to build a product. It usually includes things like buttons, inputs, modals, colour and spacing tokens, typography rules, and guidance on when to use each pattern, plus matching coded components. Teams use it for consistency, so the product feels like one product even when many teams work on it. It also saves time, because people do not redesign or rebuild a button every sprint, and it improves quality, since accessibility and states are solved once. A design system is a product in itself. It needs owners, documentation, versioning and a way for teams to request or contribute new components, otherwise it gets out of date and people stop using it.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy UI/UX Designer questions
- What is the difference between UI and UX design?
- Walk me through your design process.
- What is usability testing and how would you run a simple one?
- Why does accessibility matter, and what basic things do you check in your designs?
- How do you create visual hierarchy on a screen so users know what to look at first?
- What does designing mobile first mean, and why is it useful?
- What are Nielsen's usability heuristics, and how do you use them in your work?
- How do you set up and use components in Figma so a design stays consistent and easy to change?
- What makes a good form? Walk me through the principles you follow.