Earlier quoted context omitted.
People who ask for more complicated code than "reverse a string" or "fizzbuzz" in a remote code screen is doing it wrong. People who can't code, compile, and run a fizzbuzz in an hour are probably not fit to be hired. Asking someone to implement a proper Diffie-Hellman over Hackerrank is ludicrous, on the other hand. Interviewers should err on the side of stupidly simple problems. A surprising number of people can't…
>A surprising number of people can't code a loop in the languages on their resumes. I guess you can reach two conclusions from that: 1) A surprising number of applicants are totally misrepresenting their abilities – either through deceit or wild ignorance. 2) Something about your interview process makes a surprising number of people unable to perform at their normal level – from nervousness, unrealistic and artificia…
People that suspect they're in category (2) could come to an interview with some code samples. Personally, I'd even be OK if a (2) contacted me after the phone screen with some code samples and an explanation about what happened. Maybe we could set up another phone call and find another way to assess technical abilities.
Good development requires good communication and someone with the maturity to overcome that sort of problem will fit in well somewhere, maybe even on my team.