Programmers for frontend, backend, and project management roles. Our hacker team is 5 strong, so you'll be tackling a huge variety of projects. Help fix a horribly broken hiring world by creating the best platform for addictive programming problems and tutorials.
That was how we originally built it, but we found it less fun to rate in testing compared to this version. Hopefully the increased votes-per-person outweigh the loss of fidelity.
The biology revolution is coming, both sooner and later than you think. As one indicator, the price per base pair of DNA synthesis is following a Moore's Law, (http://singularity.com/charts/page73.html), but Fredster is right in that there are other factors at play. However, you could say the same with computers, with bandwidth, cpu, and storage all improving simultaneously.
A story that our TA in EE40 (Signals in Systems) at Berkeley really stuck with me: in the early days of personal computing, when you would go to Radio Shack to buy a set of transistors, you had to individually test each one, because they had a 50% chance of not performing to spec. Biology currently is in that stage, though multiplied by another order of magnitude.
The topic that patio11 mentioned is covered pretty well in chapter 2 of Freakonomics. The actual text doesn't seem to be part of the official sample excerpt, but somebody posted the relevant portion in a forum here: http://www.nachi.org/forum/f11/exerpt-freakonomics-book-rega...
This is not an endorsement of other portions of the book as a whole.
It looks like your privacy settings / a plugin you have installed doesn't allow for even obsfucated email sharing. Normally, what we get for Facebook logins is app+<random_string>@proxymail.facebook.com. This is the first time we've heard of that it's not able to be shared.
Wow, we did not expect to see this level of criticism from the comments.
A lot of the focus is on the 48 hour period, in that it's basically way too long to expect you guys to participate. We don't expect people to code all 48 hours; the decision was basically "make it a weekend long", but we are not tied in any way to that time period. Would it be much better if we shortened the time period to 24 hours? (We can't shorten it any more than that; as this is a global competition, everyone needs to have the same amount of daytime) The goal is not to have you guys burn yourselves out. The goal is to assess you all as quickly as possible.
From our perspective, we sort of viewed CodeSprint as a time saver; everyone you apply to nowadays requires some sort of technical proof. Sometimes you can get away with it if you have a github with a lot of open source projects, but not everyone has that.
With CodeSprint, you get to choose among a variety of problems, and companies with those specific problems get to find you. Because they receive the full code solutions, our goal is for CodeSprint to consolidate and replace the "do-a-technical-problem" part of the normal interview process. Except, this time around, this one set of problems is what's used for multiple companies, instead of just one.
Companies choose candidates on a per-question weighting system. Thus, if you spend only a couple of hours, but on a problem that is valued highly by a specific company, then there's a good chance that they'll still notice you.
He gets the satisfaction of knowing that a company probably solved one of their problems for free by running off with his code while flipping him the bird.
Programmers for frontend, backend, and project management roles. Our hacker team is 5 strong, so you'll be tackling a huge variety of projects. Help fix a horribly broken hiring world by creating the best platform for addictive programming problems and tutorials.
team+mv or team+blr at interviewstreet dot com