3 ms·
This sounds absolutely awful from a candidates point of view. 48 hours is a very long time for what is effectively an extended technical interview. The hackath
by vilya 15y ago
This sounds absolutely awful from a candidates point of view. 48 hours is a very long time for what is effectively an extended technical interview.
The hackathon format works well for one-off fun events, but no-one should ever be pulling 48 hour coding stints at work. Being charitable, I guess this tests how well people perform under crunch conditions - but would you want to work for a company which is actively planning to crunch?
- rvivek 15y agoHey vilya, there are multiple challenges and short interesting real-world problems. So you can finish sooner, in fact the rank #1 last time finished in 12 hours :) You can checkout codesprint.interviewstreet.com for more info.
- vilya 15y agoEverything on that page gives me the impression that it's a solid 48hrs; maybe you need to adjust the copy? The explanation posted elsewhere on this thread by mikeinterviewst makes it sound more reasonable. I'm probably not your target audience anyway (happily I'm past that stage in my career), but I was also put off by being asked to login in order to see sample questions.