News for hackers. Stuff that matters.
Re:How to Catch a Cheating Candidate in an Interview by exabrial on Sunday October 24, 2021 @10:38PM (#28983986)
I mean, the other option is to stop asking irrelevant questions that "need" to be gamed...
Re:How to Catch a Cheating Candidate in an Interview by jfalcon on Monday October 25, 2021 @05:30AM (#28985937)
I agree. Google will often ask the "number of marbles in a jar" question to see if you can think in scales using abstract statistics in their interviews. Now if you suck at math but are just fine in logic and code writing, should this limit you? When I interview people, I'm being attentive to show the interviewee respect but to also catch misrepresentations.

Most people don't code without having reference material available because unless it's just rehashing old code all the time for the same project, you're likely adding or optimizing something about your project. Same with every other part of the infrastructure and service matrix.

Re:How to Catch a Cheating Candidate in an Interview by singron on Monday October 25, 2021 @10:02AM (#28987906)
Fyi brain teaser questions have been banned at Google for many years.
Re:How to Catch a Cheating Candidate in an Interview by WalterGR on Tuesday October 26, 2021 @04:06AM (#28997645)
And at Microsoft.
Re:How to Catch a Cheating Candidate in an Interview by aitchnyu on Monday October 25, 2021 @02:51AM (#28985086)
I once had a candidate who Googled answers for an interview. At first, his pauses were almost believable. I slowly progressed to more conceptual questions and he didnt realise he was spending too much time before reading out stuff verbatim.
Re:How to Catch a Cheating Candidate in an Interview by gopher_space on Monday October 25, 2021 @09:13AM (#28987376)
I think the assumption here is a non-technical interviewer filling low value roles.