Java Fundamentals reinforces 5 reasons why 52:java programmers fail to interview

Here are 5 of the most likely reasons for a Java programmer's failure to interview, and of course maybe the 5 reasons apply to all programmers, so if you are a programmer, please read the following carefully.

1 Too little to say

especially those open-ended questions, such as "Please Introduce yourself" or "Please tell me about the complex problems you have solved". The interviewer will evaluate your passion through your answers to these technical and non-technical questions. They also judge your experience and ability by simulating the team atmosphere and interacting with you.

So, just two or three words to answer not only can not show your interest in this major, but also make the whole interview process seems very boring. If you can't explain the value that your experience, accomplishments and skills can bring to your business, then your competitiveness is no doubt high. So, you need to be fully prepared for some of the most common open questions and learn to sell yourself.

2 said too much.

Constantly said, constantly said, but there is no substantive content. In other words, it's nonsense, saying nothing. If you can't explain the problem succinctly, the interviewer will wonder if your performance at work will be as messy as your conversation. You can ask the interviewer first to determine if you really need to explain in detail.

Interpretation is also an art, the key is to determine the focus, if necessary, then go deep into the details. When it comes to business, you should look at it from a business perspective and don't involve any technical terminology. Learn to explain the problem in a concise and clear way. This is not a problem if you can always grasp the gist.

3 answers to some basic technical questions that must be known

The interview is not a technical contest, not a question of who answers the questions more, but there are some core Java and Web basics that must be known, and you can't know. For example, for Java developers

1) Do not know the difference between "= =" and Equals ().

2) do not know the convention when the Equals () and Hashcode () methods are implicitly invoked.

3) Do not know the concept of OO and design principles.

4) cannot handle multithreading very well.

5) do not know how to maintain state between HTTP client and server side.

6) cannot explain the high-level architecture of an application that has been put to energy.

7) do not know SQL.

...

4 Write not simple code, and can not answer how to solve the difficult problem

As a developer, you should write code for a given problem and situation based on your level of experience. Especially if you have a tricky problem, even if you don't have a solution, you should talk to the interviewer about your ideas. Of course, this can be especially stressful during an interview, especially if there is a time limit, but you also have to stay calm, at least to explain how you will try to solve the problem.

5 Bad manners and attitude

Late, inappropriate dress, shaking hands shaking feet, no eye contact, too tense, no questions, show no interest in this occupation, "I know everything" of the arrogant attitude, belittle your present and previous employers, when encountering technical problems irritable or depressed, for their own reasons instead of humbly accept the mistake, Quarrel with the interviewer, bad body language, drift without their own views, too stiff, lying, too loud to be a good listener, and so on.

Tip: The interviewer is not looking for technology stars, but actually has the right technical skills, soft skills, a correct attitude and to gain benefits for the enterprise, comprehensive professional talent. Therefore, it may be useful to study the organization you want to apply for, and learn more about its work practices to adjust the direction and focus of answering questions. Each interview as a free training course, and actively adjust the mentality, not only to achieve a win situation, but also reduce the tension of the mood, so as to achieve better performance. This way, even if you don't get the job, you can learn something and get progress.

Java Fundamentals reinforces 5 reasons why 52:java programmers fail to interview