Yeah I agree, we can conclude that to some level, we do some testing on site too. Also, if the candidate has done some sort of interview task, we're going to go through code together and talk about it. Those who just copy-pasted code from the net, without understanding it, are easy to spot.
Live coding is good in a reasonable amount, but if someone is expecting from me to code an app from scratch while whole interview team is lookin' at me, I'll just bail out, it's just too weird.
I think it's very insightful.
How does the person react to this stressful situation?
How does he help himself when errors come up?
Does he actually do real TDD?
Does he really think about the architecture or does he start writing some useless stuff?
Can he talk about what he is doing?
How does he react to another person saying something?
Does he write clean code?
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.