in reply to Interview with a Programmer

I'm far from an expert, but I've interviewed some people,
and use the simple same method which worked quite well for me :

I try to make the candidat comfortable/confident, make him talk a lot,
and try to only seek/look for the good sides, I'm not filtering the "bad", I'm chasing the "good".

It's not just rethoric, or "over-kind" attitude let me rationalize this to all of you who think that buziness is buziness
and that we only have to find to right person for the job, not be 'kind' in anyway.

Let me give some examples :

I know linux.
Q: What distro do/did you use ? what do you enjoy most with this distro ?

I know SQL/Databases.
Q: What is your favourite database and WHY ?
Or if he only uses/knows one : What is your favourite feature, what is the one missing to your mind ?

Even for those who stay elusive, you can learn a lot without 'examining' them :
I've written CGI scripts for just about every site in my resume.
Q: Which one is your favourite ? The one which makes you feel proud. can you tell me more about it ?

As you see, I ask them to speak about what they say they know,
and then try to estimate their answer based on what I know, and their way to answer.
It's not so difficult to check the veracity based on what you know.
Often simple details that match your personnal experience are enough :
'mod_perl just run fine, I just got bitten once with a script using __DATA__'
'The custom server install was a little buggy, especially with the network settings'
'It took me sometimes, before I remembered the BYPASS_DBA_AUTHORIZATION modif to do in the registry'...

"Only Bad Coders Code Badly In Perl" (OBC2BIP)