8 mistakes you shouldn't make during programmer interviews

1. Don’t prepare for experience issues

Be sure to spend more time recalling your past relevant experiences, including the projects you participated in, the various difficulties you encountered, and how you solved these problems. Your answers will affect the interviewer's impression of your technical abilities, so be sure to review and organize your past project experience.

2. Relying on memorized answers in advance

Trying to memorize some answers in advance and then use them in the interview is a very bad approach. First of all, the probability of being able to use the answers you memorized is very slim. Secondly, such preparation will cost you a lot of time and energy without any real improvement in ability. Remember, the better and more authentic you are on the spot, the higher your value will be.

3. Lack of simulation of interviews

This is obvious. You need to prepare and simulate before doing many things to prevent unexpected situations from happening. The same goes for programmer interviews. If you are preparing for a programmer interview, you should find some programmers who can prepare with you. You can simulate the interview scenario together and ask each other questions.

4. Not showing the thinking process

If you don’t speak for a long time when answering a question, it will be understood that you are unable to answer the question. If you don't provide a thinking process, the interviewer will not be able to understand your thoughts and will not know whether you are thinking or are stumped. However, if you keep talking to the interviewer, he will understand your thoughts and see your thought process, which is important. And when your thinking deviates, the interviewer can also guide you back to the correct solution.

5. Writing code is inseparable from an editor

If you are going to participate in a technical interview, the interviewer will usually ask you to write code on a whiteboard/paper instead of on a computer. Therefore, you cannot rely too much on the code editor, because it will help you add code there, show you grammatical errors, etc. Quickly take out a pen and paper and write down your code. When you are satisfied with the program you wrote on the paper, enter it into the computer and let the compiler verify whether it is correct or not.

6. Failure to develop good programming habits

Don’t think that you have done a good job just because you have written an executable program. You also need to pay attention to whether there are repeated codes, confusing data structures, excessive white spaces, etc. in the program. Just like in actual development, design more logical data structures, have better frameworks, and make the code cleaner and easier to read.

7. Not testing

After your program is written, take a moment to review your code to make sure there are no bugs in it. If you are practicing with pen and paper, you need to write the program into the editor again and let the compiler help you check it.

8. Always in a hurry

Don’t be in a hurry when solving problems, otherwise it will only lead to more mistakes and make you look careless. Be methodical and precise. Look back at your code often and correct errors if they appear. By doing this, it will actually take less time to complete the project and there will be fewer errors.

Receive LAMP Brothers’ original PHP video tutorial CD/"Essential PHP in Detail" free of charge. For details, please contact the official website customer service: http://www.lampbrother.net