Microsoft interview + internship Summary

For a week in checkout, I always feel that I should write a summary to help me find a job in the future.

Starting from the internship, I had a total of 15 questions at Microsoft.

I reported SDE for the first time. I was lucky to pass the Microsoft School's written examination, but none of my master students who passed the test with me. To sum up, do not pursue perfection too much when doing wrong questions that require points deduction. If not, leave it empty and choose the answer that you think is the most possible.

According to the scheduled time to come to Microsoft for an interview, HR said that the first two sides of the interview, if the performance is good, there are three sides in the day. Then I stopped on the second side. At that time, the interview questions were written in the blog.

In conclusion, you must prepare for the interview.AlgorithmQuestions, because I found that there are several questions in the interview. After being hit by an interview with Microsoft SDE, I spent a lot of time thinking about algorithm issues. The more I thought about why I didn't see this book early.

Fortunately, although the SDE interview fails, Microsoft recommended me to the CSS department and the database technical support team. Of course, I do not know before entering the team.

The interview with Microsoft CSS was successful. There were two technical aspects, one manager and three sides in total. The only imperfect thing is that your English is too bad and you have not prepared self-introduction. Therefore, both interviewers say that my English needs to be improved. Therefore, when preparing to interview foreign companies, we should make appropriate preparations for self-introduction.

When I checkin in June 20, I realized that I entered the database technical support team. At that time, I was very happy because I had always liked database technologies. Then I found that my mentor was the first interviewer at the time. It was nice.

Then I started my internship at Microsoft. I got up at 08:10 every day and rode my bicycle to work in the company. I am very happy with my internship at Microsoft. I feel that I am mainly Training interns and don't need to do too many projects. There is a checkpoint every week. The topic of the checkpoint is provided by the mentor. The intern will do the presentation on the checkpoint. The main content is what you did in the past week. I made a total of seven checkpoints during my internship, and I felt a lot of GAINS. I can send my intern summary, mainly about my internship experience.

It is worth mentioning that many blogs have been written during the internship, which are the knowledge and problems encountered during the internship. I'll list a single topic: intern @ Ms http://www.cnblogs.com/xwdreamer/category/391043.html

During the internship, I often dive into the SQL edition to answer some questions and get the best promise:

Http://q.cnblogs.com/q/39999/

Http://q.cnblogs.com/q/39801/

Http://q.cnblogs.com/q/39424/

Http://q.cnblogs.com/q/35617/

After two months of internship, intern started to become an interview. The first interview was oral English test. At the beginning, I paid great attention to it. Later I heard chunge say that there was no link in last year's English interview, so I didn't know much about English. I spent all my time on checkpoint. Then, my English interview failed. At that time, when I got the message, it was a great deal. It was so sad. Didn't you say that English is not good? To sum up, just listen to other people's gossip. No matter what the interview is, it is necessary to prepare, especially the English interview. If you have prepared it in advance, it will be advantageous. Fortunately, mentor helped me apply for the re-interview opportunity. However, even so, it is too important to give others the impression of poor English.

During the second English interview, I learned the first lesson and prepared it. I backed up all my self-written intern summary. The second interview passed smoothly, but the score was not high after the mentor said.

The next step is three technical aspects. The first step is to talk about how you think about technical support and why you want to be a technical support engineer. These questions are easy to answer, because I treat myself as a technical support engineer every day, and sometimes there will be other team intern to ask me SQL Server questions, some of the previously encountered and summarized content on the blog, I just sent a link to them, and there are some issues that need to be solved step by step. Interns cannot do case studies, so I treat the SQL problems encountered by internal interns as case studies. The only technical question is that the interviewer gave me a bunch of information and asked me to explain it in general. This technology was not learned during internship, and it was about the knowledge of log shipping. Because the checkpoint has worked hard on database logs, it is easy to understand the log shipping and the answer is completed successfully.

The next two interviews were both half-Technical and half-Technical. After two months, the interviewer knew me very well. I think that I am the best technical intern, but English is relatively weak, because the intern in the team, only I did not pass the oral English test.

Finally, let's talk about life, ideals, technology, and English.

If you receive a message one week later, you do not have an offer. However, because performance commitment says it recommends recommendations to other departments, I have another interview with my team.

Three technical aspects, one team manager and the last group manager interview were welcomed this time. At last, I hung on the group manager interview. The conclusion is: if you want to go to this team for an interview, you should be familiar with what their team is doing. I did, but I really don't understand what the team is doing. Office365 is a cloud computing team. I searched some documents on Google but did not understand it. Then, during the technical interview, I asked my interviewer what our team was doing and what office365 was. He also said it was hard to clarify, because office365 has little to do with traditional Microsoft Office. There should be exchange, Sharepoint, and office in office365, but the exchange and SharePoint here are different from the traditional ones. They are all on the cloud. When using troubleshooting, sometimes our Technical Support Engineers cannot even see the error log and cannot build a simulated environment. This is not like SQL Server. We only need the customer to send the database to us so that we can test it in a local simulated environment. So many times troubleshooting is used to guess what the customer has done and what is wrong.

The second point is to be concise and concise when answering the interviewer's questions. Do not talk about balabala nonsense. Sometimes, in order to express ourselves, we always talk about a bunch of theme topics that have nothing to do with the interviewer's questions. This will make the interviewer feel that there is a problem with your communication. Remember, you must be concise and concise. When the interviewer is interested in in-depth understanding, let's talk about it.

The above two points are summarized by HR. I am really grateful to Microsoft. He will give me feedback during every interview. If he fails, he will tell me the interviewer's comment. Let me know where I am missing. Unlike some companies, the message "wait for a notification within two weeks" is sent.

========================================================== ==========

The following is an email sent from checkout to the entire team. Because of the privacy relationship, the name mentioned here is replaced by the English name.

Hi everyone:

Like Jack and CaO wrote before, I am always grateful for my internship in SQL team for a few months. Thank you for your help and support. I have learned a lot here and have spent a full and passionate summer vacation.

Thanks to Linda, Hz, and JY for asking me to go to the SQL team family for an internship and help me with technical issues and correct my mistakes.

Thank you for your help. When I first arrived, I sat opposite my brother. I asked my brother if I didn't understand it. I was always enthusiastic about helping me. Later, I asked gangge technical questions. gangge always said, "Can you reproduce your questions ?" Then, Brother gang got into my seat and helped me find the wrong one. At that time, I thought it was a waste of time for my brother. Since then, no matter which of my colleagues in the team have technical questions, I have habitually recorded "what I did on this issue" and "what I want to ask next" in my notebook ", "What is my ideal result ". Later, I found that, after doing so, the effect of asking questions is significantly improved, and the efficiency of solving problems is also greatly improved.

Thanks to yt and Za for their guidance. Za strongly recommended me to read HW's book. He said that new hire should read this book. Later, I carefully read this book, which benefited a lot. Some of the chapters have been read twice and three times, some of which have been recorded in my blog. I hope HW will not hold my copyright accountable, I have listed references. Yt also helped me solve a lot of technical problems, whether it is importing a database of a lower version to a higher version or disk Io performance. Unfortunately, I have no chance to ask yt questions about fitness. Recently I am a little fat.

Thanks to Simon for bringing me back to Jiaotong University from xinzhuang. I talked a lot with Simon in the car that day, which gave me a deeper understanding of our team's work and a clearer future study direction. Later, I learned about keepalive when I was doing checkpoint. I found a blog by Simon on the Internet. I thought Simon had to pay more attention to it. Later, when talking with Hz, we realized that someone copied the official blog of our team. It is shameful not to mention the source of plagiarism. At that time, Hz also said that it was necessary to strengthen the team blog's knowledge copyright protection work.

Thanks to HR and Marlon for their help. Every time I prepare a checkpoint, I like to talk with them. They can always help me find out the starting point and key points of the problem. Sometimes we even make checkpoints together, for example, how to view the definition of the stored procedure in resource dB. At that time, I only knew the most stupid method and told HR. After a while, HR found a better way, but I would not be in the company. As soon as HR saw it, I told me this question and thanked HR for sharing its knowledge. Marlon also helped me solve a lot of problems. He always pointed out which part of each checkpoint is the most critical, which part should be the most effort to prepare, and what content is included.

Thanks to bob for helping me solve the problem. Later I learned that Bob was a DBA and asked Bob about oracle. I still remember that Bob explained 1433 and 1434 on a new hire checkpoint, and named the instance and default instance. Later, when I made my own checkpoint, this knowledge point helped me sort out a lot of ideas.

Thanks to Scott. His first contact with him was to transfer the team's blog maintenance work. I don't know how, so I play together and add meals together. It will take one or two times a week with Marlon and Scott to talk about work and the leisurely life of single men, also known as DSD.

Thanks to Eric, Eric takes our intern every week for checkpoint. At that time, he always waited for Eric to release the next week's checkpoint question and then grabbed one of his favorite questions. I remember that one night I went late and thought I should be able to immediately grab one of Eric's questions. However, Eric had a hard time seeing out his mind. Eric had to pick a question after the next day. For this reason, the next day we adopted the method of capturing questions. During the Checkpoint Process, Eric will give me suggestions based on the performance of each of us and give me some good questions. Based on these questions, we can do more in-depth research afterwards. Thank you for your attention and responsibility.

Thanks to YF and dajie, and YF gave me an SQL azure account, which gave me the first access to Windows azure. After YF finished Teck talk, I also did experiments. For me who used to use traditional SQL Server, SQL Azure is a brand new experience. I would like to thank my sister-in-law for her help in SQL partition and index performance. Some of them are my own questions. Some of them are what I wrote after reading the official blog.Article.

Thanks to JC's answers to the Entity Framework question and the Teck talk of JC. At that time, I asked you for the reflector software, but I was busy with checkpoint and I had no time to play with reflector. So I have never asked you again.

Thanks to sonic, LZ, Michael, Steven, PL, and Doris for many times when intern is discussing a problem without any results, they will be very enthusiastic to help us solve the problem. Thank you.

Thanks to HW for reading the book you have written. We also remember your guidance on our checkpoint. Thank you.

Finally, I would like to thank intern, CX, YL, SC, and SY for their internships. The days when we prepare for checkpoints together are so memorable. Learning Together, playing together, and having dinner together are memories of my internship.

It is fate, because fate allows us to get together for four months. If there is another fate in the future, we will meet again. It may be your colleagues or customers. If you are a customer, ensure that each case is scored 9 points.

Best regards,

Wei Xu