News for hackers. Stuff that matters.
Re:We analyzed thousands of interviews on everything from la... by 11thEarlOfMar on Thursday June 15, 2017 @12:21PM (#14561790)
Do you have data that shows how fast and easy the take home test approach is so I can compare? I only have anecdotal data.

I do give candidates the option of the take home vs. white boarding. So far (it's admittedly still a pretty small sample) they've all opted for the take home. However, we'll take a look at this approach as well.

Re:We analyzed thousands of interviews on everything from la... by lj3 on Thursday June 15, 2017 @07:56PM (#14565489)
> Do you have data that shows how fast and easy the take home test approach is so I can compare? I only have anecdotal data.

I'm not aware of any solid data around take home tests. All I can give is yet more anecdotal data, which is that they take a lot of time on both ends. So much time, in fact, that I've had several interviews where the interviewer never looked at the test code I was required to send in. Whether they work or not is irrelevant if nobody ever looks at the code.

Re:We analyzed thousands of interviews on everything from la... by 11thEarlOfMar on Friday June 16, 2017 @03:06AM (#14567143)
I see. The take home assignment is not a test or exam, per se. It's code sample that responds to one of 6 coding tasks. We expect something around ~100 lines, typically in C. The candidate leads a code review of their code by the team when they return for the second 2 hour interview. The code review usually takes about 45 minutes. The remaining 1:15 is 1-1 interviews. So we can assure candidates that someone reviews the take home assignment as they lead that review.