Three ways to improve your InterviewStreet CodeSprint solution
blog.drewinglis.com
blog.drewinglis.com
I've enjoyed the problems nonetheless. If nothing else it's been a good excuse to learn some features of a few languages that I haven't used yet.
While I don't expect anything to come of this employment-wise (and yes, I am looking) I'm glad to have participated.
The other points, about using an efficient algorithm instead of a merely correct one that assumes unreasonably large resources, are more on target.
Before coding any algorithm, always plug in the problem size bounds to your O() function estimate. In these contests there is usually one obvious large number that tells you where your algorithm needs to be sub-quadratic