[mikeinterviewst]

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.