Technical Writers in the Industry?

kungfooswade asks: "I am getting ready to graduate soon with my CS degree but I want to hedge my bets on finding a job and will be starting a masters degree, as soon as I am done. I am considering a masters in professional writing, so I can be qualified for technical writing positions, or just going back for a masters in CS. I am curious about the following: (1) what are the general opinions of programmers on technical writers; (2) is there someone out there who has first-hand experience in technical writing who can tell me about the work and their experiences; (3) what software is used mainly in the process; and of course (4) what seems to be the average pay? I would like to diversify my education, so that I won't be searching very long if layoffs come around. All comments and suggestions are appreciated."

Comments

API Techcnial Writer

[szucker]

Since you know how to program with your big phat CS degree, what you want to do is become what is known as an "API Technical Writer." You will make a lot more money than us people who write "point here, click there" type manuals. And I think you will be able to find a job even now because there are not a lot of writers you are bona fide programmers.

Not enough of them

[Anonymous Coward]

Although I've only been in industry for about 5 years, from what I've seen there are far too few qualified technical writers. I've never seen one myself. They've always either not really known what they were talking about or there was nobody at all to write the stuff and a programmer was forced to do it.
I don't know if companies try to make due without them, or if they are just really hard to find. All I can really say is that every company I've worked for has needed one, and none of them had them.

Technical Writing....

[axoi]

Having worked in the industry for over 12 years, and that working with a group of professional technical writers ( all with master degrees in writting) I can tell you that most of it is pure druggery. If you like rewritting the same paragraphs over and over and then only rewritting someone elses copy over and over should you consider going that route. Why not put your energy into something like research into new computer fields such as human-computer interaction or robotics. It would seem a waste of your talent to use those skills on something like writting documents. I admire those that can sit and write the same documents again and again..but only because of the sheer determination of staying awake. All of the writers I have worked with ( which counts over 12 people...some from JPL ) really don't like doing it that much.

Remember that your time here is limited and you should find something that you really like to do. Then be the best that you can be at it. I prefer writting software and user interfaces...why? because after all these years I find that I like helping people to use computers easily. I didn't find this out overnight. Neither will you. I wish you luck and good fortune.

Does it Matter?

[orbbro]

I just finished getting an AS degree in CS, and I added on a certificate in professional writing, figuring, like you do, that I could leverage my background as a writer and offer diverse skills to a potential employer.

What I learned from writers in the industry who came to talk to our classes:

1. "Technical Writing" is now more appropriately called "Technical Communication" and includes, beyond the stereotypical software manual: business & marketing communication ("marcomm"), information design, corporate training & curriculum development, online communications, single-sourcing (think XML!), and even, by some definitions, web design. See the Society for Technical Communication for more info.
2. If you want to succeed in the world of private industry with a "soft subject" degree such as tech/professional writing, you should take a handful of writing classes to brush up on your skills, but skip the MS degree and get an MBA. Most job titles like "technical writer" are being phased out for titles like "project manager" or "business analyst." In short, your writing skills are going to be put to use secondary to your people management and other "soft" skills.
3. Tech writing in the tech fields -- engineering & CS -- is being outsourced and shipped overseas just like the tech jobs. You might be better off learning Chinese, Hindi, or Russian if you want to do serious tech writing for IT in the next decade. That's where all the "how to use your cell phone/PDA/laptop books are being written. Red Flag Linux HOWTOs, anyone?
4. The job market for tech writers is almost worse than that for high tech, because tech writing for IT is dependant on the success of IT companies. When you're an IT company that's on the ropes, the first thing you forego in getting the next product to market is high-quality documentation (if you were planning to use it in the first place). Half of the ~600 self-identified tech writers in the Portland, OR area are currently un- or under-employed in this market. Yes kids, that's 50%.
5. Salary: While the bestest writers can command near 6-figure salaries or more, they're working 60-80 hours per week, just like the IT people with those salaries. Writing has a lot in common with coding, in a way -- lots of prelim. design and planning, lots of computer time, and lots of "debugging" (except it's called revision). And there are few if any shortcuts to making a good end product.
6. Tools: because you asked. RoboHelp, Adobe FrameMaker, and, sad as it is, MS Word, are the main tools for the job. Knowing XML, HTML, Dreamweaver, Flash, and the like can also be helpful, depending -- this field is as specialized as the computer world. The technologies you know define your job. For more ideas, check out the trainings offered at a local tech. comm. consulting firm.

So, the bottom line is:

You may have as much trouble getting a tech writing job as a newly-minted coder would; your job might be as specialized and ever-changing as a coder's job; you're better off with an MBA; your job might be sent overseas; and, instead of using your favorite IDE, you might get to use Word, instead. ;-)

Oh, and I forgot: because there are fewer of them, and their role is often misunderstood, you will possibly be less appreciated than the programmers.

Have fun!

-->orbbro.