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: Interview & testing From:Gwen Thomas <thomasgp -at- CBS -dot- FISERV -dot- COM> Date:Thu, 11 Mar 1999 13:35:06 -0500
Here's an example of a very useful test I was once asked to take.
The company produces financial software. Green-screen, extremely traditional doc set. The test? One page of "re-write for clarity" sentences and a brief excerpt from a functional spec describing a new report, with instructions to provide an outline of how to doc the report, with issues and questions to SMEs in the margin.
They had stated up front that they were only interested in people with directly applicable experience. (They needed someone able to hit the ground running.) If the applicant didn't choose one of the several "standard" ways of organizing the doc, the chances of hitting the ground running were pretty slim. And the sample functional had some red flags, so the applicant's response could indicate SME-interaction skills.
