Google Vs. Microsoft: a Tale of Two Interviews
jfruh writes "You might be a bit jealous of Andrew Weiss: fresh out of college, he got interviews with both Microsoft and Google. He discusses (to the extent NDAs allow) the differences between the two experiences, ranging from the silly (Google's famous gourmet cafeteria vs. Microsoft's gaming room) to the serious (Google's technical emphasis vs. Microsoft's focus on explanatory and consulting skills.)"
He went in unprepared for possible the toughest IT interview of his life and he did not get the position. BIG SURPRISE. then he had some job leads spoon fed to him, interviewed at a few other places and nailed the MS interview. the end. saved you the 45 seconds it takes to read it. the position at MS was more MIS/marketing, and they asked "softer" questions, big whoop. Just some ivy league brat who didn't nail his first interview, and wanted a way to bitch.
Here's my experience in Google vs Amazon
In summary, Google's interviews don't get a flying rats behind about anything but microbenchmarks on small pieces of code. Amazon cared more about technical design but started asking me questions on the Linux Kernel (I was applying for Java Engineer position)
Some more odds:
One of the Google interviews disagreed with me that a Java HashSet was not Big O(1) for the contains() method when I wrote out my sample code. I pointed out (very kindly) that I believe HashSet is backed by HashMap in Java, which is constant time. He said he didn't think that was true and I conceded and said, "I can assume then for now that it is not constant time then." I was extremely polite, but I'm fairly certain that cost me the job.
The Amazon interview didn't go after they started asking me the internals of the Linux kernel. Then, the gentlemen asked me to implement a C function. I stopped him immediately after he was done speaking and said, "There must be a mistake, while i'm more than willing to attempt this in C, I thought I was applying for a Java position." He said he didn't know Java and asked me to implement atoi() in Java then. Needless to say he wasn't satisfied with any iteration of my Java code and made it a point that C was far superior to Java when we were done.
I really wanted the Google job, and I feel I was definitely qualified. What makes me feel better about it I guess is that it seems some Googlers couldn't pass the Google interview.
Not to mention that I'm sure both Google and Microsoft employ plenty of minimum wage workers...
Actually Google singlehandedly raised the "minimum wage" across the Silicon Valley back in the day with all other tech giants having to catch up to avoid losing talent... don't sound so bitter man...
Bow before me, for I am root.
Out of curiosity, what is the difference in the amount of money paid to Google for the software you want help with versus what has been paid to Microsoft?