10 mistakes programmers often make when preparing for interviews, shared with programmers about to attend job interviews, hoping to be helpful to everyone.

1. Practice Only on the Computer

If the interviewer wants to assess your skills, they may ask you to write code on a whiteboard rather than on a computer. So you can't just practice on the computer. The compiler on a computer will automatically detect your syntax errors, but a whiteboard won't.

Take out a pen and paper to practice writing code. If you check it yourself and think the program is correct, then type it into the computer to see if it works as originally intended.

2. Not Preparing for Possible Questions

Before the interview, be sure to prepare for questions that might be asked. Questions may involve projects you've worked on, the different problems you encountered, and how you solved these challenges. Your answers will affect the interviewer's impression of your technical ability.

Before the interview, review the projects you have worked on and organize your main achievements.

3. Not Doing Mock Interviews

The reason is obvious. It's best to rehearse what questions might be asked during an interview. Also, during the actual interview, although the interviewer will ask you questions, you can also ask them questions, so you should prepare in advance what questions you want to ask.

4. Blindly Memorizing Solutions

If you plan to memorize answers in advance hoping to use them when needed, I advise you not to bother — it's a waste of effort. Because the probability of hitting exactly the answer you memorized is extremely slim.

On the contrary, preparing solutions also requires a lot of time and effort. Remember, the better you perform on the spot, the higher your value will be.

5. Speaking in a Low Voice

Generally speaking, speaking in a low voice can make people feel that your thinking is unclear. So, communicate well with the interviewer about any questions. That way, you can show your thought process and help them correctly judge the value of the solution you propose, and of course your value.

6. Speaking and Acting Without Thinking

Organize your language well before answering questions. Saying whatever comes to mind will only expose your carelessness. Your words should be organized and precise. As for action, carefully check the code after writing it.

7. Bad Coding Habits

A bug-free solution alone doesn't mean you will definitely do well. You also need to be aware of duplicate code, messy data structures, excessive spaces, and so on.

Write code as if for real applications. Design data structures and create functionality with logical thinking, and make sure the layout follows the conventions of the language you're using.

8. Not Testing

After writing code, be sure to spend time testing it to ensure there are no bugs. This process also requires practicing with paper and pen; otherwise, if you are asked to write on a whiteboard during the interview, you will feel insecure!

9. Being Careless When Fixing Errors

After finding a bug, it's best to think about the cause first, then take action. Don't rely on changing a boolean value or randomly flipping a flag in a loop to solve the problem. Doing this only shows that you have no idea what error you made and that you aren't patient or careful enough to check the problem.

10. Giving Up

There will always be some problems that are beyond our abilities. The interviewer wants to see your attitude — whether you are brave in facing challenges or you back off as soon as you encounter a problem.

The key is to show a spirit of rising to the challenge. Companies want people who can actually use code to solve problems, and you need to show them that you enjoy the process of solving problems.

Translation link:http://www.codeceo.com/article/10-common-mistakes-programmer-interview.html
English original:10 Common Mistakes Made When Preparing for Coding Interviews
Translation author:Code Rural Network– Xiaofeng