4 ms·
I think this interviewer was not that bad actually. He checked your problem solving skills, and he ensured you knows some textbook basics. That's fine. Thats wh
by TeeWEE 9y ago
I think this interviewer was not that bad actually. He checked your problem solving skills, and he ensured you knows some textbook basics. That's fine. Thats what we do too: In the first interview ensure the candidate satifies the minimum requirements, and is a problem solver.
- david-gpu 9y agoYou are getting downvoted, but I agree. A first phone _screening_ is meant to discard candidates that are clearly not a good fit for the role. Lots of small technical questions are a good way to go about it. Once you bring the candidate onsite you can ask deeper and more open questions. A phone is simply not a good medium for this.
- Piskvorrr 9y agoI think that the scope of the interview should have been more explicit in such a case - up front, ideally: "this is a first-level interview, I expect it to take an hour and a half; if you're successful, we will get to the specifics in the next one." Without an introduction, an hour of general quizzes would seem excessive to me. OTOH, if the recruiter reacted to this expectations mismatch with an equivalent of "no explanations are given", I would have bailed, too: the interview is a two-way street, and both sides are interviewing - "do I want to work in such a company culture as evidenced by the recruiter"?