I read jerich&#x27;s response and thought he was sarcastic in his praise.<p>Are you serious? This is your one interview question? Do you realize this is the kind of thing the Sahat was writing against?<p>Instead of actually asking them about their relevant skills, experience, and capability you think it&#x27;s fit to judge a candidate on what amounts to curious information on how a computer works.<p>Is that what you&#x27;re hiring for? Someone who&#x27;s spent more time reading wikipedia articles than actually coding? We&#x27;re in the business of creating things, not harvesting trivia.<p>Yes it doesn&#x27;t matter if someone&#x27;s written and maintained code, documentation, tests, and has collaborated with dozens of other individuals for a repository used by thousands. All you need is to do is ask him your pet trivia question.<p><i>It always shows how deep does one go in their computer science adventures.</i><p>Knowing about the adventure of one electric signal from keyboard to underwater fiber cable has nothing to do with computer science. By your own words, you&#x27;re testing for the completely wrong thing.<p><i>I am a VP at a medium size company and I do plenty of interviews</i><p>Here&#x27;s a secret then. The candidate, whoever he or she is, will always try to answer your question. In fact, they&#x27;ll try to satisfy whatever problem you put them up to.<p>&quot;What&#x27;s your favorite method of tying shoelaces?&quot;<p>&quot;How many golf balls can you fit between the earth and the moon?&quot;<p>&quot;What do you do for fun?&quot;<p>The candidate will take their time and rack their brains trying to provide an answer to please you.<p>Some will give a good answer and some will give a bad one, but that doesn&#x27;t mean your interview question is a good one.