Over a million developers have joined DZone.

Top 5 Reasons to Fail Java Interviews

· Java Zone

Navigate the Maze of the End-User Experience and pick up this APM Essential guide, brought to you in partnership with CA Technologies

These 5 Java or general interview tips will go a long way in getting multiple job offers. Multiple job offers not only empower you negotiate better salaries, but also gives you the confidence to go freelancing as you know that you can find work even in a difficult job market. Hope these tips will open more doors for you.

#1. Saying too little

Screen shot 2014-12-19 at 10.51.35 PM

Especially to open ended questions like “tell me about yourself” or “tell me a time where you had to solve a complex problem”. Interviewers will be assessing how passionate you are about cutting code and solving technical & non technical problems. They will also be judging your experience, ability to communicate your thoughts, and get things done in a team environment. So, just answering with 2 or 3 sentences will not only fail to bring out your real interest for the profession, but also will make the whole interview very boring. If you are not enthusiastic about how you can add value to the organization from your past experience, accomplishments, and skills, your prospective employer will not be enthusiastic to offer you a the job. So, prepare well for the most common open ended Q&As, scenarios based Q&As and edge case Q&As. You need to sell yourself and no one else will do it for you.


#2. Talking too much

Screen shot 2014-12-19 at 11.00.21 PM

Going on and on about yourself without much substance. In other words, lots of fluff without any stuff. If you can’t concisely explain things, how are you going to get things done on the job? Ask the interviewer(s) if they want you to elaborate. It is an art to look at the big picture and drill down to the details when it is required. When talking to the business, look at things from the business perspective without any technical jargon. Learn to explain things in a simple and concise manner. You can do this when you have a good handle on the subject matter.

#3. Failing to answer must know fundamental technical questions

Screen shot 2014-12-19 at 11.01.41 PM

Interviews are not technical contests to see who gets the most number of questions right, but there are a number of “must know” core Java and web basics that you can’t afford to not know. For example, for Java developers

1) Not knowing the difference between “==” and equals().
2) Not knowing the contract between equals() and hashCode() methods and when they are implicitly invoked.
3) Not knowing the OO concepts and the design principles.
4) Not having a good handle on multi-threading.
5) Not knowing how to maintain states between an HTTP client and the server.
6) Not being able to explain the high level architecture of the application you had worked on.
7) Not knowing SQL.
….

#4. Failing to write simple code and not thinking out loud for more difficult problem solving

Screen shot 2014-12-19 at 11.03.32 PM

As a developer, depending on your level of experience you must be able to write code for a given problem or scenario. When you are given a more difficult coding or a problem solving question, you need to at least think out loud to let the interviewer know as to how you would go about solving the problem, even if you don’t arrive at a solution or the right result. It is quite natural to be nervous at the interviews and the time limitation can make things worse, but at least explain the approach as to how you would go about approaching the problem.

#5. Bad etiquette and attitude

Screen shot 2014-12-19 at 10.55.17 PM

arriving late, bad dress code, sloppy hand shakes, not making eye contacts, being too nervous, failing to ask questions, not showing real interest in the position, “I know it all” attitude, bad mouthing your current and past employers, getting irritated and frustrated during the technical grilling, giving excuses as opposed to accepting your mistakes, starting an argument, bad body language, being an “yes” person without having your own opinion, being too inflexible, lying, raising your voice, being a bad listener, etc.

Tip: Interviewers are not looking for rock star techies, but for well-rounded professionals with right technical skills, soft skills, attitude and real interest to add value and get things done for the organization being interviewed for. So, research the organization and thoroughly understand the job specification to be able to tailor your answers. Take each interview as a free training session , which leads to a win/win situation and reduced nervousness to perform better. Even if you don’t get the job, you learn something out of it.

Thrive in the application economy with an APM model that is strategic. Be E.P.I.C. with CA APM.  Brought to you in partnership with CA Technologies.

Topics:

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}