General familiarity is cheap. Ask which version, and what changed in it, and you separate the people who've read about a system from the people who've shipped on one.
I added one question to our interview pipeline this cycle, and it’s done more screening work than questions twice its length. It’s almost nothing: “Which design system are you most fluent in, platform-native or Material, and which version?” That’s it. The version is the whole question.
Which design system are you most fluent in, platform-native or Material, and which version?
The reason it works is that general familiarity is cheap, and nearly everyone has it. Anyone can say they’ve worked with Material, or that they know the platform conventions, and it’s true enough to be useless as a signal. But the moment you ask which version, and what changed in it, you separate the people who have read about a system from the people who have actually shipped on top of one and felt it move under them. The strongest candidate this cycle answered that without blinking: current on this year’s releases, specific about what shifted and why it mattered for the work. A weaker one went vague exactly there, at the version, which is where the shipping leaves its fingerprints.
What I like about this is what it says about expertise in general. Depth doesn’t show up in the broad claim, it shows up in the specific. The person who’s done the work knows which version, knows what broke and what got better, knows the thing you only know from having been there when it changed. You can’t fake that texture, and you can’t pick it up from a summary. It’s the residue of real time spent inside a craft.
It’s changed how I listen in interviews, and not only about design systems. When someone makes a broad competence claim, the useful follow-up is the one that asks for the version, the specific, the detail that’s only available to someone who was actually there. Not to trip them up, but because the specific is where the truth of the claim lives. Anyone can describe the shore. The person who’s been there can tell you about the bridge.
The whole move costs one extra sentence in a conversation, and it reliably tells me more than the polished portfolio walkthrough that came right before it.
The teachable part
General familiarity is cheap, and almost everyone can claim it. The signal lives in the specific: ask not whether someone knows a system, but which version, and what changed in it. Real expertise leaves a texture, the detail you only have from having been there when something shifted, and you can’t fake it or get it from a summary. When you’re weighing a competence claim, design or otherwise, follow it to the version. The specific is where the truth of the claim lives.