A mechanical engineer who changed his career to Java/JEE in 1999. Maintains a Java/JEE career website at http://java-success.blogspot.com. Published 2 books on Java/JEE entitled: 1. Java/J2EE Job Interview Companion. 2. Core Java Career Essentials The above books are available via Amazon.com. Arul has posted 15 posts at DZone. You can read more from them at their website. View Full User Profile

Two most common job interview questions and how to tackle them

  • submit to reddit
Q. Why are you leaving your current job? What do you like and dislike about your current job?
A. Firstly, never be negative about your current or previous jobs. Also, don't bring salary into the discussion.


  • Enjoyed the people I worked with.
  • Enjoyed solving technical and business problems.
  • Enjoyed identifying gaps in the business requirements and technical designs and getting them rectified collaboratively.
  • Enjoyed pro-actively identifying and fixing issues relating to non-functional requirements like performance, security,  concurrency and memory leaks. These issues don't surface under normal scenarios and can be very challenging and satisfying.
  • Enjoyed writing unit tests and initiating other code quality measures like automatic code reviews via tools like sonar and peer to peer reviews, and continuous build and integration tools.

Dislikes: (give a positive spin to your dislikes)

  • Main reason for leaving is that I felt that I was not challenged enough at my current job. The company offered a great opportunity as someone with 2-3 year experience and appreciate the skills I acquired there, but now I am ready to face more challenges and take my career to the next level.
  • I am looking for more potential to grow in my next job.
  • I am also looking for an opportunity to get more involved with the hands-on design decisions in my next job.

Q. What was the biggest accomplishment and failure in your current job or career?
A. Reflect back on your career achievements and provide quantified answers.


  • Successfully completed a high profile Java/JEE based online trading system that handles 100+ concurrent users and integrates with 4 other systems.
  • Designed and developed a Java based non-blocking server that communicates with 240+ retail outlets, and integrates with 6 other internal systems.
  • Spearheaded a "Quick-Win" program that improved the site ranking from 24th to 9th in 3 months in terms of user experience, performance, and reliability.

Failures: (provide a positive spin to your mistakes or failures)

We all learn more from our mistakes or failures than from our successes or achievements.  When you mention your mistakes or failures, make it a point to mention what you learned from them. You could say that these are classified more as mistakes than failures.

  • The team was using a cut down database in the development environment and the technical solution I provided worked well for  low volume of data, but when was moved to production like data, it caused some performance issues. Learned a valuable lesson of validating the solution with more production like data set early on in the SDLC. I subsequently revised the solution within a week and got the the big thumbs up from the users.


  • Wrote some JUnit based integration tests that were bit fragile due to data fluctuations. The failing tests were causing the builds to fail. Took the initiative to fix this problem by performing the integration tests via more stable data sets that are populated via DBUnit during the set phase and the data are removed during the test tear down phase. Also, introduced other strategies for integration tests by using in memory databases like HSQL DB as opposed to actual database.


  More Java interview questions and answers


Published at DZone with permission of its author, Arul Kumaran.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Ronald Miura replied on Thu, 2012/03/15 - 10:04pm

Lie and omit, because most companies can't handle the naked truth. Or really turn into an optimist-team-player-robot (which is what all this kind of 'interview guidelines' are all about).

Matthew Welch replied on Fri, 2012/03/16 - 8:47am

Seriously? Do you think the people giving the interviews are idiots? I interview people for developer positions at our company and if they answer in the way described in this article, it's a huge mark against them. The only companies that want watered down, non-specific, peaches-and-cream answers like this aren't companies that you really want to work for anyway.

Arul Kumaran replied on Sun, 2012/03/18 - 6:44pm in response to: Matthew Welch

Provide reasons as to why. Criticising is easy. Anyone can do it.  Obviously no interviwer is going to make hire/no hire decision based on the above 2 two questions. There will be more coding based, scenario based, open-ended, technical, and non technical questions.

Jacob Share replied on Sat, 2012/03/17 - 2:45pm

I partly disagree. It's okay to be negative. Intellectual honesty means not sugarcoating things and good bosses want intellectually honest employees. If you can't see things with a critical eye, you won't go far. That said, do not badmouth anyone by name.

M Leslie replied on Sat, 2012/03/17 - 4:32pm

I really do hope the guy interviewing you next reads this article. Should make it easier for him to realise that you are spinning a story. 

Skillgun Guide replied on Tue, 2014/01/28 - 4:04am


Here is link for lots of technical and aptitude interview questions http://skillgun.com

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.