We’re a very small team with little experience in hiring but got approval for a new engineer. Basically HR will look for people through the usual channels and I think we have a reasonably good job description. Unfortunately the coding challenge (a 30h+ take home) is atrociously difficult and doesn’t really reflect what we do. On the other hand I think the false positive rate would be low. FWIW it’s a Linux application and it might be difficult to only count on experience from the CV.
Any ideas how to build a good challenge from scratch and what time constraints are reasonable?
So what we do is, between the first and second interview we have new candidates recreate Twitter over the span of a week. We stress that you can put in as much time as you want into it as you need and by no means does the site need to be functional at all by the second interview. If they spend 30 minutes thinking about it and are able to have a decent conversation, great!
The point of the assignment, for me, is not to have some barrier of entry for a candidate. Instead, I use the assignment to:
When you look at it like that, the project doesn’t really need to be that complicated. A candidate may be able to fake a challenge, but they can’t fake an interview.