3 ms·
Honesty I wouldn't like that, on either side. On one hand it's time consuming, since you simply have to ask other things also - and if you make the problem too
by poisonborz 7y ago
Honesty I wouldn't like that, on either side. On one hand it's time consuming, since you simply have to ask other things also - and if you make the problem too simple or easily guessable, you null the benefits of pair programming. Also I see enough nervous candidates to think their performance wouldn't be realistic in an interview situation. When you solve problems together as colleagues it's a really good method, but as test, its awkward.
- em-bee 7y agowhat other things do i have to ask? your CV tells me your skills. the programming session tells me if we can communicate and work together on a code problem. that's all i need to know. the rest is formalities. the test is only as awkward as every interview is. interviews are awkward because of how we treat the situation, not because of what we do during the interview. the key point is to put the candidate at ease as much as i can. i usually get positive feedback from candidates about my interviews, so i must be doing something right. i have been on the other side of this as well. and i felt that the code task i was given was way to easy to be a skills test, but i also realized that any challenge worth my level of experience would not possibly fit into a one-hour interview session.