Lorin Hochstein 
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code.
rk: it’s hyphen-minus actuallyI hate live-coding interviews. If someone is watching me, I forget how to even type. Obviously my 30+ years of writing code, all my open source stuff, my extensive resume, all those papers and conference presentations were just me faking it.
Peter Ludemann@rk
With all due respect, I've had to work with code written by well-respected researchers and afterwards I concluded that it would have been easier to have rewritten from scratch - in one case, someone, who I think was "reviewer 2" on one of my papers, had written code so buggy as to be useless for anything except the specific examples in the research paper.
(To be fair, I've also had similarly painful experiences with code written by programmers with a good reputation)
Having said that, the whiteboard coding exercise isn't a good way to evaluate programming ability.