Just after the New Year's Eve this year, a few days after returning to work, I was assigned as an interviewer by the leader. It's been half a year now.
When I received this task, I was a little apprehensive. One was a patient with social phobia. Every time I had face-to-face and one-on-one chats with people, I was more or less embarrassed and unnatural. I am not confident enough to evaluate others at will, and I am always worried about exposing my own shortcomings during the interview process and being teased by candidates in their hearts.
So I specially prepared a lot, searched for some basic interview questions, and made an outline of the questions. At that time, I was a little worried, whether the questions I prepared were too simple, and a normal person could pass the interview by simply swiping a few quizzes. Later experience proved that I thought too much.
The first interview was scheduled on a weekday afternoon. During the epidemic, all remote video interviews were conducted. Still, I booked a meeting room early and tried to create a quiet environment that wasn't disturbed.
Candidates are online as normal, very good, very punctual. Let him do a brief self-introduction first. Well, it's really simple, and it's all on your resume. Then I asked about the usual development language, technology stack, etc. I didn't ask about the technology in detail. This part is okay, what to say. Then start asking some technical questions. After all, I am an interviewer, and it is understandable to investigate more basics. The deep digging of the details of the project is left to the second and third sides. He answered many questions not so clearly, the language organization was a little confusing, and some details were a little forgotten. A few questions that I thought were "send points", I didn't expect to be able to answer them. If you give points, I can barely give a 60 points. In the last part, he asked me questions, and he simply asked what projects the team was working on and what the scale was. And then it was over, lasting about 50 minutes in total.
After a little hesitation, he let him pass the interview. One is to be an interviewer for the first time, hoping to have a good start. This is his luck. The other also wants to touch the standard of two sides and three sides to see if this level is feasible. for reference in future judgments. As a result, he hung up. Then I know, the bar needs to be raised a little bit.
During the interview later, I also encountered several situations that made me hesitate to give it to him. After struggling for a long time, I passed it, but I failed on the second or third side. It made me realize that if you are hesitant about a person, forget it. Much like love.
After that, it was much smoother and calmer, and my mentality was not as nervous at the beginning. In the process, I met a variety of job seekers.
Some people work really hard and will memorize a lot of interview questions. It's really just memorizing it without saying a word. How did I feel that he was on his back? One is the tone. Students who have memorized the text know that there is a difference in the tone of recitation and normal speaking. Another is language, the language he uses is obviously refined and leans towards written language forms. Also, the obvious thing about reciting is that it pauses in a lot of random places. Because forgetting is actually random, and these pauses due to forgetting may be logically smooth, and there is no need to stop and think. Also, if you ask one or two points down based on what he has recited, he will not know at all, or if you ask a point that he has not memorized, he will simply say he does not know. In the face of such job applicants, I was very moved, and then refused.
Still others expect to cheat to hide from the interviewer. Every time you ask a question, he will pretend to think for a long time, his eyes will go up and down, his shoulders will start to move unnaturally, and you can even hear the crackle of typing. At this time, I knew that he was secretly searching for the answer. Don't fool the interviewer this way, it's really easy to spot. At least, you have to learn to play blind. Then the microphone is farther away from the keyboard so that typing is not heard. Lastly, you also need good body control to ensure that there is no movement above the wrist as you type. If you can't do it, give up the idea.
Finally, there are some people who are very arrogant during the interview process, but can't answer the questions, giving you a feeling of "these questions are too simple and I don't bother to know". He will even tell you, don't ask these useless things, you can get them from Baidu. For such a big brother, on the one hand, I express my admiration for the high level and see far away, on the other hand, I silently hang up. In fact, this is also the confusion of many people. Whether the basic knowledge in the interview is important or not, do you have to remember all the details?
There is an episode in "The Strongest Brain". There is a huge question board in the center of the stage that keeps scrolling, and various graphics are recorded on it. The contestants need to find all the graphics that meet the conditions on the question board, and then go back to their answering positions for splicing and combination. . During the game, two types of people can be clearly seen. A type of person needs to constantly run between the question board and their position, memorize one, come back to assemble for a while, and then memorize again. The other kind of people only need to read the question board once, and then come back to complete the whole assembly, because they have all memorized. In the end, this type of person even took one-tenth the time of the first type. The guests said that being able to remember and not being able to remember are two levels.
Corresponding to the process of software development, in fact, the same is true. One difference is that we don't ask you to remember quickly, only that you can remember, no matter how long it takes. If you need to search for simple knowledge points in the process of work, it will greatly reduce your efficiency. Not only will it waste the little time you search for, but it will also interrupt your continuous thinking. So in the interview process, if it is really uncommon details, you can not remember, but if it is recognized basic knowledge, you must keep it in your heart and blurt out. Only in this way can we not be interrupted by these trivialities when conducting large-scale in-depth thinking, and we can smoothly carry out higher-level design.
In addition to solid basic knowledge, what else can win the favor of the interviewer and increase the chance of passing?
I think the first is attitude, we must be sincere and humble. Honesty means that you should truthfully report your level of knowledge without exaggerating too much. If you don't know, just say you don't know. The interviewer often just looks at your technical breadth and adds points if you have it. It doesn't matter if you don't. On the contrary, if you say that you are proficient in a technology at the beginning, you will not be able to say a few points later. This will be more of a deduction. Modesty means that although you sometimes disdain the interviewer's questions, don't show it. Other people's questions may not be suitable for you, but they are suitable for other people's business. If you want to pass the interview, answer the questions honestly without being overconfident.
Another important thing is the logic, or structure, of the expression. Be as smooth and organized as possible. It was a real pleasure to communicate with such a candidate. Even if some questions cannot be answered, they will get extra points because of smooth communication. This can only be done by exercising a lot on weekdays. It is recommended to read "The Pyramid Principle" and look for tutorials on structured expression on the Internet. Then prepare a set of your own answers under the framework of structured expression for some common interview questions.
Looking back on my six months as a technical interviewer, I also have the opportunity to examine myself when evaluating others. Have you mastered the questions you asked yourself? Do you have what you expect from others? If you interview yourself, would you give yourself a pass? Come to think of it, I still have a lot of room for improvement. The road to programming is a long way to go.