Ask an open-ended question, tell candidate there are no bad answers, and to go into as deep as possible. For example: What happens if you type ls to the console and press enter?
A shallow answer would be: the directory listing is printed.
A deep answer could mention keyboard interrupts, command to builtin vs. executable lookup, disk IO, inodes..
The answer is a great starting point to see what could some strengths of the candidate be, and explore those in some more depth.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ask an open-ended question, tell candidate there are no bad answers, and to go into as deep as possible. For example: What happens if you type
lsto the console and press enter?A shallow answer would be: the directory listing is printed.
A deep answer could mention keyboard interrupts, command to builtin vs. executable lookup, disk IO, inodes..
The answer is a great starting point to see what could some strengths of the candidate be, and explore those in some more depth.