How to prepare for an interview? NET programmer?

First, the interview skills of NET programmers:

The interview is a wonderful thing. In a short time, let a complete stranger know his professional ability, his personality and his professional habits. Similarly, the interviewer needs to judge whether this is a reliable company, whether it is rich, whether it is suitable for his job and whether it is in line with his development direction. Work is like marrying a wife. I don't mean to change casually, but to face things every day. So finding a good business and a good job is too important for a person who supports himself. The first step in finding a good business and a good job is an interview.

First, interview your comprehensive quality.

1, basic grooming etiquette:

It's not really about the interview. Basic grooming etiquette is also very important in daily life, which is the basic requirement for whether a person is educated or not.

Dress: If there is no special need, don't wear formal clothes, just casual clothes. But don't wear barefoot slippers, vest straps, and men don't wear open-toed sandals. Just be clean and tidy, which shows the importance of this interview and respect for the interviewer.

Appearance: Ladies should wear make-up, either light or plain. Men cut their hair short and shave off their beards. Again, clean and tidy, and never smell in your mouth or body (especially the smell of your feet, never).

Etiquette: say "please", "you" and "thank you" more often, remember to close the door when you enter, and remember to take out the water poured for you at the front desk and throw it away when you leave. Sit down and face the interviewer, don't be too casual as at home, speak clearly, speak slowly, and don't shoot like a machine gun. Remember, don't be artificial, just grasp the scale in the details. If you disagree with the interviewer, shut up immediately, don't argue, don't try to convince the interviewer, and don't laugh at or despise the interviewer, even if you really don't know where you are better than the interviewer. Remember, this is politeness, and it has nothing to do with how good your skills are.

Modesty: at any time, put yourself in a relatively low-key position. I am here for an interview, not to educate the interviewer. I face the interview with the attitude of reviewing and studying. I never thought my protagonist was the best in the world. Modesty, at least, won't give you a chance to be a buffoon.

2, professional basic knowledge:

For Cheng, professional basic knowledge is absolutely the most important, which is also the most basic element of successful interview. When I say professional basic knowledge, I don't mean how many projects I have done and how many lines of code I have written, but the basic knowledge of software development.

During the interview, sometimes you will meet some candidates. At first glance, their resumes all have several years of work experience and full of projects, but they can't even answer questions such as "What is the essential difference between reference types of value types", "What are the characteristics of constructors and when to call them" and "What is the difference between classes and interfaces". Note that you can't answer them, that is, you don't know, you don't know the meaning, but you can't organize the language. Such candidates usually defend themselves after failing to answer several questions in succession: "I have strong hands-on ability and can write code, but I really don't know the concepts in the book." Being able to say this shows that this person simply understands what the most basic professional quality is as a skilled worker. So don't feel that you have worked for several years, and some code experience can already challenge higher-paying jobs.

Before the interview, you should first look at your mastery of basic knowledge. If necessary, you can buy your own books or find some information online, and use your spare time to study systematically, such as the language you use, such as the underlying implementation of the framework you are good at, such as compilation principles, such as multithreading knowledge, such as Http-related knowledge and so on. Don't go to the interview without a little basic knowledge reserve or a little basic knowledge reserve. The probability of failure is very high. I think everyone will be sad if I watch my favorite job opportunity pass by.

3. Communication skills:

The interview process is essentially a communication process. Candidates should try their best to show their advantages to each other in a short time, hide their shortcomings, try their best to get satisfactory answers to each other's questions and leave a good impression. Cheng is somewhat introverted, shy in front of strangers, and doesn't talk much. Of course, this can't be said to be a mistake, just some shortcomings in personality (if it is serious, there may be inferiority complex, which needs attention and correction). During the interview, the candidate must be full of energy, hold his head high, and have a firm eye. Remember not to appear erratic, and remember not to be arrogant. When we encounter a problem that we can't solve, let's honestly say "I don't know about it" or "I don't know about it". Never pretend to understand. He is trying to fool around. It is impossible to muddle through. The interviewer's question must be that the interviewer knows the answer clearly. Fooling the interviewer is fooling yourself. Is it interesting? Of course, don't answer at random, otherwise it will only become a joke for the interviewer and other colleagues after dinner.

During the interview, try to look directly at the interviewer (but don't stare at others), keep your back straight, turn on your mobile phone in airplane mode, speak clearly and neatly, try to say whether you can answer, and say you don't know if you can't answer, especially when it comes to salary. When the other party asks about your expectation, it's best to increase 10%-20% on the existing basis, and don't overcharge. Be sure to give people a sincere, capable, crisp and professional impression as soon as you open your mouth.

4. Past project experience:

Many interviewers pay little attention to their past project experience. Although every project they have done may only be a module or even a function, they will try their best to understand the business process, research and development background, internal module functions, how to integrate with the outside, the design of the underlying database, the overall system architecture and so on. When interviewing candidates, they usually ask about the latest projects. Many candidates will say that they have designed and developed projects, but even the functional modules and system architecture (note, not architecture) are not answered. Some interviewers like to start with past experience when interviewing some middle and senior programmers, and may ask questions at any time when introducing themselves again. Because this has two advantages, the first is to prevent the form of questions and answers, and the second is to start with the candidate's past project experience. In addition to seeing whether the candidate has false construction project experience, it can also judge the candidate's grasp of development details, as well as his response and mastery ability to some technical points. After all, "sudden attack" is more of a test for candidates than "aiming at shooting".

So before the interview, you should take a good look at your previous project experience, especially the last project, from business process to product design to system development, especially some details you have done in the project, which you are going to take out during the interview. You must take this as a point and consult relevant information. The other is the highlight of the project. The highlight is tall things. You need to know more about yourself, and you can get extra points when you take it out in the interview. When talking about this (highlight) in the interview, the interviewer is very interested in this piece. The deeper he asks, the more he knows, which gives him a lot of points.

5. Don't cheat:

When interviewing programmers, some companies like to throw a test paper at the beginning for candidates to do first, and then go to the interview. Let's not talk about the quality of the way to do the paper for the time being. Never use a mobile device to check the answers online when you are writing a paper. Cheating itself is disgusting. It would be embarrassing if the interviewer observed in the dark and found cheating. Yes, yes, no, no, even if you use your mobile phone to check the answers and fill in the test paper, the interviewer will still ask you questions on the test paper in the next interview, but you still won't. So don't cheat in the interview with or without supervision.

6. Mastery of popular technical points:

In fact, this is a bonus item. If all the above points pass the interview, then this will be your absolute highlight.

First of all, you should learn about the popular technologies by yourself, then analyze the positions you are applying for to see which popular technologies may be involved, and then find special materials for learning and hands-on experiments. For example, if you are engaged in the Internet, you'd better learn the technologies related to load balancing, distributed database, cache and static page.

If you are engaged in data analysis, you'd better learn Hadoop, Microsoft Cube and HP Vertical. If you are engaged in iOS, you can look at Swift, Xamarin, WebSocket and so on. Of course, I'm just giving a few examples. It doesn't have to be like this. If you are engaged in Java, you can also look at Pathon, if you are engaged in Java. Net, you can also look at Ruby on rails and so on. The so-called skill does not overwhelm the public, which is the truth.

Second, the above six points are the requirements for your own quality. If you can satisfy the interviewer on these six points, there is basically no big problem in the interview. Next, choose a good company or enterprise.

1. Is the interviewer professional?

The interviewer here refers not only to the technical interviewer, but also to HR or the big boss. If the interviewer asks you some wonderful questions (such as what car do you drive, how big your house is, how much your other half earns, etc.). ), or show obvious impatience, discrimination, arrogance, etc. You can basically conclude that this person is a great person, and this company should also consider it carefully, because this great person is probably your boss (or HR). A good corporate interviewer should show professional standards and at least ask some standard questions questions.

2. Try to find headhunters or peers to recommend:

In fact, the reason is very simple. If the company pays headhunters to seek talents, it shows that the company attaches great importance to this position, and it also shows that the company has the economic ability to pay relatively high recruitment fees. In this way, a round of screening was conducted for enterprises.

3. Working environment:

The working environment is not demanding, at least clean and tidy. From the state of the working environment, we can see some habits of enterprise managers. If the working environment is dark, damp and shabby, and employees are yelling, it means that managers either don't have enough economic conditions for rectification, or they have bad habits and don't care about the environment. I suggest you observe the working environment carefully during the interview. If it is bright, spacious, clean and tidy, and everyone is doing their own thing quietly, it is a good enterprise in terms of working environment.

4. Overtime, wages and benefits:

When it comes to salary, don't be shy. It is normal to add 10%-20% on the existing basis, as long as the asking price is not arbitrary. The salary mentioned here refers to the pure salary, the year-end bonus or other benefits that the enterprise can provide, which should be considered during the interview. For overtime, it is normal to do overtime, but ask clearly how to calculate overtime, whether it is overtime or vacation. Please carefully consider the following situations:

A. unpaid overtime.

B. force overtime to x point.

C. single break.

D. there is no year-end award.

E. there are no benefits except salary.

F.Offer or contract does not explicitly quantify salary figures, but says "linked to performance" and "based on performance".

Before the interview, check the evaluation of the company on a quasi-network (formerly called Zhilian).

Of course, you can also Baidu first. If it is a fraud company, you can find it directly, but some companies are actually not good internally, but they are not fraud companies, so at this time you need to go to an online search for comments. But not every company has an evaluation, there are many small companies, and there is no one on a quasi-Internet. But it is also right to hold the idea that no negative comments are good. If a company obviously has a lot of negative comments, and you just want to go to this company for an interview, I suggest you think it over.

6. When interviewing at home, go to the bathroom and have a look:

Yes, just go to the bathroom. You can arrive in advance, then ask the front desk bathroom and go to the bathroom to wash your hands (or after the interview), especially depending on the quality of toilet paper. Of course, let you see the environment of the bathroom and the quality of toilet paper, not to measure whether you are comfortable here in the future, but to see the attitude of enterprise managers to managing enterprises through the condition of the bathroom. If a company has high requirements for toilets, good decoration, good sanitary conditions and even good quality of toilet paper, then in other respects, there should be no difference in treating employees. You may not believe it, but almost all the enterprises I have seen meet this requirement. Bad corporate toilets must be worn out, and damaged nostalgic facilities will not be repaired in time. Toilet paper is the cheapest. Moreover, a good enterprise bathroom is beautifully decorated, with clean facilities and thick and soft toilet paper. Actually, you can pay close attention to it. Good shopping malls, good schools and bathrooms are all relatively high-end.

In fact, the interview still depends on your own strength, so no matter how many skills you have, only when your technical level reaches a certain level can you win your favorite position.