Start with an audit and a business case, not a rebuild. Inventory the components that actually exist in production, count the variants, and quantify the cost in engineering time and bugs. Then fix the highest-traffic, highest-pain surface first and extract shared foundations from real work: color, type, spacing, then the two or three most-used components.
Why interviewers ask this
Most design jobs are not greenfield, and a candidate whose instinct is to propose a full redesign in month one is a risk. Interviewers want sequencing, prioritization, and political awareness: how you earn the right to do system work by shipping something valuable first, and how you get engineering to adopt a system rather than just admire it.
How to structure your answer
- Audit what exists in production and count the variants.
- Translate the inconsistency into engineering cost and user confusion.
- Fix one high-traffic surface end to end to build credibility.
- Extract foundations (color, type, spacing) before components.
- Get engineering to co-own the system from the first component.
Example answer
I would not open with a redesign proposal, because nobody has any reason to trust me yet. First month is an audit. I screenshot every screen and pull the actual CSS with an engineer, and the output is usually shocking in a useful way: on one product we had fourteen shades of grey and nine button treatments, four of which were the same design implemented four separate times. That artifact does the persuading for me, much better than a manifesto about consistency. Then I put a number on it: how long a new form takes to build today versus with shared components, plus the accessibility failures we would have to fix anyway. Then I pick one high-traffic flow, ideally one already on the roadmap, and do it properly, extracting tokens for color, type and spacing as we go. Real components come out of real work, not from a designer sitting alone building a library nobody asked for. And an engineer co-owns it from day one, because a system that only exists in Figma is a mood board.
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 get engineering time for system work?
- What do you do about the screens nobody wants to touch?
- How do you measure whether the system is being adopted?
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