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: Yet another title I found: "Content Designer" From:John G <john -at- garisons -dot- com> To:Amitha <aarakka -at- ncsu -dot- edu> Date:Fri, 5 Sep 2014 10:17:17 -0400
Sure beats Font Fondler ...
I've had lots of titles, and I prefer the basics. Right now I'm Lead
Technical Communicator which is just fine. Right up there with Lead
Technical Writer.
I don't go so much for the esoteric or exotic. And I really don't like
Roman numerals (Technical Writer II e,g,).
More telling than a single title is the "ladder" of titles -- from
Associate (better than Junior) Technical Writer up to Principal (or
Consulting) Technical Writer.
Associate TW --> TW --> Senior TW --> Lead TW --> Principal TW
What does your company's ladder look like?
On Fri, Sep 5, 2014 at 9:34 AM, Amitha <aarakka -at- ncsu -dot- edu> wrote:
> Cool. I've worked in an organization that called us "information
> engineers."
> -Amitha
>
>
>
> > On Sep 5, 2014, at 9:21, "Cardimon, Craig" <ccardimon -at- M-S-G -dot- com> wrote:
> >
> > I came across an ad for "Content Designers" that had the phrase
> "technical writers" in parentheses.
> >
> > Cool. I had no idea I was a "content designer," too. I'm happy being a
> technical writer.
> >
> >
> >
> >
> > Cordially,
> > Craig Cardimon
> > Technical Writer
> >
> > Information contained in this e-mail transmission is privileged and
> confidential. If you are not the intended recipient of this email, do not
> read, distribute or reproduce this transmission (including any
> attachments). If you have received this e-mail in error, please immediately
> notify the sender by telephone or email reply.
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Read about how Georgia System Operation Corporation improved teamwork,
> communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > You are currently subscribed to TECHWR-L as aarakka -at- ncsu -dot- edu -dot-
> >
> > To unsubscribe send a blank email to
> > techwr-l-leave -at- lists -dot- techwr-l -dot- com
> >
> >
> > Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
> > http://www.techwhirl.com/email-discussion-groups/ for more resources
> and info.
> >
> > Looking for articles on Technical Communications? Head over to our
> online magazine at http://techwhirl.com
> >
> > Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Read about how Georgia System Operation Corporation improved teamwork,
> communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as vwritert -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l