How should programmers interview?

Hi, dear programmers, if you have been working for several years, you must have interviewed. Today, I summed up how to conduct a successful interview from a personal perspective, hoping to help you. If you have started reading, you must have finished reading. Only those who have patience can achieve great things. If you are halfway through, this article will not gain anything for you, but will waste your precious time.

About the production of resume

Every technical interviewer has to read hundreds or even thousands of resumes every day, and the time to read a resume may not exceed 10 second. Your resume is a drop in the ocean. If you can ask the interviewer to select your resume from a large number of resumes, you need to work hard on your resume production.

Let me talk about my feelings here. I have also read tens of thousands of resumes of programmers. Let me tell you how I screened my resume. I mainly look at these places:

Education (I don't value this personally, but some companies have rigid requirements, such as you must recruit a bachelor's degree or above). You can truthfully fill in the skills used in the graduation school project before 5 o'clock and 3 o'clock. This is an unchangeable fact, so don't make a false report, because once it is found out, you know, the consequences will be very serious. About the project experience, I mainly write about the projects I have done, and put the most important projects related to the current company's business on it. Don't list some useless items on it, it will only bury useful items. The interviewer didn't find them in 10 seconds, so you were screened out. It's a pity. Similarly, the technology used in point 5 also needs to be written with emphasis. It is also important to note that you must understand these technologies yourself. If you can't, don't write, so it will be embarrassing to be asked in the interview.

About self-introduction

In fact, the interviewer has read your resume before this. At this time, self-introduction should be concise, highlight the highlights and avoid a lot of nonsense. Introduce yourself less, focus on some projects that you are proud of, choose several typical projects, not to mention several projects of the same type, and forget those without any characteristics. In short, let the interviewer get to know you in the shortest time.

About technical interview

Technical interviews are basically divided into the following three situations.

Written test, computer written test and direct chat with the interviewer

If it is a written test, you should answer it carefully on the test paper and write down everything you know. It depends on your basic skills. There is nothing to say. Don't answer questions you don't understand. Similarly, getting on the computer is also a chore, which needs to be cultivated at ordinary times. Here is mainly about how to talk to the interviewer about technology. First, one thing is clear. He is familiar with the skills that the interviewer asks you, so you won't ask him this question. Don't guess. You can say that you didn't pay too much attention to this aspect, and you need to make up for it in the future, and then introduce a similar question that you are familiar with, so that it is easy to transition over and lead the question from the interviewer's familiar range to your own familiar range. If the interviewer is familiar with this range, another taboo is that if you don't understand the problem, don't prevaricate with a bunch of nonsense, which will be seen through.

other

In addition to the above situation, let's talk about other situations that need attention. These are all details that need attention.

Be sure to reply when you receive an interview invitation email before the interview. You just know in your heart that you can't. You should reply, such as "Thank you, I will attend the interview on time". Don't be stingy to say thank you. These details can leave some impression on each other. Don't be late for the interview, and don't arrive early. Better show up on time. Interviews in most companies are arranged according to time periods, such as 8:00-9:00 for an applicant and 9:00- 10:00 for an applicant. These times are planned by others, so be sure to be on time and don't disturb others' plans. Every interviewer has his own career. If you come at a bad time, people may be busy at that time. Whether it is necessary or not, you'd better take these things, print some resumes, prepare a pen and a USB flash drive, which contains your own proud works. Don't talk nonsense when you encounter technical problems that you can't. It can be said that you have not been exposed to this aspect and need to study it later. When chatting with the interviewer, you should keep talking fast, don't speak too fast, don't get too excited, and stay calm. In the face of every question asked by the interviewer, think quickly first, then answer slowly and make it clear word by word. The sound doesn't need to be too loud, as long as the other party can hear clearly and maintain a relatively comfortable atmosphere. These details directly reflect a person's accomplishment. Always remember, the interview is not just a period of interview with the company, and all the communication before and after the interview is regarded as an interview link.

The above scenario can be carefully considered. Sometimes you have never experienced such a scene, and you may not be able to empathize with the above description. After reading it, you will pass by. It is recommended to collect this article. If you encounter similar situations in the future, you can find out this article and have a look. I believe it will help you. Finally, I wish all programmers and friends can find their favorite jobs!

Hello, everyone, I am "The world is a flower". If you have any good ideas or opinions, you can show your skills and interact in the comments area. If you want to know me better, then pay attention to me.