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.
Just a quick comment on this thread. In California, at least, if you give
any testing to one applicant, you have to give it to ALL applicants, or you
open yourself up to lawsuits (this IS California...). This hit me when I'd
started at CNET as a contractor (since converted to full-time). After three
months contracting, HR called me in to do a writing test. It was a short,
basic, "Write a few procedures" test. They've since discontinued the testing
across the board.
In my experience, you can learn more about a person's skill by direct
questioning and walking the candidate through scenarios.
Stephen Arrants
CNET: The Computer Network
Documentation and Training
stevea -at- cnet -dot- com
415.395.7805 x4766