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: new title: Information Developer From:Misti Anslin Tucker <matucker -at- MMM -dot- COM> Date:Wed, 6 Jan 1999 20:19:19 -0500
Is there any reason not to list on your resume what you actually *did* on a
job rather than the title a specific company gives that job?
Titles change from place to place and year to year, but the industry
standard is to call ourselves "technical writers". I've always considered
it to be "writing to my audience" to use the industry standard rather than
the company specific title on my resume.
Now I'm wondering...
Misti Tucker
matucker -at- mmm -dot- com
I interview and hire a fair number of technical writers and editors. I'm
always a little sceptical when a resume with a title like Information
Developer or Content Specialist crosses my desk. I know it means I'm going
have to spend some time in a pre-interview screen, determining whether you
are a writer or an editor. That's an extra step that I'd rather not take.
It's fair to say that your skillset includes information
development--that's
something I'd find interesting. But you might do that primarily as an
editor
or primarily as a writer, and that's a key distinction.