TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
How about the term "Writer." Why bother to add some pompous title, when all
the information the prospective employer needs in the resume? For example,
if every job listed or if all projects you did were for Microsoft, Symantic
or other software concerns, it is a easy bet that you wrote software
documentation.
I have a real problem with titles, as they often tell me very little, yet
reveal quite a bit. Besides, from reading all the replies to the original
post, I am not sure that the term Technical Writer can be easily defined.
Someone who writes Barbecue Cookbooks is working in the field of Technical
Barbecue Science and Application, but I would not think that a writer of
cookbooks is a Technical Writer, even though they specialize in one
specific area. According to the dictionary, the writer is writing something
technical, but very few people would equate this subject with the field of
Technical Writing.
Me, I am Bobbo, the guy who writes assembly and production procedures. I do
not consider myself a Technical Writer.
