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.
John Posada wrote:
> Besides, how thorough a review is needed? Reading a
> page or two of each type of document and looking at a
> few figures out to tell you if the person knows what
> they are doing.
Exactly. When I review a candidate's portfolio, it's about
getting the candidate to talk about the work. Even if I
were to read the manual from cover to cover, I wouldn't be
getting the insight on how this manual almost never went to
print because the writer couldn't get the SME's time (and
how did that get resolved?), or how the writer has a
particular favorite section of the manual that was written
in a trance (which section would that be?).
The point is that it's -far- more valuable to have a
dialogue with the candidate about the sample than it is to
actually -read- the book. After all, isn't there more to
being a good technical writer than how well we write? I'd
like my hires to convince me that they know how to deal
with the pressures of deadlines, SMEs who won't talk,
products that keep changing, etc., none of which can be
magically inferred on my own from reading.
- Kate O'
getting ready for more interviewing soon