One of the goals of technical interview (or any interview) is to find your real charterer (are you lazy? do you break when you do not find a solution? are you c

One of the goals of technical interview (or any interview) is to find your real charterer (are you lazy? do you break when you do not find a solution? are you creative?) The quickest way to do that in a 45 min, is to put the candidate under pressure. The best way to put a developer under pressure is to ask coding questions and expect some solution in a very short time. Note that the goal is NOT to find out if you know the ins and out of a specific algorithm. It is to discover how you think under pressure.