I completely agree with this; I understand and have sympathy for Ike's position but like you I cannot proceed if I can't establish that you can code. The techni

I completely agree with this; I understand and have sympathy for Ike's position but like you I cannot proceed if I can't establish that you can code. The technical interview is currently the tool I use for that. Having said that, I think that an at-home project prior to the interview is useful both for pre-screening but also as a sanity check on the conclusions of the technical interview - if someone blitzes the project but flunks the interview that would make think that maybe the issue was the interview (or the interviewer) and not the interviewee. Lastly, I think that if someone is aware that they do not do well at technical interviews then the best way to deal with this is be up-front with the interviewer, and try to bolster your case by having some code (perhaps on Github) for them to review. No-one I know likes an awkward or failed interview - we want people to succeed - and if you're honest with me about the issues I'll take that into account.