All Content
All Content
Podcast in iTunes
Follow me on Twitter
How to Break into Technical Writing
May 27th, 2007 | Posted in Technical Writing |
T asks:
I have been a professional pilot for 37 years. I have taken about 7 online courses in Technical Writing and earned a certificate in Technical Writing from Clemson University. I have a Master’s degree in Aeronautical Science. I don’t have any experience in the graphics software like Photoshop. How can I break into the technical writing field?
If you’ve been a pilot for 37 years, you probably know more about the airplane mechanics and the airline industry than anyone else. I recommend targeting that industry for technical writing careers. Luckily for you, industry knowledge is preferred over tool knowledge (supposedly). So emphasize your subject matter expertise on your resume.
Your question about breaking into technical writing surfaces at least monthly on technical writing mailing lists. You might try searching the archives. But here’s my recommendation:
- Look at the software requirements for the jobs you’re interested in applying for.
- Download trial versions of the software, and publish several sample help files demonstrating your ability with the tool.
- When possible, volunteer for internships to gain more experience. (I realize this option is often not feasible.)
- Write some help content for products that need help. You can visit about any open-source project and add a few pages of help content. Alternatively, pick a topic you know well (such as your cell phone) and write help content for it.
- Join the local STC and volunteer for things. For example, just about any chapter can use someone on their newsletter team, someone to help coordinate food, someone to look out for and welcome new members, or someone to work on their website. Ask how you can volunteer. Then pick the brains of these members for the best places to work in the area.
- Apply for lots of entry-level jobs. Be persistent and patient.
- Know that your tool knowledge can remain superficial when it comes to applications like Photoshop. Photoshop is the mother of all graphics programs, but chances are if you can use SnagIt, you’re fine. Photoshop is for photo manipulation. And actually, it’s cumbersome to use to draw arrows. You could probably spend your life learning Photoshop, when all you basically need to do is crop screenshots.
- When you go to interviews, bring samples of anything you’ve written and are proud of. If you can write well, chances are you can write technical instructions well too. I think it’s considerably easier to write instructions than literary essays. So if you can demonstrate your literal ability in another arena, employers might overlook lack of technical know-how.
- Develop an abiding interest in technology. Get techie and stay techie. Learn to love podcasts like Slashdot Review.
- Move to a city where tech comm jobs are abundant. See this post in my archive for the cities.
I haven’t said anything revolutionary here. Maybe a cleverer reader can add more insight. And T, what are your thoughts?
By the way, this page on the Suncoast Chapter STC is supposed to show a job stream of technical writing jobs from Indeed.com in your area (based on your IP address). Does it work for you?
Related Posts
- Personal Essays on a Technical Writing Career — by John Hewitt
- “How can I become a successful TECHNICAL WRITER?”
- Technical Writing in India — Interview with Sandeep Balakrishna
- Podcast: What’s New in the Field of Technical Communication?
- We need an IT Conversations for Tech Writers
May 28th, 2007 at 3:47 am
Back in 2002, I wrote an article on “Getting Started in Technical Writing” for the Lone Writer SIG’s newsletter. The bad news is that the article is only available to members of that SIG; the good news is that other STC newsletters picked it up and it’s available publicly (with minor local variations) on various sites, including this one: http://www.stc-sd.org/newsletter/june_2002/visitingauthor.htm
Although it’s a bit old now (2002 seems such a LONG time ago!), the general advice still applies. Interestingly, some of the tools I listed no longer apply…
May 30th, 2007 at 2:26 am
[...] degree in Aeronautical Science. I don’t have any experience in the graphics software li…Read more…cell [...]
May 30th, 2007 at 5:00 am
[...] more - ] DarrenBarefoot.com - - Monday, May 28, 2007 - Feed - Focus Sunday, May 27, 2007 How to Break into Technical Writing by tom in Technical Writing T asks: I have been a professional pilot for 37 years. I have taken [...]
May 30th, 2007 at 10:28 pm
Rhonda, after reading your article, I see that I should have just linked to it and foregone my little post! You have a lot of excellent information there.
May 31st, 2007 at 12:02 pm
Tom,
If T is a pilot, he might do better writing technical instructions for aviation equipment or something related to that field. I frequently see ads for technical writers requiring industry-specific knowledge.
Writing about aviation or aeronautics would be the easiest way for T to break into the field.
I think those of us who primarily write software instruction forget that there is a TON of technical stuff out there that is mechanical, not electronic, and it all needs documentation.
Holly
June 1st, 2007 at 6:10 am
T.
I would echo Tom and Holly here. Target your job queries initially to the aviation industry. It has a couple of advantages–easier to break into, as they have said, but you are also going to get you a higher start pay than in other industries. Not only that, it’s an easier learning curve. Since you know the terminology, etc. you can concentrate more on becoming a better writer and learning the tools.
If you haven’t already got some samples, start putting them together now. Tom’s suggestion of writing documentation for open source projects is a good one. It gives you something ‘real’ to write about, rather than just making stuff up, which is hard. I know when I was interviewing technical writers two very important things to me were the resume itself and their folio of work, both of which showed the writer could write.
Rhonda said network, and I agree with that too. Half the jobs I know about are word of mouth. Tell your pilot friends you want to do technical writing. (After they get over the huh? part and understand what it is, they may mention your name if they know of anyone who is looking for a writer.) Here in Australia the non-networked jobs come mostly through the agencies. I don’t know what it’s like in the US, but don’t discount them.
If you’re not a good typist, practise. Touch-type if possible, and get your speed up.
Toolwise, if you know of a common tool used in the Aviation industry (e.g. FrameMaker) I would spend more effort learning that one first. I would also learn about MS Word at least template and style level (and revisions). I confess in the past I have decided not to interview people based on the fact that their resume was manually formatted rather than using styles. (It may be a personal thing, but my thinking at the time was that if they didn’t know how to use styles then they were going to make a mess of the documents.
June 3rd, 2007 at 4:46 pm
Get signed up to TechWR mailing list.
I think that’s the only other bit of advice I can think of… nice article, as was Rhonda’s.
Learning how to pitch your knowledge and your ability to learn new skills is key, if you can sell yourself you are halfway there.
June 12th, 2007 at 10:02 am
[...] would definitely stand out: http://journey.wsj.com/ This also goes along with Tom Johnson’s recent post about how to break into the Technical Communication field. If you whip up a portfolio similar to [...]
December 13th, 2007 at 7:11 am
Hey!…I Googled for clemson sc, but found your page about How to Break into Technical Writing…and have to say thanks. nice read.
December 14th, 2007 at 1:13 am
Thanks for dropping me a note. Glad you liked the post.
February 16th, 2008 at 10:49 pm
[...] You might also see this post I wrote: “How to Break into Technical Writing” [...]
June 16th, 2008 at 3:06 pm
I have an English degree plus a Master’s Degree in Lib Science. I’ve writen a lot of stuff in college, but don’t know what happened to it since. What can I do to show the employers that I have what it takes to be a Tech Writer?
June 16th, 2008 at 3:11 pm
Kris, I think I answered your question with this post: How can I become a successful technical writer.