Google Developer interview questions

Should be able to code well on paper. I recommend the book "Programming Interviews Exposed"

Google ain't all that. First, their time frame is too drawn out; they schedule in person interviews anywhere from 2 to 4 weeks after the phone screening. Second, it takes most of the day; I had to take a day off for this... unfortunately. Ask if you can break it up in two visits, I felt my answers gradually went downhill after lunch. Third, uneven question quality. The first question I was asked was to implement a remove method on LinkedList (wtf is this - internship position?). The last one had to do with finding a median on an unknown unsorted collection of numbers of enormous magnitude without loading it all into memory. The engineer who asked that one had poor conversational English, making it harder still. All in all, pretty algorithm-specific, very little attention paid to OOD skills, requirements analysis etc. Finally, to give them credit, the onsite interview was Friday, and the decision was made the following Monday because I asked them to accomodate my schedule. BUT: the recruiter never replied to my subsequent email or phone call after I asked him to elaborate on how the decision not to move forward was reached... kinda rude after having someone take all that time to go through the motions. I figured I did well on at least 75-80% of the discussions, so I'd like to know how high the bar is anyway??? One other thing that stood out is that he said I could try again in a year... uh, sure - let me just mark my calendar. All in all, a great place to start your engineering career, but the process is somewhat insulting to a seasoned professional with many years of experience.