Re: JAVA Developer

  • From: "Niall Litchfield" <niall.litchfield@xxxxxxxxx>
  • To: Joel.Patterson@xxxxxxxxxxx
  • Date: Tue, 9 Jan 2007 14:52:35 +0000

I see you've had the odd reply already..

I like to do a "technical test" and some interview questions... The
technical test would cover examples of (for a java guy)

1. connection pooling
2. statement preparation and execution
3. inheritance
4. bind variable/string substitution.

and probably I'd steal some of the other good ideas as well.

Interview questions I might ask a Java guy.

1. Could you describe the so called Object-Relational Impedance mismatch and
discuss some of the problems it presents for database driven development.
2. How might you decide between solving a problem at the client/in the
mid-tier and in the database? What factors might influence your choice of
language and solution.
3. What advantages and disadvantages typically arise from following a
waterfall development cycle as compared with an agile development

In principle then the technical test describes their technical competence or
otherwise - I've tended not to allow reference books, and accept typos/bad
syntax so long as it was clear that they were familiar with what they were
doing even if the exact syntax escaped them (I always put the docs on my
machines because I can never ever recall correct syntax first time around.
ever). The interview process is designed to guage how the candidate thinks
about problems, if they are aware of broader issues outside of their
specialism and so on. I'd probably always use this sort of approach even at
lower skill levels, though I might modify some of the questions.

One of my previous colleagues always used to throw in a question like "if
you were an animal what animal would you be?" to see how they dealt with
sudden unreasonable and irrelevant questions. This is a mean, mean thing to
do and requires great chutzpa on the part of the interviewer. In
environments where you are subject to sudden unreasonable demands though it
might be appropriate.

On 1/8/07, Joel.Patterson@xxxxxxxxxxx <Joel.Patterson@xxxxxxxxxxx> wrote:

 We are getting ready to hire a JAVA Developer, and I was asked if I
wanted to ask some questions relating to the database.... or to see if we
get along.

Connection pooling comes to mind, not imbedding code that would become a
cpu issue, etc.

Not having much experience with Java, do anyone have questions I could
entertain?  Some of you may have had such an experience already, and could
pass on a couple questions you wish you had asked, or would ask next time.

Joel Patterson
Database Administrator
904  727-2546

Niall Litchfield
Oracle DBA

Other related posts: