If you are wondering that where the hell was AzamSharp AKA GridViewGuy then well, I have a good reason for it. I went to Seattle for an Interview with Microsoft. My interview was scheduled at 8:30 AM on Tuesday (03-21-2006) and due to flight delay I reached Redmond, Seattle at 2:00 AM. So, I guess you get the idea what shape I was in. Anyway, no one wants to hear my condition during the interview but you want to know about the Interview. So, here are the details.

Interview with Microsoft

If you are wondering that where the hell was AzamSharp AKA GridViewGuy then well, I have a good reason for it. I went to Seattle for an Interview with Microsoft. My interview was scheduled at 8:30 AM on Tuesday (03-21-2006) and due to flight delay I reached Redmond, Seattle at 2:00 AM. So, I guess you get the idea what shape I was in. Anyway, no one wants to hear my condition during the interview but you want to know about the Interview. So, here are the details.

I was being intervied by two teams. One was XML Enterprise Framework Team and one was ASP NET Testing Team (SDET). My first interview was with my recruiter. I went to building 19 at about 8:00 AM in the morning and waited for my recruiter. When she came I was playing XBOX 360, she caught me right when I was trying to get the bad guys in the game  . Anyway, we had a chat forabout 45 minutes. Nothing technical just asking about my projects and stuff. After that interview I went to building 42 and waited for the first technical interview.

The first interview was with the XML Enterprise Team. He asked few questions about myself and then jumped to the coding questions. All coding questions have to be done on the white board. The question was about converting a string into integer without using any libraries. Anyway, I verbalize my thoughts and presented the test cases and asked lots of questions. I solved some part of the problem but there were performance issues with my solution. Remember that you might be able to solve the problem but you need to find the best solution of the problem.

My next interview was also with the XML Enterprise Team. So, the guy invited me to his room and ask me questions that how you start building an application. So, I again started talking and asking questions and putting my thoughts on the white board. Then he told me to design the database, so I drew many tables.

After that I made classes and relationships between the classes.

My next interview was with the ASP.NET Team. And I have to mention it right here that ASP.NET team people are very nice. I met with three of them and they all are very cool and very very very nice people. Anyway, I went to the small room and was asked the coding question. So, I coded it on the white board. I was missing one call in my code which my interviewer pointed out. Later we sat down and he drew some stuff on the paper and asked me to write the test cases for this. I asked lots of questions and came up with good tests.

After that we went for lunch. During lunch he did not asked me any technical questions but talked about himself and what he does. Since, he was also in the testing team so, I asked many questions relating to his job and how the testing procedure starts. If you ask the interviewer about his job he will get very excited and tell you very cool things. I listened to every word he said very carefully and again asked lots of questions.

After lunch I was interviewed with a different person (This guy was also extremely nice). He asked me a little puzzle question which I answered correctly. The question used some common sense and linear equations or factorization depending on which path you choose. The last question I was asked was about link lists. I made a link list in C# and did some operations. We talked for a while and then the interview was over.

I was dead tired after the interview since, I only had 4 hours of sleep. I went to the hotel and crash on bed .

Here are few pointers about the interview:

1) Be yourself, be confident.

2) Ask lots of questions

3) Don't directly jump into coding. First think about the questions. Clear up the questions and then make the algo and later code it.

4) You can code in any language (At least I was given this choice).

5) Coding syntax does not matter. It's the logic that matter.

6) When you finish making the algo or code step back and think if you can improve it.

7) If you want to practice coding questions try www.topcoder.com.

8) Have a good night sleep (Not like me who only slept 4 hours).

9) Eat a good breakfast. If you are staying at HomeStead Redmond which is very close to Microsoft (Walking Distance) then please note that they don't serve breakfast. Yeah, that was a shocker for me also when I woke up at 6:30 AM and called them what do they have for breakfast and they told me they don't serve breakfast. Good thing I bought a beef burger from the airport .

10) Keep a water bottle full all the time. You will be talking, talking and talking and you will need lot's of water.

11) Keep something sweet like candy or chocolate bar with you so you can eat it between the interviews to keep the energy up.

 

So, that is all I can tell you about the interview. I hope you will find this information useful. I have not yet received the result of the interview. Actually right now I am still in Seattle and sitting on the floor of the Seattle Airport waiting for my flight.

Dude, where's my plane!

Updated: Just reached Houston.

If you are one of the thousands that visit GridViewGuy for your .NET articles and resources, you might be interested in making a donation. Extra cash helps pay for the hosting services and speed things up around here, and makes this website possible.

Make a Donation

Once, again thank you very much and remember its because of you FINE people that this website is up and running.

 

Export Button is a custom control that let's you export your DataGrid or TextBox data to several different formats. The control is extremely easy to use and also exposes design time features. In this article I will discuss some of the features of the Export Button and how it benefits the developer.

BUY IT NOW