Java Interview Questions
http://www.javacamp.org/jobinterview.html
http://www.artima.com/forums/flat.jsp?forum=1&thread=27112
quote
Re: EJB & J2EE interview questions Posted: Apr 11, 2004 8:46 PM Reply
You guys are so full of it. I've been in this business for over 20 years for various start ups and based on my experience, there are lot of great engineers out there who are not capable of articulating the difference between a servlet and an applet, let alone the difference between a EJB, regular java class, container class, ...
Just because a person can't memorize definitions and can't recall how certain methodology behaves based on what we decide to call them does not make them a bad programmer.
Best way to interview is to simply talk about how they handled their previous projects. Ask them what they did and have a length discussion about it. If you are a good interviewer, you should be able to grasp the project they worked on and ask intelligent questions based on what they were trying to do. It is here where you can weed out the fakes from the real engineers. If they're entry level, talk about their projects.
Don't ask them stupid questions like "what is XXX and how is it different than YYY and what is the behavior of XXX". Who gives a crap? Just look it up.
unquote
quote
Sante, the guys are not only full of it.
Their style presumes that what is learnt over many gruelling night is all what J2EE, EJB, etc. is about. The questions are so artfully phrased to reflect recent experiences, which, while it took the interviewer weeks to resolve, he expects the inetrviewee to answer on the spot. I know. I did exactly that before I GAVE UP playing these tricks.
In most cases junior technical leads and managers tend to go to the interview to ELIMINATE the candidate, not to find out what he can BRING TO THE TABLE. Hence this rediculous game that ends up with loss of real talent due to a new form of bigotry, called professional bigotry of the low level tech leads and insecure managers.
Try finding out the capacity of the person to do the job, rather than whether he had memorized one web site answers or another. That is the way to do a job like recruiting talent. Everybody can make a candidat s*** in his/her pants, but not many can secure the best talent for the team!
unquote