Not surprisingly, the actual interviews were very technical but mostly fair. The questions were primarily "can you figure out this tricky programming puzzle" type questions, which I generally enjoy, so there were no real surprises or problems.
The recruiting process, however, was surprisingly unprofessional from beginning to end. Some issues I encountered:
I'm not bitter about not getting the job (really. I secured a nice position with an equally "popular" and thriving company shortly thereafter that will remain nameless). I am, however, disappointed with the treatment I received from their recruiting department, given the company's size and reputation.
I suppose the idea is that since everyone wants to work there, mistreating candidates makes no difference in the short term, as there are plenty of others waiting in line to interview. In the long term, however, assuming their recruiting department continues this way, I have no intention of interviewing there again. I've also convinced many other smart friends and co-workers considering this company not to interview as well.
Describe the process, including some code, on how to create a user identifier that could be passed between websites. This identifier should not be spoofed or easily stolen.
Write the code to determine if a 2D point is inside a 2D closed polygon.
The following metrics were computed from 1 interview experience for the Google TSE Engineer and Software Engineer role in Mountain View, California.
Google's interview process for their TSE Engineer and Software Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Google's TSE Engineer and Software Engineer interview process in Mountain View, California.