Do you really need a full hour to tell if somebody has a good basic grasp of CS and algorithms? I can't see it. At least not in the best case. The way I'd suggest doing it is this: Ask a question that can result in a "1 question yes". That is, pick a sufficiently advanced / interesting algorithm, and ask questions about it, and/or ask the candidate to implement it. If they pass on that, move on from CS/algorithms to something else. If not, move to the 2nd choice algorithm, and repeat. Do that for a few iterations. This way you only fill a full hour if the candidate forces you to dig really deep into your list of topics.
The same methodology could be applied to the other domains as well.
11:00 to 12:00: Computer Science and Algorithms
Do you really need a full hour to tell if somebody has a good basic grasp of CS and algorithms? I can't see it. At least not in the best case. The way I'd suggest doing it is this: Ask a question that can result in a "1 question yes". That is, pick a sufficiently advanced / interesting algorithm, and ask questions about it, and/or ask the candidate to implement it. If they pass on that, move on from CS/algorithms to something else. If not, move to the 2nd choice algorithm, and repeat. Do that for a few iterations. This way you only fill a full hour if the candidate forces you to dig really deep into your list of topics.
The same methodology could be applied to the other domains as well.