This question can truly be incredibly interesting.
But I didn't come up with it in a quick Web search and thought maybe I had dreamed it.
That's easy.
Bash checks all the directories as listed in my $PATH, doesn't find it and then prints "api.example.com: command not found" on the screen.
If you want me to tell you how a bluetooth keyboard works you're going to need to pay more than a sysadmin's salary.
There are some poorly paid electrical engineers in the world. There are overpaid under educated sysadmins in the world as well.
I could see myself getting started on a big tangent, and the Interviewer listening politely, then responding with "you're over thinking it; a new line is inserted and the cursor moves to the next line."
> Really a great question for exposing how the candidate models a complex system.
The question could do that, if the interviewer is sufficiently interactive and asks the candidate to explore or explain, but I have yet to experience it. Every single time I've answered the question, the interviewer just sits and listens.
Am I really exposing how I model anything when I'm giving what's now a pretty rote answer, colored by years of reading postings about it?
This has been one of my interview questions for years. Take a minute to speak your answer aloud. Do it now, I'll wait.
It requires walking through several layers and subsystems. Really a great question for exposing how the candidate models a complex system. The best part, as an interviewer, is seeing how deep the candidate goes down the potentially infinite rabbit hole.
The most entertaining answer I've received started with the electrical contact in your ENTER key sending the key code through USB. He briefly digressed into the pinout of PS/2 vs USB, and continued in that fashion.