|
|
|
|
|
|
by throwaway4233
1912 days ago
|
|
|
Most hiring interviews involve the interviewer's knowledge about a particular domain, language or framework since it is easier for them to evaluate answers for those given the limited time window they have. If according to this matrix, the interviewee has levels of expertise in each row different from what the interviewer has, then the candidate is bound to appear to fail. I am not implying that this is a bad tool for hiring, just that it is not give a definite impression about the candidate. Over the 6 years period when I have worked as a software developer, my work has been split mostly between python and ruby, solving problems in different domains based on what was required as part of my job. However when interviewing at Ruby or Python dev companies, a lot of questions asked are very specific to language based design patterns/concepts which I end up being unable to answer because of not being aware of the exact vocabulary or because I have never encountered them. Does that make me a bad hire ? Maybe. Maybe not. Does it mean it that the interviewer is asking the wrong questions ? No, they are asking questions on what they have worked on and is possible for them to evaluate. After realizing this while interviewing candidates myself, I allow candidates to search for concepts that they are unaware of, and demonstrate what they understand or how they would use it given 5-10 mins of going through any documentation they find(or I can provide). Because (1) there is a limited amount of information a person can store and reliably extract from memory and (2) just because someone is not aware of a design pattern/concept, it does not imply that they cannot adopt it. |
|
|