Email Newsletter

Search results

Podcast on getting a job in technical writing (TW Job)

How to get a job in technical writing

by Tom Johnson on Dec 26, 2009 •
categories: beginners podcasts

Download MP3
Length: 40 min.

Last week I gave a presentation to BYU Idaho students entitled 7 Steps to Getting a Job in Technical Writing. This is a recording of my presentation. You may remember a lengthy post I wrote on this same subject, 7 steps to getting a job in technical writing, as well.

Although getting a job is the focus of the podcast, I also talk about what technical writers do, how they approach a project, how they decide what to create, and how they generate ideas for tasks. Specifically, I talk about about a project people can work on at tech.lds.org. People can start writing help for the project here.

In listening to myself give this presentation, I realize that I have a breathless energy to my voice. As weird as it sounds, "breathing" while I'm presenting is something I'm working on. I don't know if I need to simply pause and relax more, or if the mic is too sensitive and is picking up every tiny breathing sound and magnifying it. But if you have suggestions, please let me know. Also, you may hear typing noises in this podcast as well as the panel. That's a student taking notes on a laptop.

Sponsored content

Buy me a coffeeBuy me a coffee
follow us in feedly

About Tom Johnson

Tom Johnson

I'm a technical writer / API doc specialist based in the Seattle area. In this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, visual communication, information architecture, writing techniques, plain language, tech comm careers, and more. Check out my API documentation if you're looking for more info about that. If you're a technical writer and want to keep on top of the latest trends in the field, be sure to subscribe to email updates. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.

Comments