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.
As a manager, I've never given a writing test, and don't think I'm inclined
to unless one or more of the following situations exist:
1) Testing is required by HR
...in which case, I'd first try to adjust the policy, second ask that the
testing occur very late in the selection process (see situation 2, below),
and finally ask to help construct the test so that it actually asks
something reasonably relevant. (The last HR-required test I took had so
little relevance to the job of a TW that it was truly a waste of my time.)
2) After interviews, samples, and reference-checks, I'd narrowed the field
down to two or three candidates, none of whom was the clear choice because
of differing skillsets
...in which case, I would follow the test format that has twice been
provided to me: give the candidates some source material about a
product/concept used in-house, ask them to create a sample document (user
guide, brochure, etc., based again on the job they've applied for), and give
them a couple of days (i.e., until the next interview) to do it.
This method allows the candidate to not have to work under a microscope, and
to use whatever tools they are most comfortable with. (Note: if they do not
have access to resources at home, on-site workspace should be made
available.) It allows me to evaluate candidates I'm already comfortable
with on something closer to a level field - candidate samples are usually
wildly different.
This type of test, in my experience, usually comes with instructions like
this:
"Here are some samples of the type of source material you'll be working
with. For this exercise, assume that it's complete and correct. If you
have questions about any of the information, feel free to call me. Create a
User Guide. Include anything you think should be in the document."
I put together a little booklet, complete with full front matter, TOC, a
brief index & glossary, and about three pages of content (concept,
instructions, clip-art graphics, etc.) based on the material they gave me.
I later learned that my competitor (who had been given exactly the same
assignment) had created a one-page list of steps to showcase his skills.
I got the job.
Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
