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: Not Sure From:"Diane Evans" <diane_evans -at- hotmail -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Fri, 15 Aug 2003 08:09:54 -0700
OK, time for my two cents worth...
I consider myself a technical commuications generalist. My current job
description is similar to www.salary.com's definition of a documentation
specialist :
"Prepares and/or maintains documentation pertaining to programming, systems
operation and user documentation. Translates business specifications into
user documentation. Plans, writes, and maintains systems and user support
documentation efforts, including online help screen. May require an
associate's degree in a related area and 3-5 years of experience in the
field or in a related area. Familiar with a variety of the field's concepts,
practices, and procedures. Relies on experience and judgment to plan and
accomplish goals. Performs a variety of complicated tasks. May lead and
direct the work of others. Typically reports to a manager. A wide degree of
creativity and latitude is expected."
On the other hand, I have written everything from API/SDKs to marketing
material. There is hardly a phase of technical writing I haven't done at
some time to another.
Would I be vague in a job interview? Definitely not. I would research what
the company was looking for, and bring a portfolio to the interview that is
tailored for that job description. A person who is vague at interview time
("I can do anything, just let me try...") is most likely hiding something.