Seven reasons Java programmers through the interview without
preamble:
Now is the peak of graduates looking for work, then what problems will arise in the course of the interview Java programmers in it? What problem are entering the workplace Java programmer in a job interview most likely to commit it? Below, I summarize the five reasons why Java programmers do not pass the interview, for your reference.
Why not get a JAVA programmer wants to offer these reasons you are aware of it 
1. The ability for the job is too high or too low
Because of the low capacity and there is no chance this is normal, so too will also affect the ability to hire you? In fact, demand from this sector employment stability and leadership of view. High expectations of the ability of people in the higher positions in general, once this position can bring him either treatment or career growth than less, then quit shortly after the almost entirely predictable result, long-term stability is relatively poor. The employer does not need to department heads is perhaps too high capability employed by job demands, convenient management also better training, engaged in years of worry-free future HR work friends "leisurely moon and stars," once said: "Maybe, the other department heads are not keen to find a man to share his duty, he just needs a helper, so the more you perfect, but more through the audit department. "
2. The tendency shown by past experience does not meet company expectations
Simply put, past experience has flaws, but this does not seem to affect the flaws completely eliminated, is likely to affect the state of your next job. As like frequent job-hopping, and now there is still this tendency; to take care of the family, it is difficult to take into account the work; venture failed, the state has not yet adjusted; work experience and work experience does not match the gold content; Job Target too confusing, for their lack of career planning .
3, unfocused speech
In other words, nonsense, saying nothing. If you can not succinct explanation of the problem, then the interviewer will wonder when you will work is not the same as talking to you, dragging its feet. So in the interview process, you can ask the interviewer, the need for a detailed explanation.
Interpretation is an art, it is critical to determine priorities, if necessary, and then deep into the details. When talking to the business, you should look at the issue from a business perspective, do not involve any technical terms. Learn to explain the problem with a clear and concise manner. If you can grasp the moment the subject, then it is not a problem.
4, said too little vague
Especially those open-ended questions, such as "Please introduce yourself down," or "Please talk about solving complex problems you have had."
The interviewer will assess your passion through your answers to these technical and non-technical issues. They will be judged by your experience and the ability to simulate and communicate with your team atmosphere interactions.
If you are not a good indication of the value of your experience, skills and accomplishments can bring to the enterprise, then your competition will not engage. So you need to open some of the most common questions and answers be fully prepared, learn to sell themselves.
5, do not understand the basis of the technical problems
An interview is not the technology race, not to see who answer more questions, but there are some "must know" the core Java and Web basics, you can not know. For example, for Java developers:
I do not know the difference between () "==" and equals;
Do not know equals () and hashCode () method is invoked implicitly agreed upon;
I do not know the concepts and principles of OO design;
We can not handle multi-threaded;
I do not know how to maintain state between HTTP client and server side;
I can not explain the effort has been put into application the high level architecture;
I do not know SQL.
6, not write simple code, can not solve the thorny problem
As a developer, you should according to their level of experience, to issue for a given situation and writing code. Especially if you encounter a more difficult problem, even if you have no solution, you should tell the interviewer to listen to your ideas.
Of course, this will make people during interviews particularly tense, especially in the case there is a time limit, but you must remain calm, you should at least try to explain how the method to solve the problem.
7, bad manners and attitudes
Late, inappropriate dress, shaking tremor feet, no eye contact, too nervous, no question, show no interest in my career, "I know everything," the arrogant attitude, to belittle your current and former employers , encountered technical problems or irritability dejected, dispute with the interviewer to find reasons for their occurrence rather than humbly accept mistakes, bad body language, their own views and not follow the crowd, too stiff, lie, his voice is too large be a good listener, and so on.
These are a few reasons for my summary of Java programmers in the interview does not pass. In fact, every game interview can be seen as a test, and draw lessons for lessons.
Like this article, they should point to the author likes to point at attention, will share Java-related articles every day!
Remember to focus on me oh, will occasionally presented benefits, including consolidation of interview questions, learning materials, source code, etc. ~