News for hackers. Stuff that matters.
Re:Cracking the Coding Interview Tutorial by stale2002 on Tuesday September 27, 2016 @06:41PM (#12593841)
Agreed. HackerRank works great as an 'initial' filter. The way to use it correctly is to ask people a couple fairly easy questions, because if they can't pass the easy stuff, then you shouldn't waste their time with a full onsite. A person who is at least moderately capable, shouldn't at all struggle with your initial filter.

Save the tough questions for the onsite interview, where an interviewer can subjectively make judgments about their performance.

Re:Cracking the Coding Interview Tutorial by gaylemcd on Tuesday September 27, 2016 @08:17PM (#12594448)
Or, ask two questions, where (on at least one) it's fairly easy to get an inefficient solution, but requires more thought to get a more efficient one.

You don't necessarily demand perfection on this test though.

One mistake that companies make is that they think they want to set a lower bar, so they make the questions easy. But then, in order to distinguish candidates, they basically require perfection. Now, a simple mistake can "fail" a good candidate.

It's better if they make the questions harder, but just don't require perfection.

Re:Cracking the Coding Interview Tutorial by stale2002 on Wednesday September 28, 2016 @07:20PM (#12602124)
Oh god I know what you mean.