Interview process is well organized in the MS. There are some standard procedures, guidelines for interviewers and mandatory training before you allowed to be an interviewer. Loop takes one day. Starts and ends with recruiter. At morning recruiter instructs you about process. 5 interviews one hour each. One of them is a lunch interview. Interviewers exchange information about you in between and fill up report form available for limited amount of people. First question of the form: Hire/No Hire. Several paragraph of explanation your decision after it. If candidate get first tree "No Hire" he gos home after the lunch. After first 5 interviews there is one more -- bonus play. Usually a manager of two-tree levels up. Answer you get from recruiter. Typically in a week. Content of interview depends on the position and on the team. Stupid questions like "Why road hatches are round?" are discouraged now. Hiring of right people is the most vital task for any high tech company. The goal of interview is anything else but demonstrating how smart and funny the interviewer is. Expectation is that you would grow couple "levels" in the next 5 years so questions where you want to be your career are impotent. If you don't have potential to grow you don't fit for the position. There is no magic answer here. Its ok to not have a plan especially if you are a collage hire. You can instead ask an interviewer about career opportunities in the MS. Asking right questions about a group, company, development/shipping process is as impotent as answering questions. Show an interest in getting position and respect to yourself and to the company. In some way you are "selling" yourself. Be prepared to discuss your previous work experience; what you consider was success and challenge and how you deal with this challenge. Usually on each interview you have one problem. The good problem is not well defined. You need to work with the interviewer on "formalizing" the task. It would be a mistake to make an assumption and jump to white board for codding it without postulating your assumptions at least. In most tasks you need to find and code some algorithm. Usually it is easy to find n*n algorithm or one that requires additional memory (or stack) allocation. If this is the case it may be helpful to show your knowledge. If you stick you would be offered a hint. Hint is usually not a full answer so keep working. In codding you don't need to write a "production" code but need to take in account all conner cases and possibly inva