So here’s the route to work:

bikeroute

So I made it, the only big surprise is how I was exhausted climbing the hill west of 405, and a strong southerly wind, which should both help me on the way back

I was reading some blogs and stumbled upon one that mentioned that 872 layoffs were coming in March. Intrigued by such an exact figure, I dug deeper.

There’s apparently a WARN act, which stands for Worker Adjustment and Retraining Notification Act, which obliges big companies to notify states, labor unions and cities of a big layoff coming. Turns out that Microsoft did file one of these which can be seen on the state’s web site.

The useful data from there is that there is to be 872 layoffs starting on March 23. So with January’s 1400 that would bring the total to 2272, with 2728 more to go. There are many other Seattle-area companies planning layoffs. Times are really bad…

So, here’s the three-part series:

Part 1 – The Interview With the Recruiter
Your first steps at Microsoft!

http://channel9.msdn.com/ShowPost.aspx?PostID=18472

Part 2 – The Shuttle Ride
Update: Now they’ve gone green and drive Priuses…

http://channel9.msdn.com/ShowPost.aspx?PostID=18718

Part 3 – The Famous Whiteboard Question
That’s what got us famous… :p

http://channel9.msdn.com/ShowPost.aspx?PostID=19171

I am really excited to have found such a great job right after finishing school like that. It’s totally amazing. In the meantime, I’m actually taking it easy, getting some needed R&R after finishing school.

Well, this pretty much sums it up. Over the next months I should be planning my relocation to the Seattle area, so that should generate some interesting blog stories.

Not too long after my recruiting coordinator calls me to her office. She summarized how the day is going to work out for me, told me the teams I would be interviewing with that day, and with who my first interview will be with. She gave me an occasion to ask any questions that I may have and then asked me some questions, such as the famous “Why Microsoft?”. Then, she took me outside to the recruit shuttle and off I was to building 44.

After a quick shuttle ride, I enter the building, register with the receptionist, then sit down and wait. They have washrooms and water in the lobbies, though sometimes a little hidden, so you may have to ask. After awhile, my first interviewer came to pick me up to his office. We talked for awhile, then he gave me two simple programming questions, and then talked some more about me, the position and Microsoft. The second interview was lunch. The interviewer took me to lunch at the cafeteria, where we talked more about my projects, my education, etc.

The third interview was the most interesting one in my opinion. It began with questions about teamwork. The main question was how would I manage a situation where there’s a conflict over the way something should be done. Then, I was asked a whole bunch of questions on data structures (the interviewer used to be a data structures professor). I knew these fairly well Then the last question was a hypothetical three-dimensional database storage system (imagine a three-dimensional excel spreadsheet). What data structure would I use, how would things work, etc? So I throughly discussed pointer-based, array based solutions, thinking out loud, raising issues, then discussing how I would approach these.

At this point, I was really happy. I knew I did well, and I would proceed to the next interviewer. I waited long enough for that one, which was a step harder than the rest. I got two pointer-related/string questions, which I solved relatively well. I started getting a little bit worried that I might not make this one, since my interviewer was expecting me to zip through these faster than I did, but, I did get the last interview.

The last interview was where I was put on the spot to enumerate my areas of interest, something quite difficult for a recent graduate, since I have not had lots of time to deeply dive into something for several years. Then, I was asked a logic riddle: “M people are standing in line. At each pass, you eliminate every Nth person. Who will be the last one standing”. At first, I thought this was a simple math formula, but it became evident that I needed to work out an algorithm, so I sketched schemas and pseudocode on the board to visualize the problem, and described an algorithm, of course, with some steering of the interviewer.

Once that was over, the day was over. I chatted with the interviewer while waiting for the shuttle, then returned to the recruitment building, and then back to the hotel.

Some thoughts…

The interview experience itself at Microsoft is something quite valuable valuable. At this point, I was happy I made it through the day, which meant to me that whether I would be hired or not, I was at least worth their time, and that gave me confidence, that I would not only be getting a job, but a good job, somewhere.

To future interviewees, I’d tell them to feel confident. The fact that Microsoft has invited you for an interview means that they saw something in you they liked.

In this multi-part series, I will detail my interview process at Microsoft, following which, I got two offers from them, one was with the Operations and Services Management group and the other with Windows Terminal Services group. I have not made my choice yet at the time of this writing (flying back to Montreal at 10000 meters in the air), but I can assure you this is the most difficult part of the interview.

Also, I don’t intend to make this post a repository of Microsoft interview questions because all you have to do is google up a few keywords (there are a handful of sites listing these out – yeah, take a look at them). Also, merely knowing many interview questions won’t make you ace the interview, it will just make you look stupid when the interviewer will call you on a random problem he just thought of.

The reason for blogging it in installments is not to crave attention (personally I don’t quite like the kind of attention Digg provides). Rather, this story may get long, and I don’t want writing it to fall on the back burner. So, without further ado, here’s part one.

I guess by the time I finish writing this I will be back in Montreal. I just finished watching what I had of Heroes, and I’ve only got like 15 minutes of battery left.

I have submitted my CV to Microsoft several times over the last two years, once last year when they came over to CUSEC 2006, during last fall’s career fair at Concordia, and during Microsoft’s “meet the company” event hosted at Concordia last month. I had to skip geology class for that, but I really really don’t regret it.

Following the last event, I was called in the same night for an on-campus interview with a Microsoft employee the following morning. A couple of general questions, along with a whiteboard program. I didn’t think much of it: I had plenty of work to do around that time, it was in the morning, and I was totally unprepared.

About a week later, just before I finish school, I get invited to the Microsoft headquarters in Redmond for a day of interviews in May. Since I have some friends there, I decided to make it a 1-week vacation (Microsoft pays for only 3 nights at the hotel)

So, I arrived in Seattle friday, that gave me a weekend before my interview to spend with my friends, so we went around on Saturday, then Kayaking/Picnic on Sunday. Monday was reserved for last-minute review (totally useless actually), moving into the hotel, and getting a good night’s sleep before the interview.

The interview morning, I go down to get breakfast and ask the front desk for a cab to Microsoft. I was actually quite surprised not to spot other candidates. The funny thing is that everybody around there knows that you are there for an MS interview, so they keep on asking you about it and try to put you at ease. Really nice people!

I promise, part 2 will detail the interview process! I should finish writing it over the next few days.