Interview ASP. NET programmers

This article is intended for users who have one or two years of experience in coming to the interview. I hope this experience will be helpful to you.

I am the project manager of the company's technical department. Recently, my company has been recruiting personnel. I am mainly responsible for interviewing. NET programmers.

Speaking of the interview, let's talk about your resume first. I have read more than 300 resumes from October 17 to October 17. A lot of resumes are smelly and long-lived, and many of them are too big to be confused. All such resumes are rejected. It is very painful for me to look at my resume as if I were engaged in technical work. Some people write more than 1000 characters in their hobbies.

I think a good resume should focus on its own strengths. Many people do not have a strong resume, and they can do anything, people like Wanjin oil cannot sharpen anything except Superman in year 45. For those who have only one or two years of experience, I think a 4 K paper is enough for a resume. As for your project experience, it is better to talk with the interviewer. I would like to say a few more words, such as the motto in my resume, or belief or something else! After all, this is a mental thing that carries a false element.

The next step is the interview. People who receive a phone call can say that they have already had 30% chance to enter the company. 50% depends on their own abilities and performance during the interview, the remaining 20% is about looking at the company, and recruitment is not as bad as buying cabbage. If the company thinks that you can get into the company by "value for money", for general companies, the interview is often not the most competent person to enter the company, but the company thinks that the most valuable person to enter the company, in other words, the most affordable cabbage can be entered into the company. Let's take a look at the value of the 20% S. Estimate the estimated value and see what you can do to make things worthwhile. Now let me talk about the performance of 50%. I gave a set of questions to the programmers who want to interview. I changed the question to 50% C # language basics and database basics, and 30% for ASP.. NET. In 20%, I took the test to design a project. Speaking of the basics, I will talk about the currently used. NET

C # is a fully object-oriented language. Speaking of object-oriented, I think we should have some understanding. What is object-oriented? Why should we use object-oriented? The three object-oriented features of inheritance, encapsulation, and polymorphism are:

What does it mean? At least you can clearly describe it in your own words. Here I will give a brief introduction. For details, refer to the online materials:

1. The object-oriented model allows us to better cope with changes in requirements during project creation. The introduction of classes and objects is more in line with people's abstract thinking.

2. inheritance is used to achieve code reuse. Child classes can use the parent class method. Code hiding is achieved through encapsulation. Polymorphism reoccurs the behavior of the class.

These are not profound theories. Only those who have understood these basics can write code.

Although the current IDE programming environment is becoming more and more advanced, the code prompt function is getting better and better, but some basic elements are better remembered. One of the questions is the keyword when writing the Delegate statement: Delegate, many people

Are empty and cannot be written... Many people have been working for two years, and even four or five WEB projects have yet to understand JavaScript objects and DOM objects. It is really sad for a person who only pays attention to the application and ignores the theoretical basis. Maybe he

I will never think about the differences between them.

Let's talk about the answer. In the process of doing the question, some people did not finish the question every minute. As soon as I saw it, it was not really right, but most of the ideas were correct, this kind of person belongs to the kind of person who can do things but is not good at doing things .... PASS out. If there is such a person in the project, it is quite troublesome. The trouble is that he thinks that he has done a good job, but he has not done it yet. If not, he will have to rework. Maybe he will have to accompany me to work overtime!

Most interviews are for computer science graduates (non-graduates), but the word "Data Structure" seems to be like listening to tianshu. It's really sad! But I am glad to find someone who doesn't know the data structure better than I do. More than half of people have no idea about the data structure of "tree. There are hundreds of thousands of people with common data structures. I often hear people complain that what I learned from a university is useless. People with such ideas basically go into the water. The university cannot expect any experience, but should lay a good foundation. What are the computer composition principles, compilation principles, data structures, database theories, and so on? Even if they are hard to learn, at least these concepts can be found in the brain. Otherwise, it is hard for me to imagine how long a person can grow.

To design a project, I mean the object-oriented design principles and design patterns. These are Rarely touched by a person who has not worked on a medium or large project, especially programmers of a software company that often uses templates for development, it is even more difficult to understand the 23 design patterns. But I think we should know why we should introduce the design patterns. What is the main idea of the design patterns? In addition, there must be an indirect layer concept. The object-oriented design principle should be understood and understand the meaning of each principle. Otherwise, I will recognize this person as below. Many design patterns are applied to the. NET FrameWork class libraries. if you pay attention to them, you will find a lot.

Let's talk about this. During the interview, there should be no small actions or the like. During the interview, some people don't even look at me. I always look at the ceiling, some people turned to me while talking and holding a pen in front of me, so I was dazzled. Someone else raised their legs and answered my questions. These are really hurtful. In this case, I usually think that these people are under too much pressure and are often nervous, and I often PASS these people out. Most programmers are not talkative. When I ask them which projects they have done, they can be clear, but many of the answers from related modules are vague. This shows that they do not have a clear idea, there is no summary of the past. I am not asking them to remember the detailed modules here. I mainly want to take a look at what impressed him when he was working on a project and how he solved the problems. It's good to cook dumplings in the teapot. Most of them don't remember anything. In addition, many people's pursuit of this kind of technology is limited to small technologies, such as JS bullet boxes and special effect animations. If you have been working for a year or two and are still pursuing this kind of thing. The eight-to-one level is not high. After reading this, you may understand whether a person can be admitted to a company with only 50% of his/her abilities. However, I think that if a person has a persistent pursuit of technology, I don't care about other bad habits (personal habits, not coding habits. After all, it is not just about eating, but also about the pursuit of technology and a kind of self-challenge.

These are just some of my experience in interviewing others and I hope they will be helpful for me. Some may not be suitable for some people, because some companies decide whether or not to interview by the HR department. In this way, the more detailed the resume should be, the better, the more you don't know how to do it, the more time you spend, the less you don't have to do this to me.

I hope you can point out something wrong.