Use evidence of repetition, not a hunch. A pattern earns a place in the system when it has appeared in three or more real contexts, when its behavior is stable, and when someone will own it. Ship the one-off first, let it prove itself, then promote it with clear props, states, and usage guidance. Premature components create abstractions the team fights for years.
Why interviewers ask this
Design system work is judgment about abstraction, and getting it wrong in either direction is costly: too permissive and the product fragments, too strict and teams route around the system entirely. Interviewers want to hear a threshold you actually apply, plus an understanding that a component is a maintained contract with an owner, a deprecation path, and documentation, not just a Figma file.
How to structure your answer
- Set a repetition threshold before you promote anything.
- Let the one-off ship and prove the behavior is stable.
- Define the contract: props, states, content rules, and what it is not for.
- Assign an owner and a deprecation path before it goes in.
Example answer
My rule of thumb is the rule of three. The first time, I just build it. The second time, I note the duplication. The third time, I look at all three and ask whether they are really the same thing or three things that happen to look alike. That last question matters, because the classic design system failure is merging two patterns because they look similar and then bolting on a variant every time they diverge, until you have a component with nine boolean props nobody can use safely. When I do promote something, it comes with a real contract: the states including loading, empty, error and disabled, the content rules, and a short 'do not use this for' section, which prevents more mess than the usage guidance does. And it needs an owner. On one team we shipped a beautiful system that decayed within a year because nobody owned it, so teams forked components locally and after eighteen months we had four kinds of dropdown again. Governance is unglamorous, but it is the actual job.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you handle a team that wants to break the system for one screen?
- How do you deprecate a component that is used everywhere?
- How do you keep the Figma library and the code library in sync?
Related ux designer questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions