Hmm, this could be a risky approach. If you do it right, it could be a fun, interactive way to suss out a candidate's approach to solving problems, preferred ar

Hmm, this could be a risky approach. If you do it right, it could be a fun, interactive way to suss out a candidate's approach to solving problems, preferred architectures, etc. However, it also feels quite artificial and stressful, which is a bad combo for a lot of people. Unless the position actually requires rapid fire system design and architecture, I'd be cautious using it as a primary filter. For most positions, designing a system architecture includes include some amount of research, reflection, iteration, etc. In other words, you're evaluating something the job doesn't actually require (typically), and you're potentially missing out on people who might be brilliant architects given a little time to absorb the problem and think through options.