User MArk B. (MMcNaughton@STSSystems.com.nospam) posted:
Personally i would ask them to script something. Something reasonable of
course, indicating that commenting, style is as important as the script
working. I wouldn't want an uncommunicative interviewee to have his
scripting skills go unnoticed...
Here's some MarkB wisdom as well:
Subject: Re: Interview process and/or questions
From: "MArk B." <firstname.lastname@example.org>
Date: Mon, 6 Mar 2000 09:40:00 -0800
One question I like is: "How much of an application do you expect to get
Wrong answer: 100% (or the like)
Possible correct answers are all < 100% and come with a reason.
Another one: "You are given an application to test you know nothing about
and have three weeks to test it. What do you do first?"
Wrong answer: All of them. Applicant should just leave the interview without
answering. (But should be polite on the way out.)
The only criteria for a successful answer to this question is that includes
something about polishing up the résumé.
Editing trick. Getting the little "what ever they're called things" above
the "e's" in résumé is difficult to do on a word processor unless you know
this trick. Spell it wrong, something like 'resuma', and then pick the right
one from the list when the spell checker catches it.
I'd ask them to bring a sample of their work and have them explain what it
does and how it works, line by line. If they do a good job, it indicates
they probably wrote it, and can communicate technical concepts well.
Check the sample(s) for readability, useful comments (and neatness if
anyone else will ever have to deal with their scripts). I'd also check
for modularity/re-use (is every line of code in the script, or do they
have libraries of re-usable subs/funs?). I might hire someone who doesn't
understand the benefits code re-use IF I thought that they could/would
pick it up.
I'd also try to deduce how well they analyze a complex application and
create useful test cases.
If the job is going to include creating req., test cases, etc., my favorite question is (while holding up a pencil) "Tell me some requirements that were put into this pencil." "Tell me a list of defects this pencil would produce."
If you are not familiar with automated scripting yourself you might want to have someone in the interview with you that does. So at least that person can let you know it the interviewee knows what they are talking about