Re: Perils of technical interviews (was RE: Better way to code a maintenence program ILERPG)

david.kahn@gb.abb.com wrote:
> 
> I wrote:
> 
> >Colin Williams <Williamsc@technocrats.co.uk> wrote:
> >
> >>You mean you failed a technical interview because you were honest!
> >
> >Why? Is there an easier way?  :-)
> 

That really depends on the interviewer and what the interviewer wants. 
Which, of course, is sometimes VERY hard to figure out.

When I do a technical interview, I am NOT looking for the interviewee to
have all of the answers.  So, yes, sometimes it strays to the esoteric
for VERY knowledgeable interviewees.

What I strive for is SOME question that the interviewee stumbles over. 
I want to know how the interviewee handles a situation that they have
placed in front of them, for which they have no ready answer.

Reactions range from simple "No" followed by the silence that also
indicates they don't care to the instigation, by the interviewee, of a
mini training session.  In the latter case, the interviewee is
determined to walk out of the room with at least a better understanding
of the subject of the discussion even if they don't get the job.

That's the person I want working for me.

-- 
===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---