[ChadB]

My Google interview a few years ago was very similar. No matter how confident you are, it's amazing how nerves can cause you to stand there at the whiteboard babbling like a newborn.

Google actually had me do two on-site interviews (one in my hometown and one in Mountain View). The first one went very well. I had a great rapport with the (single) interviewer, and had fun solving the (single) problem he gave me.

The Mountain View interview went more or less like the one described in the article. Marathon style. Had good rapport with some of the interviewers, less so with others. Once you start stumbling your confidence starts to fall apart, and it can really hurt you for the rest of the day (the interview lasted all day).

I also didn't exactly end up with the job. They offered me a testing position with "fast-track" promotion to engineering. I passed on that.

Good advice in the article though: practice problems on a whiteboard at home or with friends. Especially fundamental problems that you learned in your first algorithms class and the like.

[nihilocrat]

Yeah, when was the last time you wrote code on a whiteboard when you WEREN'T in an interview? Definitely good advice, but I would caution that it's just an interview skill, and only serves to improve your performance rather than your content.

Also, you should remember from your test-taking skills that time asleep is more valuable than time studying. Thus, as pointed out, you should really make sure you're well-rested.