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.
Let's move this topic on to a discussion of what would make a good test. A
company that I have worked for would ask candidates to write a procedure
for changing the time and date on a Windows 95 PC. The writer would have
one hour to complete the task. The candidate was told to assume nothing.
The interviewer was the subject matter expert. A PC was provided with
Windows 95 and the word processing/page layout application used by the
company. The interviewer would observe the process and look for things
like:
1) Did the candidate ask for a style guide or a sample ?
2) Did the candidate ask any questions about the audience he was writing for ?
3) Did the candidate complete the task in a timely manner?
4) Did the candidate look comfortable using the tools provided?
5) Were the procedures complete?
etc.
Although this form of testing is a bit time consuming, it does tend to weed
out some undesirable candidates. As I told a former coworker of mine, one
candidate started looking on the back of the PC for a knob to turn to
change the time!
Any other ideas for a good and quick test of technical writing skills?
Roger
>On 9 Dec 1996 14:11:07 -0600, you wrote:
>>I know some people hate this, and I don't mean to start a flamewar,
>>but a well-designed writing test can really go a long way toward
>>determining ability. Have your candidates rework a poorly worded and
>>designed technical document (no more than a page long), have them
>>describe, in writing, how they approach a new writing project, or
>>something else that can help them show you all of their abilities (of
>>course, have them do this in the DTP or WP of your choice, so that
>>they can do a little design and formatting).
>Yes. But "well designed." Most of them aren't. When I've been asked to
>take a test, it never, never told them a darned thing about my
>abilities as a tech writer or editor. I always felt dejected and dumb,
>which I'm not.
>For instance, about a year ago a company gave me a short test that
>asked me to write a sentence in active and passive voice. They didn't
>learn much more about me than Beth threw the ball and the ball was
>thrown by Beth. Beth.