Re: Getting a job as a technical writer (was just job)
Here are some ideas on how to get into technical communication:
- Demonstrate to the tool heads that you can use FrameMaker (or Word or something) at a sophisticated level. Most recruiters take tool ability to mean you can also do the intellectual part of the job. In reality the tool is just 10 percent of the work albeit an important 10 percent.
- Show that you can use a reasonably sophisticated HTML editor.
- Demonstrate a knack for keeping up with the latest trends in relevant technology.
- Include in your resume all the word-processing, desktop publishing and graphics software tools you know how to use.
- Get the latest buzzwords and phrases into your resume. Be able to converse using these terms. It shows people you understand where they are coming from.
- Show the recruiter you know how to work with difficult people (like software developers, engineers, and other linguaphobes) who have trouble communicating what's actually important to the user.
- Let the recruiter know you aren't going to piss people off with your I'm the Language Guy BS. The words "team player" mean you are capable of being flexible.
- You have to know your market. Choose an area of technical interest: Technical writing isn't really your job. Technical communication is being a conduit from technicians to an audience. You have to understand both the technician and the audience. You are the "middle-man". Think of yourself as an information distribution warehouse. Get information at the lowest possible cost to you (i.e.: You don't waste time.) and get it to the consumer at a price they can afford (i.e.: You aren't wasting their time.). My point is that not every warehouse contains all wares.
- Have you ever edited? Editing can be a way in to technical writing. But it's not necessarily for everyone. It isn't (wasn't) for me.
- Have you ever created a set of procedures for a complex process? It isn't necessarily as easy as it looks. Find a worthwhile project (paid or not) that gives you experience while you're looking and that you can use in a portfolio.
- Go to school and learn about technical communication. Some people need or like this approach. School gives you a theoretical and practical background. It's not a requirement even though some would argue it should be. I'm not one of those. (Please don't flame me.)
- JOIN STC now. VOLUNTEER for a committee or something. GET to know people in the industry. LEARN what they are doing. LISTEN to what they say. THIS is the most successful technique I know and in conjunction with all the the suggestions has always worked for me. People who know and LIKE you are more likely to give you a chance.
Brian
From ??? -at- ??? Sun Jan 00 00:00:00 0000=
Previous by Author:
Re: Recommended software for breaking into technical writing
Next by Author:
Re: Getting a job as a technical writer (was just job)
Previous by Thread:
Re: Mutiple doc, html, or fm files to single PDF file?
Next by Thread:
Re: Getting a job as a technical writer (was just job)
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads