<p>I have recently decided on pursuing technical writing as a career. I would like to know more about this career from someone who has experience with it. What major is good for an aspiring technical writer? Is there any way to get into a specific field of technical writing such as writing for pharmaceutical companies or writing psychology reports? I am trying to find other areas in technical writing to keep my options open as well.</p>
<p>Do you think technical writing is in high demand? How do you feel about the career in general?</p>
<p>I'm pretty familiar with the field as it applies to computer systems, software applications, electronic components, etc.. </p>
<p>The major isn't terribly important although if someone has a science/engineering major and is a good writer and wants to be a TW, it should give them an edge. I think most engineering majors, even if capable of writing well, wouldn't want to become a TW. The major does NOT need to be an English or journalism type of major. The key is to be able to do technical writing well. This is different than writing a novel. </p>
<p>They need to have a good command of English grammar, punctuation, and spelling. Importantly, they need to have the ability to grasp the context of the document they're writing from a technical perspective - i.e. they need to be able to understand to a limited extent the subject they're writing the doc about. This doesn't mean they need to be experts since they're not the actual engineers, but they need to be able to put into a doc what the engineers disseminate. They also will sometimes write a doc based on operating the item themselves.</p>
<p>I can't speak to the demand of TWs but almost everything of a technical nature requires them. If the TWs don't do the writing then the engineers have to do it and that's a waste of engineering resources plus many engineers would be incapable of writing well. As more items are produced in other countries, many of their docs need to have native English speaking TWs produce the English version of the docs.</p>
<p>TWs can earn some pretty decent money. They can also have fairly flexible positions - sometimes working partially from a home office. However, they can also sometimes be working contracts where they'll work on a project for a while but once the project's launched, move onto another contract. For some this means working on a variety of interesting and sometimes lucrative contracts but for others it means some time between contracts. Of course, there are many companies who employ TWs as regular positions in a TW department.</p>
<p>My brother is a technical writer. He did not set out to be one. His major was Technical Illustration. He was a commercial artist for many years. He fell into technical writing about 10 yrs ago. He has worked in the aerospace industry since graduating from college 30+ yrs ago. He seems to have no problem finding work though the last two jobs have been contract positions which do not give health benefits. In the 30 yrs he has worked in his field he has seen most of the writing and illustration jobs go to contract positons. His wife fortunately works in Health Care Management so he has benefits through her employer.
Adding- after reading UCLA Dad's reply. My brother has in the last two years has had a contract to do writing through Boeing for the military. The job also involves supervision of the actual work being done.</p>
<p>The kind of work you're talking about is usually referred to as "science writing" or "medical writing" (in the case of pharmaceutical companies), rather than "technical writing," which usually refers to writing connected with computers or engineering.</p>
<p>The big bucks are at the pharmaceutical companies, but generally you have to have an advanced degree (in many cases, a doctorate) to even get in the door. </p>
<p>I'm a science writer/editor, but I can't give you a lot of guidance because I sort of drifted into the work after a more laboratory-oriented career did not work out. I like the work because it is interesting and varied, although not particularly well-paying (unfortunately, I do not have the credentials to work for a pharmaceutical company), and because it is relatively easy for experienced science writers and editors to find part-time or freelance opportunities -- something that worked out very well for me when my children were young. Also, I am naturally picky and detail-oriented (some would say bordering on obsessive-compulsive), so the work is a good match for my personality.</p>
<p>It might also be a good idea to discuss your interest in this career with the counselors at your college's career center. They may have some good ideas for you.</p>
<p>For several years I worked as a TW in the aerospace industry -- mechanical and fluid devices mainly. I had an engineering background and was (am) good at fixing things. Also my writing style was very direct at that time, and that's a good thing when doing TW. Being able to converse with engineers was important, as was understanding how readers would use the manuals. As previous posters have indicated, it's a REALLY nice job for someone with the right skills and personality.</p>
<p>I used to be a technical writer, and at one point was the manager of technical publications at a large software company.</p>
<p>Technical writing ranges from very interesting to deadly dull, largely depending on the industry. Banks, for example, employ technical writers to document their internal systems because it is legally required. Those writers are pure overhead, and the work they do is neither crucial to the corporate mission nor likely to actually be <em>used</em> much by the end users. On the other hand, in the software world, the work tech writers do is part of the product--printed user guides, help facilities, marketing materials--and tech writers are the link between the engineers and the end users. Engineers tend to forget that when the end user opens up the product they will not have an engineer sitting at their elbow to explain why certain design choices were made, or how or when one should use various features of the product. Features are often included in a product in order to get a large sale, and they must be documented even though very few will ever use them. (Hence the popularity of after-market user guides: the author is free to present the most commonly useful ways to actually do things with the software, and ignore features and functionality that clutter up the picture.) Very few programmers actually approach the product from the user point of view: they have a tendency to enjoy writing elegant code more than producing a product that performs a needed function in a straightforward way. The technical writer can not only present the product to the end user, but in some cases present the end user's needs to the programmers. </p>
<p>I could go on about the ins and outs of technical writing forever, but to me the major plus is that if you are employed in the right sort of industry you are part of an extremely interesting environment of bright, well-educated people who enjoy learning, and constant learning is an integral part of your job. What you need most is the ability to learn quickly, present information logically (ideally both verbally and visually), and communicate effectively with all kinds of people. </p>
<p>In my experience, pure brains, comfort with technology, natural curiosity, and a degree in some writing-heavy subject are the hallmarks of a good technical writing candidate.</p>