> Then, come the interview, the guy can barely code, much less know the ins and outs of variable scope. It turns out there is very little correlation between how good a resume is, and how the interview actually pans out.
Be careful with this assumption.
Interviews generally measure how well a person responds to anxiety. This can overwhelmingly dominate and mask any signals about their competency.
I can talk about algorithms and data structures all day and have little difficulty solving fairly challenging problems.
Stick me in an interview and, depending on a lot of different factors, I can easily come across like this person. Sure I've built open source libraries, written countless articles, and have given talks at open source conferences but at the end of the day I can't handle 5 hours of talking with people and then do even the most basic tasks. Anxiety and exhaustion will over-ride everything at that point.
Be careful with this assumption.
Interviews generally measure how well a person responds to anxiety. This can overwhelmingly dominate and mask any signals about their competency.
I can talk about algorithms and data structures all day and have little difficulty solving fairly challenging problems.
Stick me in an interview and, depending on a lot of different factors, I can easily come across like this person. Sure I've built open source libraries, written countless articles, and have given talks at open source conferences but at the end of the day I can't handle 5 hours of talking with people and then do even the most basic tasks. Anxiety and exhaustion will over-ride everything at that point.