HOME | FAQ | PORTFOLIOS | CRITIQUE | RESUME | RESOURCES
This page answers the most common questions people have about technical communication. This is by no means a comprehensive list of questions or answers, but it offers the basic information you need to get started in the industry. If you have additional questions, check out some of the technical communication Web sites on the Links page.
Technical writing falls under the broader category of technical communication, which encompasses technical writing, editing, and design. Technical communicators organize, interpret, write, and edit scientific and technical material, gathering information of a technical nature and presenting it to those who need it. Many different professionals fall under the broad category of "technical communicator." Technical Writer is the most commonly used job title for this occupation. Other titles include:
|
|
|
|
|
|
|
|
|
|
|
|
Technical writers compose communication from product developers for users of the products. Users include consumers as well as scientists, engineers, plant executives, line workers, and production managers.
Communication skills: These include writing, self-communication, interviewing, research, and interpersonal communication skills. When writing technical documents, professional technical communicators must be both clear and concise. When planning and managing projects, they need to be able to anticipate obstacles, prioritize tasks, and manage their time. When gathering information for assignments, they must be able to efficiently collect it from the busy subject matter experts (SMEs) they are working with, or be able to find it in reference materials. Project meetings can be a great place to find useful information, as long as the technical communicator knows how to listen for it. Because technical communicators are almost always part of a larger project team, they must possess tact, gentle assertiveness, willingness to help, and the ability to adapt to rapidly changing circumstances.
Technical skills: These include knowledge of hardware and software, general computer literacy, and familiarity with the tools of the profession like Microsoft Word, Adobe FrameMaker, and RoboHelp. Technical communicators must be familiar with the appropriate networking and telecommunications equipment as well as specific database, telecommunication, and programming software. Technical communicators also need to be familiar with industry processes, such as ISO requirements.
Many employers prefer applicants with a four-year college degree in communications, engineering, or journalism, or those possessing a degree or certificate in technical writing. A college degree is recommended for people interested in careers in technical communication, although a major in technical communication is not necessary. Individuals interested in becoming technical writers should take courses in
|
|
A 2002 survey of Society for Technical Communication members showed the seven academic backgrounds most common among technical communicators:
| English | 32% |
| Technical Communication | 22% |
| Business Administration | 10% |
| Computer Science | 9% |
| Science | 9% |
| Engineering | 8% |
| Journalism | 7% |
| Other | 28% |
Note: The question was presented as multiple-choice and some respondents checked off more than one area of study, so the percentages listed add up to more than 100 percent.
Apply directly to employers: Direct application to employers remains one of the most effective job search methods, but it should by no means be the only method that you should use.
Join a professional organization: Many professional associations, such as the Society for Technical Communication, maintain job listings on their Internet sites. Professional association meetings can be a good place to make contacts and get advice from those experienced in the field.
Meet others in the field: Networking with other professionals is also an effective way of finding jobs, including those that are not advertised outside of the company.
Technical writers should prepare a portfolio of technical writing samples that may include projects completed as a student or a volunteer as well as professional work. This portfolio is over and above the normal résumé or curriculum vitae that a technical writer must have, and will show any prospective employer the quality of work that you have produced in previous assignments. This work can include Web pages you've designed, technical manuals you've edited, or brochures you've designed, among others.
Only a few years ago, computer literacy was considered merely an asset whereas today it is a requirement, and some technical writers may be required to know and be able to read programming languages. Applicants must have good computer skills and may need a working knowledge of specific industry operations and procedures. Applicants should also have good communication skills and be able to convey scientific and technical information clearly and accurately. Increasingly, companies require technical writers to be knowledgeable about computer graphics and desktop publishing, including multimedia production. Some employers will only hire experienced writers who specialize in one field of technology. Some employers require a strong background of technical knowledge and experience, combined with writing skills. Employers also select trainees from among technicians who have backgrounds in science, military equipment, and communications.
Writers must write in a concise and easy-to-read manner for consumer publications or in highly specialized language for experts. With the increased use of desktop publishing, technical writers are increasingly responsible for the publication process including graphics, layout, and document design.
Technical communicators work in every medium, including print, illustrations, video, multimedia, online help systems, Web sites, and training materials. They work in almost every industry, including:
Banking, finance, and insurance
Legal, government and defense
Computing, engineering, and telecommunications
Healthcare, biotechnology, pharmaceutical, and environmental
Manufacturing and aviation
Within their chosen industry, many technical writers will specialize further. For example, technical writers in the computer industry might specialize in software documentation, tutorials, or user manuals.
Technical writers design and develop a broad range of information and produce a variety of communication products. User's guides, reference manuals, policies and procedure guide, quick references, online help, online wizards, guided tours, and online cue cards explain how to use products, services, and policies. Web sites provide support and documentation. Technical reports, articles, and books exchange "basic" scientific information. Proposals, catalogs, brochures, videotapes, audio tapes, and demonstrations market products and services. Workbooks, tutorials, quick references, and online coaches train users. Newsletters, magazines, and e-zines have a combination of purposes.
Work week: The normal work week is 40 hours; however, this is often exceeded to meet publication deadlines, and tight deadlines can create stressful working conditions.
Environment: Most technical writing is done at a desk in an office. However, during planning and production of publications, writers may be required to travel to discuss a project with others. Some technical writers are able to do much of their work from a home-office, using teleconference technology and the Internet to communicate with others.
Pay: According to the Society for Technical Communication's 2003 Salary Survey, the mean salary for entry-level technical writers/editors in the United States was $43,260. For these professionals in Canada, it was $41,030. Some companies pay time-and-a-half for overtime, while others offer compensatory time off.
Benefits: Benefits available in some companies include vacation, holidays, flexible hours, sick leave, bonuses, health and life insurance, and retirement plans.
Tools: Technical writers use personal computers and word processing or desktop publishing packages as typical tools for text, graphic, and multimedia production.
Supervision: Writers may work alone or together under the supervision of a publications chief or editor, a product or procedure specialist, or a marketing manager.
About one fourth of technical writers are independent freelancers and consultants. Choosing to work as a freelance technical writer can be both liberating and frustrating. You can choose when you want to work, and you have a wider variety of experience available to you than the technical writer that works for a single company. However, finding freelance work requires self-discipline and motivation. Jobs can sometimes be hard to come by. Self-employed technical writers must carefully estimate the number of hours needed to complete a project under contract. Technical writers who work under contract or freelance may work from their home or at the employer's site. Self-employed technical writers must pay for their own insurance.
Technical writing has become an increasingly essential occupation in business and government, and jobs can be found in almost any industry sector because of the need for users' guides, instruction manuals, and training manuals. Demand for technical writers is expected to grow because of the need to communicate new scientific and technical information to others.
The U. S. Bureau of Labor Statistics' Occupation Outlook Handbook (2004-5 edition) predicts that over the next several years, among the different areas of writing, the most job opportunities will be for technical writers and writers with specialized training. It goes on to say that demand for technical writers and writers with expertise in specialty areas, such as law, medicine, or economics, is expected to increase because of the continuing expansion of scientific and technical information and the need to communicate it to others. The full entry can be found at the US Department of Labor, Bureau of Labor Statistics.
HOME | FAQ | PORTFOLIOS | CRITIQUE | RESUME | RESOURCES | CONTACT
This page was created using Microsoft Front Page 2003.
Technical Communication Introduction ©2006 Damien Wilker, Wright State University