The issue is you're given 5 minutes to write a solution, and then criticized for the lack of depth (mercilessly and hilariously, granted). This is actually great practice for interviews, but not great at determining technical depth.
At the level of "five minutes to describe the entire system and its response to the worst confounding factors imaginable" it is not fair to say "You used keywords but didn't describe in detail how ... ".
It also guessed wrong that I'd never done any of this before, probably b/c of above issues.
As a way to belittle someone who self-selected into a skills review in the middle of a workday, probably so that they'll sign up for your training curriculum, then man, I gotta say it's probably going to work well. Especially once it's not an obvious snark generator and learns to cut a little deeper.
The issue is you're given 5 minutes to write a solution, and then criticized for the lack of depth (mercilessly and hilariously, granted). This is actually great practice for interviews, but not great at determining technical depth.
At the level of "five minutes to describe the entire system and its response to the worst confounding factors imaginable" it is not fair to say "You used keywords but didn't describe in detail how ... ".
It also guessed wrong that I'd never done any of this before, probably b/c of above issues.
As a way to belittle someone who self-selected into a skills review in the middle of a workday, probably so that they'll sign up for your training curriculum, then man, I gotta say it's probably going to work well. Especially once it's not an obvious snark generator and learns to cut a little deeper.