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: Job Titles for TechComm People From:DURL <durl -at- BUFFNET -dot- NET> Date:Fri, 13 Feb 1998 09:41:57 -0500
Are you serious about Utility Infielder? Or were you just seeing
if we were paying attention? <G>
The problem with job titles like those in your list are that they
don't convey any real information. If I say "I'm a writer," people can get
a mental picture of what I do. If I say "Documentation Consulting
Specialist", heaven only knows what they think.
Maybe titles, like manuals, need to be considered in terms of what
you want them to do for you in a particular audience. Inhouse, "Project
Manager" might press all kinds of buttons having to do with pecking order.
To outsiders, or even inside a different company it might be code for
Mary Durlak Erie Documentation Inc.
East Aurora, New York (near Buffalo)
durl -at- buffnet -dot- net