i used something like this in unstructured technical interviews all the time.
reply"you type a phrase into google search, you press enter, get some results. tell me, in technical detail, what happened in that chain of actions"
the diversity of replies is fascinating, you learn a lot about a "full stack" candidate this way.
Feynman's classic "Why?" chain: https://www.youtube.com/watch?v=36GT2zI8lVA
I'd probably spend at least 20 minutes just to get through how the keyboard works, much more if it's a USB-HID device.
replyHah - that is exactly what I did. Someone asked me this question and after 5 minutes in the weeds of the debounce on the mouse click they said "look all we wanted was to find out if you'd ever heard of DNS, let's move on, that was great".
replythe good ones would usually follow up with, "how much detail do you _really_ want ;D"
replyA great response is "What exactly do you want to know?", so we don't end up like Cliff giving answer after answer. In his case it was a great test question, but such a vague question is a horrible communication tactic if abused.
replyIt's reminds me of that scene from Fargo: "He was kinda funny lookin'" ... "Could ya be any more specific?"
replydeleted
reply