Answer to Scott: How to be a Tech Writer

Subject: Answer to Scott: How to be a Tech Writer
From: "Belef, Mike" <MBelef -at- OS -dot- VARIAN -dot- COM>
Date: Thu, 1 Jun 1995 13:42:00 PDT

Scott asked a bunch of questions about becoming a Tech Writer. I will
attempt to answer them in order: to save space I won't retype the questions.

Of course, "being mechanically minded" helps. Software writing requires a
bit of extra ability to comprehend and communicate concepts.

Some technical writing training is essential. I had three years of college
German and Journalism when I explored technical writing. With all that
training, my San Jose State University editing course was still very
difficult: I found I had a lot to learn about writing! I consider that
class to be the most important training I've received. It is good that San
Jose State engineering students are required to take that class.

Since you mentioned San Jose State...
San Jose State's Technical Writing program is superb. The program director
is Dr. Lois Rew.
De Anza College also has an excellent program. The program director is Dr.
Donna Dowdney.
University of California at Santa Cruz Extension, in Santa Clara, has a
strong program that targets experienced tech pubs people. The program
director is Shirley Krestas, PhD.

I have participated in all three of these programs and completed the De Anza
and UC Santa Cruz certificate programs.

All of these programs help foster career changes by promoting their
students, through internships and close work with the Society for Technical
Communication (STC). I think that more than half of De Anza College tech
writing students are changing careers and are over 30. It's never too late
to make that kind of change: it depends on your priorities. (My martial
arts teacher is 84 and he says that he is still learning and changing).

I've met competent technical writers from every imaginable occupation
including: mothers who never worked outside the home, engineers, security
guards, and real estate agents.

Silicon Valley is definitely a "hot bed" of technical writing but you can
find writers everywhere.
It's a particularly good career for working out of the home, but it may be
best to work for full time for a company first. Wages for technical writers
varies, a lot. I guess the salary range in this area to be: $35,000 -
$70,000 per year depending on experience. There are also people working
above and below those figures. Keep in mind that the cost of living here is
high.

Positives: growing field, many "alternative" career paths, decent salary,
helping others understand technology, being an "advocate" for "the user,"
being involved in interesting technologies, lots of choices in types of
companies and types of work, working with all sorts of people, and a smug
knowledge that you can "read between the lines"

Negatives: Many managers, engineers, and other professionals do not
understand the role and value of technical writers. It can seem a thankless
job. It can be tedious work. The field changes as fast as technology (this
can be fun and interesting or exhausting). It seems that writers are asked
to do more every year. You may have to battle the writer's curse,
unconsciously editing everything you read. (Beer helps me, but I live in the
US). I think most of the negatives are relative to the company you keep: if
the negatives outweigh the positives, it's time to find a more positive
position.

Writers do much more than write. Their responsibilities depend on the
company or contract. Tasks include: interviewing experts, formatting
documents and electronic media, editing, performing usability surveys and
interviews, testing products, estimating and scheduling projects - the list
goes on. Technical communication media includes paper, CD-ROM, video, and
other electronic media like online help and the internet.

Some writers are very specialized and work in a specific industry most of
their careers. Other writers "do it all." You should join the Society for
Technical Communication (STC) to learn more about the field and to meet
other technical publications professionals. The STC has many "stem" groups
or Special Interest Groups (SIGs) that can help you learn about specific
industries, technologies, and career paths within the technical
communications field.

By the way, I've seen an ad for technical writers in Saudi Arabia in the
national STC newsletter, Intercom. Perhaps you will need more technical
writing experience, but you obviously have excellent experience in Saudi
Arabia.

Summary: If you're interested, join the STC. Keep asking questions. Start
honing your editing skills (I found that the fastest way to improve my
writing skills). Get experience by working on a project like a technical
paper, tutorial, or technical communications related project. Be sure to
solicit regular evaluation of your work from communications professionals.
You can get you feet wet by editing this email for punctuation, grammar,
style, and usability... ...but I'm not responsible for any factual
variances.

P.S. I can provide addresses for STC and colleges if you need them (but
I'll have to get them from home).

P.P.S. to all interested in politically correct language: I heard a
hilarious, interesting presentation with question and answer session on
National Public Radio (NPR), yesterday, 5-31-95. The speaker's last name
was Cerf (or Serf, Surf...). The talk was sponsored by the Chatuaqua
Institution in New York as part of a series recorded in Summer 1994: a tape
is available for $10.oo. The speaker co-authored a politically correct
dictionary. The talk should be played and discussed in every writing class
(and every group that has to deal with social change)!

FROM: Mbelef -at- varian -dot- com


Previous by Author: Re: help! online help tools for
Next by Author: Win95 and WinHelp Buttons - Problem
Previous by Thread: Re: Origin of phonetic alphabet
Next by Thread: Re: Arguments not to use


What this post helpful? Share it with friends and colleagues:


Sponsored Ads