Of course, you have nothing to loose and everything to gain. I think I said this earlier but we ask lots of very challenging. Questions that most people don't get right. The people that call or email us afterwards with a solution we will be much more likely to hire than those that just gave up completely.
Tell them that your mind blanked and you knew of better solution once you jumped in the car. It is normal, especially under stress and pressure of an interview to seize up.
These technical tests are not a flawless indicator of programming ability and a good interviewer should make adjustments. Working under stress of an interview is different to everyday coding and is different to tight deadlines in the job. Last night we had a massive system failure right before a major pot ethical investor was scheduled to make tests and potentially invest millions- we hacked away for into the small hours on the back of a string of 12 hour days and no weekend. I had even stopped for the night and had a few beers! That was coding under pressure, and it was still way different to an interview. Sadly the failure was out if our control.
The thing is there aren't any good alternatives. You can get people submitting code samples but you have no way of knowing how many people contributed, how long they took, what code review process was in place, what help was found from stack overflow etc. And that is if the person has code that they can share, you certainly can't share code form previous employers.
Tell them that your mind blanked and you knew of better solution once you jumped in the car. It is normal, especially under stress and pressure of an interview to seize up.
These technical tests are not a flawless indicator of programming ability and a good interviewer should make adjustments. Working under stress of an interview is different to everyday coding and is different to tight deadlines in the job. Last night we had a massive system failure right before a major pot ethical investor was scheduled to make tests and potentially invest millions- we hacked away for into the small hours on the back of a string of 12 hour days and no weekend. I had even stopped for the night and had a few beers! That was coding under pressure, and it was still way different to an interview. Sadly the failure was out if our control.
The thing is there aren't any good alternatives. You can get people submitting code samples but you have no way of knowing how many people contributed, how long they took, what code review process was in place, what help was found from stack overflow etc. And that is if the person has code that they can share, you certainly can't share code form previous employers.
Last edited: