Moving into Technical Writing -- A DICE Article and More Links
How to break into technical writing is one of the most common questions readers ask. (If you wrote a book entirely on this subject, I'm sure you'd sell regular copies.) Recently a journalist interviewed me and others (Jack Molisani, Mike Hughes, and Andrea Ames) on this topic. He published his article, called Use Your IT Experience to Move into Technical Writing, in DICE.
I have only a small quote at the end. In one of my responses about tools, I must have mumbled Camtasia in a way that sounded like Fantasia. (But I admit the latter sounds like a more fun tool to use.)
The article includes excellent research and information for breaking into technical writing. For those looking to break into technical writing, I also have an entire section on my blog dedicated to this topic. Breaking into Technical Writing (as a Student or Transitioning from Another Career) lists more than a dozen links with information on how to transition into technical writing. If you have more to add to my list, please send me them.
As a side note, the DICE writer who interviewed me is interested in moving into technical writing himself. So if you know of a company near San Jose, California looking to hire a new technical writer with excellent writing skills, let me know and I'll put you in contact with him.
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.
If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. 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.