Marquee de Sells: Chris's insight outlet for category 'interview' via ATOM 1.0 csells on twitter

You've reached the internet home of Chris Sells, who has a long history as a contributing member of the Windows developer community. He enjoys long walks on the beach and various computer technologies.

David Ramel Asks About Interviewing at Microsoft

David Ramel from is writing an article that includes the Microsoft interviewing process and he send me some questions:

[David] How would you succinctly sum up the Microsoft interview process as compared to those of other tech companies?

[Chris] MS does some things similarly to other high-tech companies I've worked with, e.g. having each interviewer focus on an aspect or aspects, e.g. team skills, people skills, technical skills, etc., expecting a candidate to ask questions, communicating between interviewers to push more on one area or another, etc. The riddle questions are a uniqueness at Microsoft (at least they were when I last interviewed), but theyire pretty rare these days. Coding on the whiteboard also seems pretty unique to Microsoft (myself, I prefer the keyboard : ).

[David] How has the Microsoft interview process changed over time? (Microsoft seems to have shaken up the tech interview process some years ago with those brain-teasing puzzle� questions, but now seem to be much more technically-oriented and job-specific. Just wondering about your thoughts on this observation.)

[Chris] While I have had them, puzzle questions were rare even when I was interviewed 7 years ago. Since then, I haven't run into many people that use them. However, when they are used, an interviewer is often looking for how a candidate works through an issue as much as the solution that they come up with. In an ever changing world, being able to learn and adapt quickly is a huge part of how successfully you can be in the tech industry at all and at Microsoft specifically. I prefer technical design questions for these kinds of results, however, and it seems that most 'softies agree.

[David] What would you say was the biggest factor in your being offered a job at Microsoft?

[Chris] I had a reputation outside of MS before I interviewed, but that almost didn't matter. If I hadn't done well during the interview, I would not have been offered the job. When in doubt, a team generally prefers to turn away a good candidate rather than to risk taking on a bad one, so if there's anything wrong, team fit, technical ability, role fit, etc., a candidate won't get an offer.

[David] What's the single most important piece of advice you can offer to those preparing for a Microsoft job interview?

[Chris] You asked for just one, but I'm going to give you two anyway. : )

  1. If you need more information to answer a question, ask for it. Thatis how the real-world works and many questions are intentionally vague to simulate just this kind of interaction.
  2. Try to answer non-technical questions based on your personal experience, e.g. instead of saying "here's how I would deal with that situation,"� say "I had a similar situation in my past and hereis how I dealt with it."� This is a style of interviewing known as behavioral� and even if your interviewer doesn't phrase his questions in that way, e.g. "give me an example of how you dealt with a situation like blah,"� it's helpful and impressive if you can use your own history to pull out a positive result.

[David] Could you please share any other observations you have on the Microsoft interview process that may not be covered in your site or the Jobsblog?

[Chris] I run a little section of my web site dedicated to the MS interviewing process and the thing I will tell you is this: don't prepare. Be yourself. If you're not a fit for MS, no amount of preparation in the days before an interview will help and if you are a fit, that will come through in the interview. Also, make sure you ask questions. Working at Microsoft isn't just a job, it's a way of life, so make sure you're sure you want the team and the job for which you're interviewing.

[David] Does MS provide training for interviewers? If so, what do they stress most?

[Chris] I'm sure MS does provide training for interviewing, but Iive never been to it. At Intel, I learned the behavioral interviewing technique, which Iive used in every interview since, both as an interviewer and as a job candidate.

[David] Do you have standard questions, or do you tailor them to the situation? If the latter, is it usually tailored for team fit, to a specific open position, particular skills, etc.?

[Chris] I have once standard technique question and a few standard behavioral interview questions. The technical question is to ask them what their favorite technology is and/or what they consider themselves to be an expert� in and then drill in on their understanding. If they can answer my questions deeply, this shows passion about technology and the ability to learn something well, both of which are crucial for success at MS.

My behavioral interviewing questions are things like "Tell me about a time when youive been in conflict with a peer. How did you resolve it? What was the result? What did you learn?"� and "Tell me about a time when you had much too much work to do in the time you were given. How do you resolve that issue? What was the result? What did you learn?"� The core idea of behavioral interviewing is that past behavior indicates future behavior, so instead of asking people things like "How would you deal with such-and-such?�" you ask them "How did you dealt with such-and-such in the past?"� This forces them to find a matching scenario and you get to see if they way they dealt with the issue in real life matches what you want from a team mate in that job.

[David] How would you describe the kinds of coding questions you ask? A couple of real examples would be perfect!

[Chris] I don't often ask coding questions, but when I have, I let them use a keyboard. I hate coding on the board myself as it's not representative of how people actually code, so I don't find it to be a good indicator of what people will actually do. I guess I even use behavioral techniques for technical questions, now that I think about it. : )


Ed Helms on Microsoft Recruiting

This spoof on Microsoft's college recruiting practices was recorded long ago (back with the XBox was new), but it has recently surfaced again, so I thought I'd share. Enjoy.


Wasting the Prince of Darkness

From "Pete" (not his real name):

I walked into my first technical interview at Microsoft, and before I could say anything, the woman says, Youre in an 8x8 stone corridor. I blink and sit down.

Interviewer: The prince of darkness appears before you.

Me: You mean, like, the devil?

Interviewer: Any prince of darkness will do.

Me: Ok.

Interviewer: What do you do?

Me: <pause> Can I run?

Interviewer: Do you want to run?

Me: Hmm I guess not Do I have a weapon?

Interviewer: What kind of weapon do you want?

Me: Um something with range?

Interviewer: Like what?

Me: Uh a crossbow?

Interviewer: What kind of ammo do you have?

Me: <long pause> Ice arrows?

Interviewer: Why?

Me: <floundering> Because the prince of darkness is a creature made of fire???

Interviewer: Fine so what do you do next?

Me: I shoot him?

Interviewer: No what do you do?

Me: <blank stare>

Interviewer: You WASTE him! You *WASTE* the prince of darkness!!

Me: <completely freaked out and off my game> Holy crap what have I gotten myself into.

She then tells me that she asks that question for two reasons. 1) Because she wants to know if the candidate is a gamer (which is apparently really important please note: Im not a gamer) and 2) because she wants her question to show up on some website. I hate to accommodate her, but this is definitely the weirdest interview question Ive ever heard of.

Well, here you go, weird-prince-of-darkness-wasting-lady...



Tue, 9/6/05, 2:29 pm


Scott Hanselman's Great .NET Developer Questions

Scott Hanselman has posted a set of questions that he thinks "great" .NET developers should be able to answer in an interview. He even splits it up into various categories, including:

Am I the only one that skipped ahead to "Senior Developers/Architects" to see if I could cut Scott's mustard?


Jason Olson's Microsoft Interview Advice

Jason Olson recently interviewed for an SDE/T position (Software Development Engineer in Test) at Microsoft and although he didn't get it, he provides the following words of advice for folks about to interview for the first time:

You can read the full story on his web site.


Standing Out When Submitting Your Resume

After seeing all of those pictures in Wired of the wacky letters that people send, I love the idea of Michael Swanson opening the floodgates by sending his resume along with a life-size cardboard figure. What's next?


Some of the MS Interview Process Filmed (Finally!)

Channel9 did what I was unable to ever get done: filmed some of the interview process (part 1, part 2 and part 3). It's not an actual interview, but Gretchen Ledgard and Zoe Goldring, both Central Sourcing Consultants at HR for MS, lead you through what to expect at a Microsoft interview, providing a wealth of wonderful tips, e.g.

BTW, I have to say that I never got a ride on an HR shuttle. I guess they save that for the "good" hires... : )



Questions for Testers

A friend of mine sent along some questions he was asked for a SDE/T position at Microsoft (Software Design Engineer in Test):

  1. "How would you deal with changes being made a week or so before the ship date?
  2. "How would you deal with a bug that no one wants to fix? Both the SDE and his lead have said they won't fix it.
  3. "Write a function that counts the number of primes in the range [1-N]. Write the test cases for this function.
  4. "Given a MAKEFILE (yeah a makefile), design the data structure that a parser would create and then write code that iterates over that data structure executing commands if needed.
  5. "Write a function that inserts an integer into a linked list in ascending order. Write the test cases for this function.
  6. "Test the save dialog in Notepad. (This was the question I enjoyed the most).
  7. "Write the InStr function. Write the test cases for this function.
  8. "Write a function that will return the number of days in a month (no using System.DateTime).
  9. "You have 3 jars. Each jar has a label on it: white, black, or white&black. You have 3 sets of marbles: white, black, and white&black. One set is stored in one jar. The labels on the jars are guaranteed to be incorrect (i.e. white will not contain white). Which jar would you choose from to give you the best chances of identifying the which set of marbles in is in which jar.
  10. "Why do you want to work for Microsoft.
  11. "Write the test cases for a vending machine.

    "Those were the questions I was asked. I had a lot of discussions about how to handle situations. Such as a tester is focused on one part of an SDK. During triage it was determined that that portion of the SDK was not on the critical path, and the tester was needed elsewhere. But the tester continued to test that portion because it is his baby. How would you get him to stop testing that portion and work on what needs to be worked on?

    "Other situations came up like arranging tests into the different testing buckets (functional, stress, perf, etc.)."


What do job interviews really tell us?

For the New Yorker, Malcolm Gladwell discusses various indicators of how well interviews actually work for screening job candidates (in a phrase: not very well). The discussion of how we make our decision about someone in the first 2 seconds after seeing them and then use our future interactions with them to either reinforce our initial reaction or forgive as an aberration is particularly telling.


"Interviews are practically worthless for screening candidates."

Bram Cohen, the inventor of BitTorrent, discusses his thoughts on interviewing, include:

Fun. : )


HR Bloggers

I've heard for years that MS HR uses my site as part of their internal HR training, although I've never heard it from the HR folks themselves. Until now.

On Wednesday, Heather Hamilton, an MS recruiter, said that my "site is legendary, especially here in staffing."

On Monday, Zoe Goldring, also an MS recruiter, said "Net/Net Chriss site is great. Plus I respect the fact that he doesnt give the answers to the questions!"

And, to top it off, they're even bloggers, and they provide a whole host of interesting info for folks interested in interviewing at Microsoft. Certainly, I'd trust anything you read on their blogs far more than the stuff on this one, most of which was obtained far before I ever worked at MS.


Interviewing for MS Interns

Shawn Morrissey (my boss) posted some questions he asked at UPenn's Wharton School of Business:

He posted a couple of answers, but you'll have to read his post for them.


Interviewing at Lego

Sat 1/10/2004 10:12 am

Jamie, a contender for a Master Builder spot at Lego, describes a very different interview process than you're likely to get at Microsoft (except that 'softies hit you with sneaky stuff, too, sometimes : ).


Robert Scoble on Interviewing at Microsoft

Robert Scoble (the Scobleizer) sent along his answer to a common question: What is it like to interview at Microsoft?

About dress code while interviewing at Microsoft. Yeah, I wore a suit and tie. Not mandatory (no one wears them up here) but I feel it still shows respect for the company hiring you, and for the interviewing process. And, it makes it so I never wonder if I under dress. Microsoft employees might joke with you about being overdressed, though. That's cool. I'd rather that then have someone write me off cause I didn't dress well enough. But then, I was also up for a job that required me to be in front of people, so I'd expect to wear a suit and tie on the job occasionally.

The process for me was:

  1. An exec asked me "would you ever consider working here?"
  2. A one-hour phone interview with HR. They asked me questions to make sure my experience matched my resume, and also to make sure I wasn't gonna embarrass them in the longer interviews.
  3. I passed the HR interview, so they flew me up to Redmond.
  4. My interviews started at 8:30 a.m. First interview was with someone else from HR. She explained the process, and asked a few more questions to ensure I was gonna be worth sending onto the first group.
  5. She gave me a list of three candidates, which would take me through lunch. She was pretty clear that if the three liked me, I'd get another list of "after lunch" candidates.
Each interviewer would meet me at the lobby (Microsoft has a recruiter shuttle that'll fly you around). I'd usually try to get a question in, like "what role do you play here?" Just to get things going.

The kinds of questions you'll get will vary, but I got a lot of questions about past experience, and some more fun ones "how would you get Google to convert from Linux to Windows?" Other people have gotten questions like "how would you sell ice to eskimos?" or "how would you sell a pen to someone?"

If you're up for a programmer job, they'll ask you logic questions, and ask you to demonstrate that you can think in code on the whiteboard.

One guy asked me to explain the architecture of Radio UserLand on the whiteboard.

There's an excellent book written on the Microsoft interviewing process called "Moving Mount Fuji."

I also read Chris Sells' "Interviewing at Microsoft" site:

Some more advice: I came an hour early and took an early-moring walk around the campus. That helped me calm my mind down, and get into what it's like being there. Also, it let me think about "why do I want to work at Microsoft?" which was one of my first interview questions.

I brought my own water bottle. That saved awkward moments where interviewers would want to take you to the company refrigerators. It also makes it look like you aren't there to take advantage of Microsoft's largess. Try not to drink too much during the day. The temptation is to drink a Diet Coke on every interview. You can get a bit jittery by the end of the day.

I also treated everyone I met as an interview candidate. I have no idea if the recruiting shuttle drivers report back on their feedback or not, but why take the chance? Plus, the stories you hear are often good ones to tell later on.

They did interview me over lunch, by the way, and also took me to a Sonics' game . I'm sure that was to get a feel for how I'd be in social situations. Behave, and geek out! (we only watched about five minutes of the Sonics' game cause we were so busy talking tech).

I later found out that they usually have three to seven candidates fly up for each job and that flying up isn't any guarantee of a job. A few friends have gotten flown up and didn't pass muster.

My wife has interviewed here too and didn't get hired. I think it's solely on passion. Most of the people who work here are hard-core geeks and they like hiring other geeks. Anything you can say to demonstrate that you're a geek and that you love playing with technology is probably a good thing.

Later I found out that the flyup interview is mostly to see if the candidate can fit into both the job, and work with the team. They figure you're mostly qualified because you got that far. They're just trying to make sure you'll fit in at that point.

Don Box also gave me some advice: "we want you to think, so think." The way another friend of mine put it, is "look like you think about every answer. Take a few seconds to think about it."

My answer to the Google question? "Acquire them." Hey, it worked for Hotmail. (Seriously, then I followed that smartass answer up with a more serious one ) . Luckily I had spent a few hours with some of the kids who started Hotmail, so I knew what the pain points were in getting them to move their system from FreeBSD to Windows.

When did I know I had the job? At about 6 p.m., the guy who invited me up, told me I had gotten a job. Turned out I wasn't appropriate for the job I was interviewing for (which he knew) and then he made a new job. It took a couple of weeks to get all the T-s crossed from that point. Other people don't learn whether or not the got the job for a week or two afterward. It's OK to ask at the end.

If you get walked to the door at lunch, though, you know you blew it somewhere. (Not many get walked to the door, from what the recruiting shuttle drivers tell me).

One last piece of advice: keep your energy up all day long. It's tough. Hard to think straight at 4 p.m. after answering questions all day long. But, a lot of the decisions are made on "does this guy get excited by technology?"

Good luck in your interviews!



17 older posts       No newer posts