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.
>Pro TechWriter wrote:
>>Brad Whittington wrote:
>>>James Barrow wrote:
>>>
>>>"In one paragraph (100 words or less) describe what should be included in
>>>a good documentation package, and explain why it would be good."
>>
>>I though of bio-med hardware too, immediately :-)
>>
>>Would the interviewee mind posting what type of documentation position he
>>was applying for?
[]
>
>My first thought was, "Documenting what?"
Good questions all. I am writing the end of my suspenseful story for the
list at the moment:^)
I didn't tell everyone what I would be documenting because I didn't know. I
was supposed to have my interview followed by the test. Due to schedule
conflicts, the order was reversed. And I didn't mention what sector or
industry the position was for because the job requirements are vanilla:
"Assist identifying user documentation needs. Draft, proof, edit, organize,
and disseminate technical documentation including technical processes,
manuals, and user guides in support of IT programs and services."
Identifying the industry/sector would have biased your answers considering
the fact that the things I would be documenting wouldn't have a one-to-one
correlation to that industry (it's difficult for me to explain).
For example, let's say that this job was for the Administrative Office of
the Courts. You would assume that the documentation would support court
clerks, judges, etc., but this is not the case. The documentation supports
(for lack of a better explanation) things that happen almost exclusively on
the back-end.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
