TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Should I Say Something? From:"Comeau, Lisa" <Lisa -dot- Comeau -at- MOH -dot- GOV -dot- ON -dot- CA> Date:Mon, 17 May 1999 12:30:44 -0400
"If the reason for showing the sample was to evaluate how the person being
interviewed reacted, he/she would have been informed as such."
>Generally, they WOULDN'T be told unless they were specifically being asked
for their input. (Go ahead, ask me why...)
"If it was part of the evaluation, he/she wouldn't have had to ask for the
sample. it would have been presented as part of
"Sure...it might have been part of some grand convoluted plot by the company
doing the interview."
> I've seen much more convoluted plots - especially in the sales game...
"You are there for one reason and one reason only...to get the job. if it
won't increase your odds, don't do it."
>Absolutely CORRECT! Give the man a biscuit! That's the point, if you don't
think it'll help your chances, leave well enough alone! Most of us are not
stupid, we can tell right away if it's a conspiracy or an interview, and
most of us wouldn't want to work for a company that engineers big silly
tests, but be aware that they exist, and do what you need to do to get the
Still cranky, but slowly reentering the human race...