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.
My company is just moving into the Software Development arena. For
proposal purposes, I am trying to create a "blurb," which describes each
team member's respective roles and responsibilities in terms of
application development initiatives. Obviously, these roles will
change/evolve over time AND depending on the project. However, I am
presently trying to think of all of the POSSIBLE ways in which a
technical writer could/would contribute to a software development
project. Below is the "blurb" that I've come up with so far. I'm
looking for ways to improve/expand it. Technical Writers with this kind
of experience... what do you think?
Thanks in advance!
The Technical Writer will be responsible for interviewing SMEs (subject
matter experts) and conducting QA testing for the product. Using the
software itself, client specifications, and any user and engineer
requirements as a guide, the Technical Writer will also be responsible
for creating and/or contributing to the creation of on-line help files
and user manuals. If training is involved, the Technical Writer will
work with our Certified Instructors to develop customized courseware for
the new applications.
Gina Hertel
Technical Writer
Alpha Technologies, Inc.
ghertel -at- alpha88 -dot- com
(732) 980-1800 Ext.749
