Make the token layer the single source of truth: colors, spacing, typography and radii live as named tokens that both the design tool and the CSS consume, so a change is made once. Build components against tokens rather than raw values, review new one off values as design debt, and publish the component library with documented props so product teams compose instead of forking.
Why interviewers ask this
This is a collaboration and maintenance question. The interviewer wants to know whether you can absorb design changes without a rewrite and whether you push back constructively when a mockup invents a fourteenth shade of gray. Talking about tokens, documentation and a contribution path shows you have worked in a team where the frontend is shared rather than owned by one person.
How to structure your answer
- Anchor on tokens as the shared contract.
- Explain how a change propagates from design to shipped CSS.
- Describe the review path for new values or components.
- Mention documentation and how consumers discover components.
Example answer
The thing that actually keeps it in sync is having one source for the primitives. Colors, spacing, type scale and radii live as tokens, exported to CSS custom properties for the code and consumed as variables in the design tool, so when a brand color changes it changes in one place and everything picks it up. Components then only reference tokens, never raw hex values, and our lint rules flag a hard coded color in a pull request. When a mockup introduces a value that does not exist, that is a conversation rather than a silent addition: usually it was unintentional, and occasionally it is a real gap and we add it deliberately. For components I keep a documented library with the props and states visible, so product teams can see what exists before rebuilding it, and there is a clear path to contribute back when something needs a variant. The failure mode I have lived through is a system nobody could find, so four teams each shipped their own button, and by then consolidating it was a quarter of work.
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 product team that needs a variant the system does not have?
- How do you roll out a breaking change to a shared component?
- How do you keep theming and dark mode manageable through tokens?
Related frontend developer 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