Latest posts by techwriter (see all)
- What is the Readability Index of Your Writing? - November 20, 2017
- Should Technical Writing be Boring? And if Yes, Why? - November 15, 2017
- How to Create a Custom-Designed Header in MS Word that Would be Available to All Other Word Documents - November 13, 2017
Are you a Computer Science/Engineering undergrad? Or, have you graduated and are looking for alternatives to the usual Software Development or Testing career paths? If yes, have you considered technical writing as a possible career option? Chances are, you haven’t; because you don’t know enough about technical writing.
People still know so little about technical writing that they miss out on the lucrative job opportunities this profession provides. In this piece, I try to explain what technical writing is all about, and why you should consider this as a career option.
As organizations have started recognizing the need and importance of technical documentation, the demand for technical writers with all experience levels have gone up. The demand for technical writers, and consequently the pay packages, are now at par with (or even better than) that of the Software Development or Testing professionals.
Sounds like a cool career option?
The typical job responsibility of a technical writer is writing software documentation; although technical writing can also involve hardware documentation and training program development. Some real-world examples of software/hardware documentation are:
- Context-sensitive help for a desktop applications (accessed by pressing F1),
- Administration Guide for a server
- FAQ pages for a social-networking website
- Online help for an image editor
- User manual for a cell phone
- Troubleshooting manual for ATM machines
- and more..