What is the most efficient way to update a brand color globally?

WHAT THIS TESTS: This question evaluates whether you understand the architectural difference between Figma variables and styles in the context of a scalable design system. Specifically, it checks if you know that variables are purpose-built for single raw values like hex codes, while styles handle composite properties. The interviewer wants to see that you think in terms of tokens and propagation rather than manual labor.

A GOOD ANSWER COVERS: First, create a color variable in a published collection to store the raw hex value of the primary brand color. Second, apply that variable to every component layer and instance that needs it, ensuring the binding is direct rather than hard-coded. Third, publish the variable to the team library so all consuming files receive updates. Fourth, when the brand color changes, edit the single variable value and the update will cascade instantly across all components and instances without opening them individually. Mention that variables support modes, which future-proofs the system for themes like light and dark.

COMMON WRONG ANSWERS: Suggesting you select every component and change the fill manually is a critical red flag that reveals a lack of design system thinking. Proposing a color style is also incorrect for this scenario because color styles are built for composite stacks such as gradients, multiple fills, or blend modes, whereas a brand color is typically a single raw value. Another weak answer is confusing variables with local overrides, which does not provide true global token management.

LIKELY FOLLOW-UPS: The interviewer may ask how you would handle the same change if the brand color needed to shift between light and dark modes, which is where variable modes shine. They might also ask what you would do if the brand color were part of a gradient or required an image fill, in which case a color style would be appropriate because styles can hold multiple raw values and complex formats. You could also be asked how publishing and library updates work when multiple files consume the same variable collection.

ONE CONCRETE EXAMPLE: Imagine your primary brand color is a solid blue stored as a variable named brand-primary. It is bound to 50 button instances, 10 navigation bars, and 4 card variants across 3 files. When marketing decides to shift from blue to teal, you open the variable collection, change the hex value from 0066CC to 008080, and every bound layer updates simultaneously within seconds. If you had used a color style instead, you could still update globally, but you would be using the wrong abstraction for a single raw value and would lose the ability to easily map that same token to a different value in dark mode without creating an entirely new style.