Whether you're attempting to become a technical writer at 21 or 41, the steps are the same. Statistics show that the best way to find a job is network, network, network. Go to association meetings, like STC (Society for Technical Communication) (www.stc-va.org/home.html) (International Office: 703.522.4114; Email: stc@stc-va.org) and talk to as many people as you can. Introduce yourself and tell them honestly what you want. Ask them a lot of questions about how they did it. Everyone started somewhere.
Find out which companies tend to hire the more junior or intern writers or editors/proofreaders. Ask each person you speak to for another referral. You're looking for direct job leads or information that could lead you to a job. Look at it as solving a mystery. Just keep talking to people. Even once you begin calling companies direct, ask for other leads. People have friends who have moved on to other companies.
Identify which companies you'd ideally like to work for by going to the library, going online or using one of many other resources, such as Hoover's Database (www.hoovers.com) or Thomas Register (www.thomasregister.com) or CorpTech (www.corptech.com) or Red Herring Magazine (www.redherring.com). Also online you can find ComputerWorld, PC World, PC Week, and much more. If you like the idea of a startup, the venture capital firms usually post their investments on their websites. Once you've identified ten or twenty companies that you like, start approaching them. Find out if they have a pre-recorded job hotline. Go to corporate open houses by contacting the human resources departments. Go to career faires (usually advertised in local newspapers and on local radio shows) and corporate open houses.
Try to get informational interviews from your A list of companies. Find out what it takes to become a technical writer in each company, when they will be hiring , and what qualifications they look for in a potential technical writer/editor. Quite often the informational interview "accidentally" turns into a job offer. Offer to intern for three to six months, a technique that many writers use very successfully. Once you're inside a company, quite often you end up getting an offer there. You'll get the experience you need and will meet people that could hire you later, if not now.
Before you contact a hiring manager, it is critical to assess your skills. The major key to marketing yourself is knowing what you know. Companies hire for product knowledge. It's easier and faster to become productive if you already have knowledge of a particular topic. The most popular "competitive" skills that win the confidence of publications managers are the following: Web, HTML, multimedia, Windows online help systems, GUI (graphical user interface), other end user topics, such as accounting or biomedical, and a desktop publishing tool, especially FrameMaker.
In addition, programming background is one of the hottest skills around for writers. If you have any programming background, capitalize on it. Programming languages like object-oriented C++, C, Pascal, Assembler coupled with the ability to write will open many doors for you. It means you know how to communicate with developers. Internet-related application development tools, API (application programmer interface), relational database engine, object-oriented development or network management software, such as IP routing protocol, tools are all sizzling topics today.
Ability to get along with all types of people is another unique skill, believe it or not. The way to establish that talent is with letters of recommendation and/or references. Willingness to fit in, chemistry, and corporate culture are unspoken truths about working for any company. You can have every skill in the book, but if you are difficult to get along with you won't last ninety days. Part of a writer's job includes coordinating with others, like users, developers, and managers, and getting their participation. You, the writer, have to orchestrate everyone's diverse needs. Hiring managers tell me that fitting in is equally as important as writing ability.
Whatever your background, play it up. Even if you've done something that doesn't seem relevant, look for the relevant parts. If you've worked with the public, for example, or taught or trained in a school or corporation, you had to communicate. Bank on whatever talents you have.
To prove yourself, offer to make over a poorly written and/or designed manual. Managers love this because it shows you are serious - you are making the effort to enhance an existing product with your own work. It is also one of the best ways to get experience putting together a user manual if you haven't actually done so.
Take a few technical writing classes or obtain a certificate. There are several programs usually listed at the STC site under the "Education" link. Some schools to contact in the SF Bay Area are San Jose State, De Anza College Tech Writing program, and UC Extension, among others.
Dr. David McMurrey is an excellent resource for anyone wanting to break into Technical Writing. He offers online as well as face-to-face classes and can be found at www.io.com/~hcexres/ or hcexres@io.com or (512) 223-4804 .
Three other experts in the field of technical communication, JoAnn Hackos, William Horton, and Henry Korman, lead a series of seminars for technical communicators via a company called Seminars in Usable Design. You can contact them at 710 Kipling St., Ste. 400, Denver, CO 80215; 303/234-0123 . For more information about any technical wiritng seminars or programs, contact an STC Education Manager.
There are several good books on the subject: Writing Effective Software Documentation, by Patricia A. Williams/Pamela S. Beason, Writing Better Computer User Documentation by R. John Brockmann, How to Communicate Technical Information by Jonathan Price and Henry Korman, and Designing and Writing Online Documentation by William (Bill) Horton.
Once you've decided you want to pursue technical writing, go for it. Find out what it takes and do it. Persistence will make you a winner.
© Copyright 2009 Micro Search. All Rights Reserved.
Look for Janice's new book coming soon about job search and navigating corporate websites. She is accepting
requests for job search advice as research for her book. Your privacy will be protected. Email her
at jlitvin@microsearchsf.com to be considered.
|
|