In the programmer's written test and interview process, what are the deductions and bonuses in the eyes of the interviewer?

Since I started working in 2007, the author has been engaged in the design and development of enterprise-level application software for 15 years. During this period, I have also served as the company's written test and interviewer for many times. Here are some deductions and bonuses in my eyes. This article represents my personal opinion only.

Resume link

When a programmer submits a resume, the interviewer usually does not have too many requirements on the appearance of the resume (ie font, typesetting), as long as the content is concise, clear and easy to read. Try to avoid any typos.

However, there is a deduction item that all job seekers should pay attention to. In the technical terms related to the position you are applying for in your resume, you must not make spelling mistakes. For example, once I met a job seeker who applied for an HTML5 front-end development position, but he mistakenly wrote HTML5 as HMTL5 in his resume. After he completed the entire interview process and before he left, I kindly pointed out the spelling mistake to him. .

Or in his eyes, this is just a small problem, not worth mentioning, but in the eyes of our interviewer, we will think that the interviewer is careless and not rigorous enough.

Written examination

We generally email the written test questions to candidates, giving them one to two weeks to complete. Finally, submit the source code of the answer to Github.

During the process of answering the questions, we can view other code submission records of the applicant's account on Github. If you participate in other open source projects in your spare time, it is undoubtedly a plus. In the process of candidates submitting the code of the written test questions, we will observe the candidates' problem-solving ideas and basic programming literacy through some details of the candidates' git commit message.

If the candidate submits all the code to Github at one time until the deadline, we also feel that this behavior is slightly deductible, because this operation does not leave any buffer time or wiggle room. If it is practical work, a professional programmer tends to submit the locally written code to the develop branch when the project is released, how much trouble will it bring to its peer programmers and Quality Engineers?

Interview session

If it is a fresh student seeking a job, the interview is divided into two rounds of group interview and 1:1 interview. If it is a social recruitment, generally there is only a 1:1 interview.

Some candidates may think that the more positive they are in the group meeting and the more they speak, the better the impression they will make on the interviewer, but this is not the case. In the group group meeting, each group is generally assigned a topic, conducts group discussions within a specified time, and finally selects a group representative to give a presentation.

If the presentation made by the group representative is clear and the subject is prominent, it will undoubtedly be a bonus. However, the interviewer will also carefully observe the group meeting, each team member's contribution to advancing the topic discussion, and even to the final presentation, which is a result-driven assessment method. Even if you actively speak during the discussion, if your ideas and directions are contrary to the final presentation, it will not leave a good impression on the interviewer.

In the 1:1 interview process, the first thing candidates should pay attention to is honesty. For example, "participating in a project" is packaged as "playing the core design and development work in a certain project". It is undoubtedly a very embarrassing thing to be discovered during the communication process, and it will also become a deduction item. In the process of technical communication, if you encounter a knowledge point that you are not familiar with, or reason based on your existing knowledge system, tell the interviewer your understanding, or admit that you have never understood this before, these two Either method is acceptable. Don't pretend to understand because you don't understand, go further and further in the wrong direction of discussion, and leave a worse impression on the interviewer.

The above are some of my superficial feelings as a written examiner and interviewer in the work process, I hope to be helpful to all job seekers.

This article participated in the SegmentFault Sifu essay "How to "anti-kill" the interviewer?", you are welcome to join.