I read jerich's response and thought he was sarcastic in his praise. Are you serious? This is your one interview question? Do you realize this is the kind of t

I read jerich's response and thought he was sarcastic in his praise. Are you serious? This is your one interview question? Do you realize this is the kind of thing the Sahat was writing against? Instead of actually asking them about their relevant skills, experience, and capability you think it's fit to judge a candidate on what amounts to curious information on how a computer works. Is that what you're hiring for? Someone who's spent more time reading wikipedia articles than actually coding? We're in the business of creating things, not harvesting trivia. Yes it doesn't matter if someone'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. It always shows how deep does one go in their computer science adventures. 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're testing for the completely wrong thing. I am a VP at a medium size company and I do plenty of interviews Here's a secret then. The candidate, whoever he or she is, will always try to answer your question. In fact, they'll try to satisfy whatever problem you put them up to. "What's your favorite method of tying shoelaces?" "How many golf balls can you fit between the earth and the moon?" "What do you do for fun?" The candidate will take their time and rack their brains trying to provide an answer to please you. Some will give a good answer and some will give a bad one, but that doesn't mean your interview question is a good one.