Set conventions and stick to them. Separate exploration from the source of truth, keep one page per flow with a clear ready-for-development section, name layers and components predictably, and use variables and modes for theming rather than duplicated frames. Use branching or clearly versioned pages for big changes, and archive dead explorations so nobody builds from a two-month-old frame.
Why interviewers ask this
Messy files cost teams real money in miscommunication, and an engineer building from an outdated frame is one of the most common sources of rework. Interviewers want to hear conventions rather than personal habits, evidence that you have worked with other people in the same file, and familiarity with current Figma capabilities such as variables, modes, and dev mode.
How to structure your answer
- Separate scratch exploration from the agreed source of truth.
- Make it obvious at a glance what is ready to build.
- Use components, variables, and modes instead of duplicating frames.
- Set naming conventions that survive other people using them.
- Archive or delete stale work so nobody builds the wrong thing.
Example answer
The single most important thing is that anyone can tell in three seconds what is real. So there is a scratch page for exploration where I can be as messy as I like, and a clearly marked ready-for-build section that is the only thing engineering should ever open. If it is not in there, it is not agreed. Inside that, one page per flow, frames named for the state they represent rather than 'Frame 247'. I use variables and modes for theming and spacing, which killed the old horror of maintaining light and dark as two separate files that slowly drifted apart. For anything substantial I use branching so the main file stays stable while I work. And I am ruthless about archiving. The most expensive bug I ever caused was an engineer building from an old frame that was two revisions behind, because I had left it sitting next to the current one with a similar name. Now old work either moves to an archive page or gets deleted.
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 keep engineers from building the wrong version?
- How do you use variables and modes in practice?
- How do you handle a designer who ignores the file conventions?
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