>         Hehe, this reminds me of a case where a person being
> interview had made a
> typo on their resume. When pressed it was obvious the person had no idea
> what the CORRECT word was. After some drilling it was determined
> the persons
> FRIEND wrote THEIR resume!??! Very funny...

It is especially important to dig deep on resumes that from
from contracting agencies -- I had a contracting company put
me up for a position, and in the interview I was asked things
I didn't know, nor claimed to know.  Apparently the contracting
agency significantly adjusted my resume to the point of blatant
lying.  Not only do I not want to be misrepresented, but I
don't want to land a position where I don't know the subject
matter I'm expected to.

On the flip side, I now delve deep into contractors' resumes
and have caught many lies.



>         And then, of course this might sound obvious, but...
> NEVER GET ANGRY during
> a interview! One person got angry at the interviewer because
> he/she felt the
> question was "unfair"??

Funny story ... back at Nortel some years back, I asked a SQL
programming "expert" to tell me  the output of a query (with
tables/data listed) and of course used an outer join.  He tried
for 5 seconds, got pissed off and got up, claiming that it was
unfair and was not expecting to have a pop quiz.  !?!?!?

Guess I've been around too much. :-)

Cheers,
-Neil.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.