Timeline for Given a 'homework' tasks on a job interview?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2014 at 17:33 | comment | added | dyesdyes | The do homework can be useful for far away candidates. Not all candidate can afford it. In this case, it's a good compromise I think | |
| Jan 29, 2014 at 4:51 | vote | accept | Bor | ||
| Jan 29, 2014 at 3:12 | comment | added | Móż | Yes. I'd love to hear from someone who does give take home tests. | |
| Jan 29, 2014 at 2:13 | comment | added | Kate Gregory | No argument from me. I don't do take home screeners pre interview and I do whiteboard tests in interviews. Just explaining the possible thought processes of those who give take homes. | |
| Jan 29, 2014 at 2:12 | comment | added | Móż | Definitely agree that sitting with candidates and watching them code is time-consuming, but it's incredibly effective. And only rarely does a candidate I'm doubtful about turn out to be a competent coder, so over time I've got more vigorous about cutting that session short. I can't see how letting them go away and work on it would help that process, what I want to see is how they approach the problem. | |
| Jan 28, 2014 at 13:31 | history | answered | Kate Gregory | CC BY-SA 3.0 |