"here's a high-level description of a fictional product. Let's have a discussion about where you start, what kind of technical and and design discussion you mak

"here's a high-level description of a fictional product. Let's have a discussion about where you start, what kind of technical and and design discussion you make and what goes through your head as you would theoretically tackle this project". Not exactly what you want, but that's still what I'd ask. That will tell me more about the candidate's abilities than syntax questions or other silly things like that. INCLUDING how good they are at syntax and silly things (the way they speak will show it). What I like about these kind of open-ended problems, is that it accounts for variety of backgrounds and skillsets. People can surprise you with solutions and ideas you'd never have thought about. It does require 2 things: 1) make it absolutely clear that this isn't a question with a predefined answer. 2) you have to be open minded about how the candidate answers. Most frontend devs will go through their frameworks of choice, project structures, backend tooling preferences, how they sketch a UI, how they work with designers, etc. I had one once walk me through a complete system architecture analysis. We gave them an offer to lead our devops team ;)