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.
Re: What constitutes a senior tech writer and how to get there?
Subject:Re: What constitutes a senior tech writer and how to get there? From:Kevin McGowan <mcgowan -at- LORAN -dot- COM> Date:Fri, 30 Jul 1999 12:23:35 -0400
Let the games begin.
If a writer has been on a project(s) for over three years, and still has not
developed the necessary skills to do the job, I would say the writer is not
qualified to be a senior.
Yes, experience in the best teacher. The fact is this: if this person has
sat in a chair doing almost nothing for two years, and then only some actual
work for one year, this person is pretty darn lazy. too lazy to take the
opportunity to come up with projects on his/her own, too lazy to say "this
sucks, I'm getting another job." If you're not growing in a particular job,
it's time to find a new one.
While the manager has responsibility to train and mentor a junior writer,
the real world dictates that most managers have too much to do. It is up to
the writer to do this on his/her own, through research, associations (STC)
and a little effort.
This person might find themselves with a layoff notice, and be stuck with no
skills and no prospects.
Imagine this interview:
"So, Mr/Ms X, what were your responsibilities at your last technical writing
job?"
"Well, they never gave me anything to do, so I sat there for three years
surfing the internet."
"Uh-huh. We'll be in touch."
Just my two cents on a Friday.
-Kevin
> -----Original Message-----
> From: Technical Writers List; for all Technical Communication issues
> [mailto:TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU]On Behalf Of Anonymous Poster
> Sent: Friday, July 30, 1999 12:08 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: FWD: What constitutes a senior tech writer and how to get
> there?
>
>
> ANON>> Brief background: Two writers in a group, each with 7-8
> years of experience,
> ANON>> plus tech writing degrees. Three years ago, a third writer
> is asked to join
> ANON>> the group, but has no experience, no education, no
> training. Spends the
> ANON>> first year with virtually no projects, and nothing to do
> beyond proofreading
> ANON>> projects for the other writers. Second year, third writer
> is given a few
> ANON>> simple projects, which are completed to the best of the
> writer's limited
> ANON>> capabilities. At review time, writer is soundly criticized
> for doing a
> ANON>> "lousy" job with the projects. Group manager says he will
> spend more time
> ANON>> "training" new writer, but ends up being "too busy" to
> help beyond taking
> ANON>> the red pen to the new writer's work. Third year, new
> writer is given a few
> ANON>> projects to do from scratch, which seem to be going ok. At
> review time,
> ANON>> writer is again criticized for not developing the skills
> and technical
> ANON>> expertise needed to be considered a senior writer.
> ANON>>
> ANON>> The question is this: what kind of skills and experience
> does one need to be
> ANON>> considered a senior writer? What kind of training,
> seminars, books, would
> ANON>> help? Is experience the best teacher? How can one learn
> new things if one is
> ANON>> not assigned projects that make one grow?
> ANON>>
> ANON>> Any opinions, facts, and advice are welcome.
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Forwarded anonymously on request. If you want the
> original poster to see your response, you must reply
> to the TECHWR-L list. All direct replies to this
> message are automatically discarded. Contact Eric
> ejray -at- raycomm -dot- com with questions.
>
>
> ==================================================================
> =========
>
>
>