That's the problem. I think everyone is too focused on technical prowess and forgetting something just as important which is written documentation and explanation.

Pair programming has the downside of selecting people with good interpersonal skills and will tell you nothing about quality of code delivered.

A good middle ground I believe is simple takehome tasks with focus on documentation that could be done in no more than two to four afternoons.