Written Tests for Interviews?
University Tech asks: "I am a technician
at a small private university in the process of hiring a new technician. Everything here is done by committee. One of the committee members was very offended that we were giving the interviewees a written test after we had finished the oral part of the interview.
How many of you have had written tests as part of a job interview? I think I have had one at every tech job interview I have ever had (six interviews) and even two hands on tests. Most of my co-workers and friends have as well. Is this perhaps a regional thing or is this normal for us techies?"
It generally works pretty well in assessing competence levels, but a lot of applicants have noted problems getting acclimated to our configurations. Written tests can't tell what a person can do in the computer chair.
It is extreme. Your company would have to be pretty special for me to be willing to go to that much trouble. Remember, since I already have a job I have to take time off every time I go to meet with you. For two interviews that adds up to two half-days depending on how flexible your interview times are. Add a full day for this ropes course and my current employer is going to start to get suspicious. Not to mention those are vacation days that I'd rather spend with my other team (i.e. my family).
in the Linux Administration Handbook ISBN 0-13-008466-2
. htmll
;-), but wouldn't find them offputting if i did.
pp851-852 talk about just such interview tests.
they also refer to these online samples:
http://www.admin.com/Pages/SkillTestOne
http://www.admin.com/Pages/SkillTestTwo.htm
personally, i've not had written tests, only oral (as the Nun said to the Bishop
hth,
olly.
Our rationale was that we would discuss experience during an interview, but too often during tech interviews, someone would be asked questions such as "What would you do if the system came up with error xxx?" That isn't representative of the work environment.
So, we sent a series of questions, letting the person know they had a few days to work on it and that they should use whatever resources they could. That way, we could more directly test their ability to discover the answers to the problems they would face in the job.
Surprisingly, we often would find out more about the person's personality than their technical skill. Some wouldn't reply. Others grumbled. Others sat down and really researched the questions, answering with their own experience. It seemed in some cases, people would put on a happy face when they put on a suit, but when doing "homework," you got to see their true work attitude. Overall, I thought it was an effective measure of how much they would work on a problem and what skills they had to research a problem.
Later, in Wards Cove Packing Co. v. Antonio (1989), the Supreme Court reversed itself, saying that "business necessity" was a huge burden to prove.
Then, with the Civil Rights act of 1991, Congress reinstated the business necessity requirement, but courts have been a little uneven on how to apply the law.
Search on "disparate impact" if you want to see more.