Thanks for the info. My point was more to the tune of - when you can tell so much more from a candidate's github work -- his algo's, coding, coding style, commit notes, commit times, descipline.. why would you want to poke his coding again ? Why not just discuss his prior github work and clear the coding part of his interview ? Agreed on the need to check if you can work with him, team work, problem solving ..etc. But isn't github eliminating the need for vetting coding ? Fake github profiles is surprising! Never heard of that before!