3 ms·
Totally agree that the aim is to minimize false positives. although I think you could devise the pair programming type interview to still allow for 1 hour chunk
by jwoah12 11y ago
Totally agree that the aim is to minimize false positives. although I think you could devise the pair programming type interview to still allow for 1 hour chunks with many different people doing the sessions. A good phone screen should be able to filter out candidates who obviously don't have the foundation, and watching them code in a (semi)realistic environment can tease out things like resourcefulness, search IQ, etc. I find those things to be better indicators than the ability to find the distance between two nodes in a binary tree.
- rco8786 11y ago> I think you could devise the pair programming type interview to still allow for 1 hour chunks I try and do my interviews this way. While I am required to use the whiteboard and the interviewee is required to write on it, I try to make it as clear as possible that we can brainstorm/strategize on the problem together. Of course I've asked the same few questions probably 100 times now and have seen them solved every which way so I have to play a little dumb sometimes. Same problem occurs in a "real" pair programming environment too, though. Interviewing is hard, and it's easy to throw stones at companies who don't do it the way you want it done.