I was originally contacted by an internal recruiter at Avanade. This conversation was to go over technical abilities and career goals - essentially a 20 minute interview to determine whether or not it was worth the time to continue in the process. She was a very positive and up beat individual, whom it was nice to speak with, and made me feel good about the process. As a company, definitely the type of person that you would want to have doing initial contact with candidates. At the end of the conversation, she indicated that she would be recommending me to continue on in the process and that from that point forward I would be dealing with two contacts: one contact to relay feedback and advise of next steps in the process; and the other contact would be the one that coordinates the interview phases between myself and the Avanade employees. I was contacted a couple hours later by both contacts to introduce themselves and to schedule the technical phone interview. I advised the contacts that I was currently on vacation and could move as fast as they could move - which they did. The first interview was a technical phone interview that was scheduled to last 30 minutes. I was on the phone for about 45 minutes. The individual I spoke with was very nice and knowledgeable. He spent about five minutes describing his role (developer) and what working with Avanade is like. He was very understanding and asked that I not be insulted if the technical questions were too easy or upset if I didn't know one or if they were too hard. In reality, if you have more than two or three years experience these should be straight forward questions. There were also questions on architecture and SDLC methodologies. I spent probably about 10 minutes discussing the pros and cons of agile methodologies versus methodologies like waterfall, etc. Technical questions consisted of: tell me about inner and outer joins in SQL; when creating an object and you want to iterate over it using a foreach loop, which interface would you implement; difference between string and stringbuilder... It was nice to speak with someone that feels the same way I do regarding technology. At the end of the interview, he advised that he would provide his feedback and the representative would be in touch. About two hours later I received a phone call from the representative stating that the feedback was very positive and I was being recommended onto the second technical interview, which would be a phone interview supplemented with using Microsoft Live Meeting. The interview was scheduled for the next day. The second technical interview was hosted by a development manager. After logging into the Live Meeting and dialing in, the interviewer advised that he would not be using Live Meeting to conduct the interview. He indicated that it was unnecessary to ask further technical questions because of the level of position I was interviewing for. He wanted to discuss my leadership abilities in detail. Some questions that were asked: what type of tools do you use during the life cycle of a project; how would you manage a junior developer; speak about a time on a project that I lead when having to deal with difficult situations and different levels of management and what was the outcome. This interview was supposed to last approximately 45 to an hour and it lasted about 30 minutes. At the end of the interview, he indicated that he would recommend me onto the final phase, the in-person interview. Again, about two hours later I received a phone call from the representative stating the feedback was very positive and I was being recommended onto the final phase, the in-person, confirming interview with my hiring manager. This interview was schedule the middle of the following week due to the hiring manager traveling. This interview would last approximately one hour. At the beginning of this interview the hiring manager advised that it would be a little everything: technical skill, soft skills (communication), and discussing points on my resume. At this point I was also made more aware of the Avanade ATS organization, what his role was, and what my role would be. This lasted for about 10 minutes and then it was right into my resume. It started giving an overview of what projects I listed for my current employer, technologies used, and my role. After discussing this, I was then asked to pick one of the projects and draw the high-level architecture of the project on the dry erase board in the office. Moving forward, I was then asked to explain how I would estimate this project. The questions that followed made me support my theory and decisions based on the project - as if I were defending it to the client or upper management. At the end of this interview he indicated that he was going to follow up with the previous people I spoke with and get their feedback and then be in contact with the recruiting representatives on next steps.