I'm late to the party, but I'll provide my two cents as someone who worked at Google and interviewed candidates (most engineers there are trained to do intervie

I'm late to the party, but I'll provide my two cents as someone who worked at Google and interviewed candidates (most engineers there are trained to do interviews): 1. Your resume looks good and should get the recruiters attention, and 2) that's about all your resume is good for, in my experience. Interviewers will look at what you've done in the past to help decide what questions to ask, but your answers to those questions are far more important than your past experience. As others have said, review your basic algorithms and data structures. Be prepared to write correct code on the white board (not pseudo-code, at least not as your final product). Finally, if things don't work out at Google - why not submit your resume to OpenX (http://openx.org/jobs http://openx.org/jobs or email me joel at openx dot org)? We're also hiring :)