|
I've found that there is a counterpart of the nightmare candidate who won't say anything. It's the nightmare interviewer who keeps asking the same question, literally without modification, because you gave an answer that he didn't like and he's too inarticulate to drill down.
|
#
¿
Mar 16, 2016 04:20
|
|
|
|
| # ¿ May 12, 2024 02:18 |
|
|
At the previous employer, the senior engineer on my team was a freemason and research physicist who looked like Nathan Myhrvold. Very professional and knowledgeable guy who I respected. One day I overheard him doing a phone screen: "Do you have any experience with C++?" "Well, if you've used C++ the answer would be yes. If you have not used C++, the answer would be no." That company's strategy for phone screens was possibly the only thing I saw them do well. The basic principle was, ask questions that anyone with the required skills could answer from memory. Nothing clever. Nothing that can be waved away with "I didn't deal with that aspect." You have years of J2EE experience and want to bring it here? Tell me what a servlet is. You just got a CS degree and want your first job? Tell me the differences between an array and a list. Anyone who fumbles these questions doesn't come on-site.
|
|
#
¿
Mar 16, 2016 22:23
|
|