The demand for qualified technical writers is constantly growing. For every software application or technology product that's developed, there's an instant need for accompanying documentation. In a global market increasingly dependent on high-tech products and services, it's virtually guaranteed that technical writing opportunities will never run dry.
Technical writing may be your ideal field if: you love working with technology, but simply don't have the desire - or skill - to become an engineer or programmer; if you enjoy training people; if you want a stepping stone to a career in high-tech; or if you enjoy writing and are simply looking for a different way to use your craft.
If you've decided to give technical writing a try, but don't know where or how to start, keep reading! This three-step plan outlines the basic qualifications you'll need, how to learn the necessary skills, and how to make a successful foray into the field.
STEP 1: GETTING THE BASICS
Believe it or not, to be successful in technical writing, you don't need to already have a high level of technical know-how or a master's degree in English. However, you should have the following:
Basic technical skills.
Any experience in technical support, web design, networking, teaching, or even in helping your Mom set up her computer will be an asset. If you don't have a basic understanding of how computers and software work, take a class - almost every community college or education center in North America offers "Intro to Computers"-type courses.
Basic writing and grammar skills.
If you're already a writer, you probably won't have to worry about this one! However, understand that technical writing generally uses active rather than passive voice; the terminology used must be consistent throughout an entire document or document set; and the objective is to make procedures as simple as possible. These guidelines may be difficult for some creative writers to get used to.
An interest in technology.
It's not uncommon for a technical writer to spend hours poring over a half-completed software program, trying to find hidden commands or features that need documenting. You may also have to work extensively with engineers and programmers, who will rely on you for feedback and suggestions on the product's interface. So if you're less than enthused by the prospect of "getting your hands dirty" with technology, and working with very technical people, you probably won't enjoy this field.
STEP 2: EDUCATE THYSELF
If you have the basic qualifications for technical writing and are still interested in what the field has to offer, it's time to learn the basics of technical writing and the standard tools used.
