The Inside Scoop on Interviewing at Microsoft
(or at least, my personal take on it!)
Over the last couple of months, I've been interviewing candidates for a couple of different roles at Microsoft at a rate of almost one a week. Interviewing is definitely something of a skill, both for the interviewee and for the interviewer. A good interviewer doesn't ask random questions, even if it seems that way - they're trying to get a candidate to reveal enough about their character, skills, temperament and awareness that they can determine whether they'd be a good hire for the team.
I enjoy the mental stimulus of being on either side of the desk for an interview: as an interviewer, the challenge of trying to get through the mask that people sometimes put up to find out where someone's real talents and weaknesses; as an interviewee, the process of finding out more about yourself and the areas where you personally need to develop. Either way, it's a process of continual learning.
One thing that surprises me is how many potential new hires fall into the same "traps". I don't try to catch people out or set trick questions, but I see people who don't do themselves justice in the way they present themselves. Here are a few ways I see people shooting themselves in the foot, based not on any individual candidate but a broad aggregation of the perhaps 15-20 interviews that I've conducted in the last year:
- Stock Microsoft interview questions often start with the phrase "Tell me about a time when..." The goal of questions like these is usually to find out more about your actual performance in a real-world scenario, rather than your best-case performance in a hypothetical situation. It's interesting though how often I get answers that focus entirely on the project or organization someone has worked on, rather than their individual contribution. Of course, we're looking for people who work well in a team setting, but telling me about a project that you worked on that was particularly successful doesn't give me any indication of whether you were the star performer that turned it around or whether you were a knuckle-dragger that just happened to be associated with the project. Tell me what things you did, what impact they had, what you learnt from the experience, rather than making me want to hire someone else from your project team!
- Show passion for both what you've done in the past and what you're interviewing for. I want to see evidence that you care about the job enough that it's not just another notch on your resume. Even if you're historically a star performer that we'd be lucky to hire, I want to be convinced by you personally, not just by your performance on paper. Do some reading around the area; if you know the interviewer's names, search for them on MSN Search (or Google if you really must!) and find out what their interests are, what they've written about, and what they have a passion for - not to flatter them, but to demonstrate your commitment to the role.
- If I ask you where you're weak, it's not a trick question. It's amazing how few people are prepared to own up to any flaws at all. Sometimes people do this fake thing where they highlight a strength as a weakness ("people say to me that I care too much!"). I don't believe that you're completely perfect - really, I don't! What I want to see is that you're aware of your limitations, you're not so arrogant to presume that you can't learn anything or accept feedback, and that you have the ability to reflect on your own character. Give me something - even if it's just that you're not a morning person!
- Lastly, demonstrate vision - share your hopes, your dreams, your ambitions. Tell me where you see this job as a stepping stone to - where you'd like to be in five years time. I want to see that you have a sense of the strategic - that you understand the industry, that you have knowledge that stretches beyond the specific requirements of the role you're interviewing for.
In general terms, it's in both the interviewer and the interviewee's interest to determine whether the person is a "good hire" or a "bad hire". No matter how much you want a job coming into an interview, pretending to be someone you're not (more technical than you really are, more interested in a certain type of work than you really are) to land a position doesn't lead to satisfaction in the long run, when you wind up getting bad performance reviews because your skills just don't mesh with the requirements of a role. On the other hand, if you can find a job that really matches your interests, skills and goals, you'll have great fun doing it and naturally excelling in it.
Comments
- Anonymous
March 23, 2006
What's a common clothing at a MS interview? A black tie or a t-shirt? :) - Anonymous
March 23, 2006
I found this post interesting and useful. I've been on a lot of interviews over the years. When I was... - Anonymous
March 24, 2006
Kostik, probably somewhere in-between. It's a pretty laid-back, casual atmosphere here - I have to take the dust jacket off my suit before wearing it - but equally some interviewers might feel a Grateful Dead T-Shirt and ripped jeans is just a little too laid-back! Obviously it depends a little on the kind of role you're interviewing for... - Anonymous
March 27, 2006
The comment has been removed - Anonymous
March 30, 2006
Here's another one you could ask. Have you actually shipped a product on time? That seems very important to ask. If the answer is yes, consider hiring for Vista, MS Office or even Virtual Server. - Anonymous
March 30, 2006
[Tim] Tell me what things you did, what impact they had, what you learnt from the experience, rather than making me want to hire someone else from your project team!
[Tom Archer] I would add that the interviewer should take care to note that many of us were not raised in the same culture and have been brought up to believe that you should play down your individual contributions and talk about the team. When I first came to the states and started interviewing, I had to be reminded a couple of times that the company wanted to know about me and my contributions. For example, I frequently stated "we" even in cases where I was the only one on a project I was describing because that's how I was reared. - Anonymous
April 01, 2006
Tom, that's a good point - both interviewer and interviewee would do well to take account of each other's cultural references. However, it behoves the interviewee in particular to be aware of the mores of the interviewer, since it's the interviewee that's selling him/herself rather than the other way around. - Anonymous
April 03, 2006
Lone Deserter, I'm going to guess that very few developers have been part of a project the size of Windows Vista, and that even fewer have successfully shipped it on time. Can you name another project of its scale and breadth of distribution? - Anonymous
April 04, 2006
I intereviewed with Microsoft last year. It turned out that I was not the best fit for the role. I was disappointed and at the same time I was very impressed with Microsoft and how they handled it. Most companies just show candidates the door if you are not a fit for the role--the end. However, Microsoft stated that they were still interested in me for other roles and I was a good fit for the culture. They are taking a longer term view. There is still some hope. I learned a lot during the interview process about the company and people. I didn't have the name of the interviewers in advance, however I researched the group as much as I could. It was a very exciting day. I agree you don't want to be in a role where you are not positioned to be succesful. That only hurts the company, hiring manager, and you. - Anonymous
April 10, 2006
Well, ugh - of course you don't - who would? It's a horrible thought...! But perhaps you think you'd... - Anonymous
April 13, 2006
Hi Tim Sneath,
This is my first step towards the preparation for Microsoft which is being my dream company since when i new about this.It is more than Awesome that peoples like you from Microsoft provides such kind of information which is very very helpful towards the Interview.
Thank You Very Much,
Pramod - Anonymous
April 15, 2006
>If I ask you where you're weak, it's not a trick question.
No it's your job as an interviewer to find out the strength and weaknesses via your questions.
Just my 2 cents. :)
regareds Allan - Anonymous
April 20, 2006
Wrong Wrong and Wrong!
Tim,
If you have set your mind on what should the answers to your questions be and are expecting a standard type of answer from a novice to an experienced engineer, I am Sorry but you have utterly failed to interview, you'll be disappointed that no one would fit to the position you are hiring (majority of them unless they are just like you). Weren't you told when you were interviewing after the college to describe your -ve attributes as a +ve feature, don't tell me that you did not do that while you interviewed. If you read any of those 101 Answers to tough interview questions, all of them suggest to talk about a +ve attribute when asked about a -ve weekness. What about that???
Like someone on these posts said all are raised with different cultural background and it has a great impact on the way one presents themselves during the interview. If your interview process cannot TUNE to understand what strengths an individual has you have failed not the candidate. Can you explain why Microsoft was asking Puzzele and trick questions for a long time. None of the puzzle questions would extract what the candidate can do and his strengths are they are just making the interviewer look good and superior. Take a written test on Math and Problem solving if you want to test someone’s real caliber.
No interview I repeat No interview on this planet can test an individual in a single day on what his strengths and skills are. Most of Microsoft interviewers fail to make the candidate at ease, and all he/she utters is not what they are all about. - Anonymous
April 28, 2006
Hi Tim. I'm a tech writer of 6 years, and I've been a star performer at the companies I've worked for (web hosting and web content management). However, I recently bombed an interview at Microsoft for a position I was very interested in and knowledgeable on. I think it was because of the way I answered their questions (not clear enough, not detailed enough). But this is why I chose tech writing over tech training, sales, support, consulting, etc. -- my writing is more articulate than my voice. Any advice for someone like me? - Anonymous
April 30, 2006
Great entry, just preparing myself for an interview at corp so it's going to come in handy! - Anonymous
May 02, 2006
I would just add that opposite to the "I/We" thing - I interviewed for a role recently where it was flagged that I talked too much about what I had done, and not my team.
So sorry, but you can't win with MS interviews it seems as in the past I had the opposite (to much we, not enough I)! - Anonymous
May 04, 2006
Personally, I think you all should just listen to Tim. Afterall - he's already IN Microsoft. We can all moan and complain about interviews and wether or not they're of any real use but the fact is - interviews are how we get our jobs. Its great that Tim should even offer to write down his advice. So Ramesh and co, stop wining and moaning - learn how to perform at an interview. - Anonymous
May 13, 2006
I guess Microsoft is so much flodded with Resumes that everyone's thinking is only sourrounding on "We are selling outsleves...", "We need a Job...", but no one seem to account that the employer is needing of a human-resource to accomplish their goals, reach their targets, and make big money. So the interview becomes equally important to the employer or even more imp as they spend money in the hiring process. - Anonymous
May 14, 2006
Hi Tim,
Thanks for your blog entry. I have an interview at MS Redmond next week. I found your advice very useful and wrote to my recruiter to send me details about the groups interviewing me, so that I could read up a bit about them. Its quite exciting being interviewed at MS coz it'll put a lot of things at rest for me. The most important one being whether I really fit in the company that I have dreamt of working for all my life. If I don't then I could just happily move on atleast knowing that I do not belong there. Or if I find out otherwise and happen to get a job offer, well... then obviously I would be on top of the world.
cheers
AG - Anonymous
May 15, 2006
There's been some interesting comments on my entry: "The Inside Scoop on Interviewing at Microsoft",... - Anonymous
May 24, 2006
Hello-
I agree with Ramesh's comments. It appears to me that
Tim is helping and wanting to hear what she/he wants to
hear from a job candidate by writing a blog about the style of interview at Microsoft. It's very common these days to tell a strength attribute as a week attribute based on the context and perception.
It appears to me that Tim may have to look back thin about how she/he should be conducting interviews in future? - Anonymous
May 26, 2006
Whatever you do, try and avoid Live Meeting interviews over the phone. A lot of miscommunication can happen here. I think the interviewer needs to see the person face to face because facial and body expressions can be an important factor in the interviewing process as well. You might enthusticastic about a position, but if your voice does not give that impression, then you might get passed up. There needs to be more in the interview than a voice and an invisible cursor revealing text on a white background. - Anonymous
June 20, 2006
PingBack from http://mikefarinha.wordpress.com/2006/03/30/interviewing-tips/ - Anonymous
December 04, 2007
Microsoft Technical Evangelist, Tim Sneath, gives us the Inside Scoop on Interviewing at Microsoft. Great