Jan 16
2009A technical writer from Hangzhou sent me an email with some technical writing-related questions. I thought I’d share these questions with my readers. I don’t have all the answers so I’ll share from my observations and thoughts. If you have any insights to share, please feel free to comment on this post.
Can I really learn some useful things in the tech comm programs?
I already have much experience and can manage communicating with SMEs & conveying the technical information in my documents well; I may get the project management skills if I stay in my current company longer and get prompted some day later. While in the websites of the programs, there does not seem to be anything exceptional with the curricula.
I don’t have a degree in technical communication, so I can’t say whether the degree is useful or not. I believe there are only a handful for colleges and universities in the U.S. that offer TC programs or degrees. There are no such programs in China. I’m not sure about other countries, but my guess is that TC is not a popular degree. I also think that having a TC degree is very limited because it is too specialized. Unless you know for sure that you want to pursue a long-term career in technical communication, I think a more general degree like English, journalism, or other liberal arts program is a better choice. Most schools offer TC-related courses, so students who are interested in pursuing technical writing can take those classes.
Generally, I don’t think companies look to see if you have a technical writing degree. Companies usually prefer to hire experienced technical writers, so any experience you have, whether through TC-related coursework or previous work experience, can help you get a job.
Is there any space for the tech comm technology to develop?
It seem that this technology does not have any ‘depth’. I have been wondering whether there is anything to research in this area, though very possibly it is a stupid idea… However, it is true that at least the Ivy League universities have not shown any interest in offering the tech comm courses.
All the Ivy League schools are known for their liberal arts programs, which provide you with a more well-rounded education. Usually, undergraduate students don’t have a clear picture of what they want to do yet. It is better to get a general degree first for their undergraduate degree. Later, when they have a better idea which area or field they want to pursue, they can get a specialized degree for their masters or Ph.D.
In terms of how much room the tech comm technology can grow or develop, I don’t have a good answer because I’m not an expert in this area. By research, I think you mean whether the tech comm process can be improved at a bigger/global scale. I believe there are. For example, the recent trend in technical writing is single-sourcing content. The most popular “technology” for single-sourcing content is called DITA. I don’t know much about DITA, but it’s the talk of the tech comm world. DITA is not perfect, but it provides a better solution than other methods out there. Another areas of research could be the impact of Web2.0 on how documentation is created/delivered, such as documentation in Wiki format.
Will any company in the US hire someone to write in English, when he is not a native speaker?
A more practical question. Also due to this question, I think going to study tech comm in order to work in the US could be risky. So do you think it is a good idea for me to pursue my American dream? And what do you think about the future for people in this profession?
As mentioned previously, most companies don’t look to see if you have a technical writing degree. Having a specialized degree is certainly helpful but not required. Typically, companies look for two things: ability to write/communicate and interest/background in technology. Some companies also require previous technical writing experience. If you have these three areas covered, then you are a good candidate for a technical writing position.
Now the question of whether a U.S. company will hire a non-native English speaker for a technical writing position, I don’t think this is a big issue. I’m not a native English speaker, and I work for an American company. Many companies are outsourcing technical writing to China and India. I’ve seen some quality documentation written by non-native English speakers. I’ve also seen bad documentation as well, but not just from China. You’ll find some poorly written documentation in the U.S. too!
Technical writing is a very specialized “language” that can be learned. If you are looking to work for a U.S. company, then you need to provide excellent writing samples to demonstrate your ability to write/communicate.
Related Articles: |






Great to read the response in your blog! I am the one who asked the questions
Now I have also noticed that techcomm is a rather “specialized” subject, which is part of the reasons why it is not so popular – not even in the US where it originates. However it has room to develop and is worth researching, as you have also acknowledged. In addition, in some magazines, e.g. US News & World Reports, it has been always indicated that technical writer will be among the twenty hot job tracks in the future. So I am sure more people will be interested in this job soon. Though I cannot determine right now whether technical communication shall be my lifelong profession, I definitely like to explore further in this field, for example trying some new tasks, so as to find out how this field is evolving and which career path is suitable for me.
Just food for thought – one interesting topic I have noticed recently is user experience, which should be counted as a sub-area of tech comm: by writing good documents we teach the users about the products, but most users are not so willing to learn; while by designing more user-friendly product interfaces, we can have the users getting along better with the products, and they would be happy because they need to read fewer “boring” manuals. So I think tech communicators may like to try this kind of job, if they do not want to “write manuals for all their lifes”. By the way, I am sure that NI has the user interface designing stuff, so you may have chance to take job rotations and work with them or in their roles, if you like