3 ms·
Great article! For 15 years I have conducted interviews and been the victim of the interview process. Your article sounds familiar; I have been telling my wife
by utahmadmike 16y ago
Great article! For 15 years I have conducted interviews and been the victim of the interview process. Your article sounds familiar; I have been telling my wife the same thing (out of frustration) for years. On several occasions I have made it through 3 or 4 levels of the interview process and then blocked in the final interview-step by an insecure or egotistical technical person.
I would add the following (problem) points as well.
* Some technical people like to hire clones of themselves, creating conflict and diversity issues.
* Some technical people, conducting the interview, use the interview process to posture and show how smart they (the interviewer) are.
* According to the BLS, the demand for programmers is decreasing while demand for analysts is increasing. Programming has changed a lot with tools like intellisense and included libraries.
* If you can’t answer the question, "why did you ask that question?", you should not ask the question. Each interview question should have a specific targeted purpose.
I hope my additions help.
http://www.linkedin.com/pub/michael-pritchard/3/93b/4ba http://www.linkedin.com/pub/michael-pritchard/3/93b/4ba
- utahmadmike 16y agoAlso: * Realize that answers to questions like "what is abstraction" might vary from one text book to the next. * Establish context for your interview questions. I was once asked "What is Application?" (too vague). In response I said, "In what context?" The interviewer smugly said, "What comes to mind?" . . . He did not like my answer. Hum?