Surprising that they gave such detailed feedback. That's usually a big no-no. And for a good reason as we can see here. If the candidate disagrees with the feedback, he will get angry. But good luck with the search.
I interviewed with one of the bigger org's at MS in Seattle about a month ago, they told us that they would be unable to give us feedback if we didn't receive an offer. I suppose different branches of MS could do things different? Fortunately I didn't have to worry about that, starting this summer :)
How I was rejected at Microsoft
11–20 of 22 posts
Re: How I was rejected at Microsoft
#12Earlier quoted context omitted.
I interviewed with one of the bigger org's at MS in Seattle about a month ago, they told us that they would be unable to give us feedback if we didn't receive an offer. I suppose different branches of MS could do things different? Fortunately I didn't have to worry about that, starting this summer :)
I was also surprised about the detailed feedback. I was not expecting that. It was too superficial to help you to improve. I can say that I interviewed for Microsoft Dublin.
I have also felt the hurt of rejection.. I got in a few stages at Google, got dumped. I made it to a final interview at Apple, and they bailed. Applied to Pixar, Mozilla, 10gen, twitter, etc... also with little to no word back at all.
Honestly I feel like the #1 thing I learned from my job search is that the interviewer you get has a insane impact on the outcome. This is especially true of technical phone interviews, I felt like I was literally unable to communicate with some of the interviewers at google because of a language barrier. The whole process seems heavily based on luck.
Re: How I was rejected at Microsoft
#13Surprising that they gave such detailed feedback. That's usually a big no-no. And for a good reason as we can see here. If the candidate disagrees with the feedback, he will get angry. But good luck with the search.
Re: How I was rejected at Microsoft
#14Re: How I was rejected at Microsoft
#15This is actually common. You're right, the HR person wouldn't know what a compiler is, she is following a script with admissible answers to the problems and just listening for keywords that show you have the bare knowledge to pass the screening interview.
From the tone of your comments about the interview, it sounds like you seemed shocked at some questions, thought they were simplistic, etc. and probably let this show. This, I think, was the biggest factor why you didn't get it. Many interviewers have no idea how to interview, and they ask pet questions culled from online sources and friends. If they get the idea that you find some question simple or "beneath you" they take it personally.
So, lesson for next time: React to all interviewer questions equally and control your frustration.
Re: How I was rejected at Microsoft
#16With that said, implementing a heap with two stacks seems pretty good. That's something that certainly doesn't just jump to the front of my mind at all.
You'll do fine. You seem like a bright kid.
Re: How I was rejected at Microsoft
#17Re: How I was rejected at Microsoft
#18Re: How I was rejected at Microsoft
#19Blame the interviewers throw easy questions at you and think that it's all they get is blatantly wrong. Most Microsoft's devs are better than that!
Based on my experience, the fact that you did not get harder questions show that they thought you did not sail through the easy ones as they expected. And believe me, knowing the answer is one thing, explaining it clearly is another thing.
When I interviewed in Redmond last year, I got 5 interviews total. The first one is easy with all similar questions you got. The second was harder as the guy asked me a problem that starts off easy but when you add more data to it, it becomes more like an open problem. The third one is a OOP design question. The fourth one I met an engineer that joined MS from 1992 and he asked me only one algorithmic question that I have never seen before (Believe me, I read all those 'interviews' books and I know many ). It was very strange tree structure that I did not remember. I spent about 20 minutes stared at it and I got the first part after 35 minutes and then he asked me to explain how I finish the problem. He seemed to be OK with my answer. The last interviewer is a manager. He did not ask me anymore technical question but focus mostly on my preferences, experiences, previous jobs and some behavioral questions.
I think the interviews are on par with other top companies like Google ( but Google focus much more on scale ), Facebook and Amazon ( focus more on design and scale ).
In conclusion, rest assure that your interviewers are much smarter than you think. Hope you do better next time!
Re: How I was rejected at Microsoft
#20"Are you fucking serious? Probably HR persons do not know what a compiler is" This is actually common. You're right, the HR person wouldn't know what a compiler is, she is following a script with admissible answers to the problems and just listening for keywords that show you have the bare knowledge to pass the screening interview. From the tone of your comments about the interview, it sounds like you seemed shocked…