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.
Hi. I used to read TECHWR-L regularly, then stopped for a few years. So
I'm sure during the time I was gone you must have discussed this. It's
such a big concern of mine, though.
How can we convince employers who are looking to hire a tech writer that
their primary concern should not be with the software programs a tech
writer has experience using? that a technical writer is not, primarily,
a typist?
I got a copy of FrameMaker and taught it to myself in less than a week.
I got a copy of FrontPage 98 and taught it to myself in a week. I
learned Visio by myself in less than a day. I haven't done the same with
RoboHelp because it's so darned expensive, but I know this would be a
similar case.
How can we convince employers that today's software is easy and can be
learned quickly, and a good technical writer can't be defined by her
software experience? A good writer is a good writer, right?
But take a look at the want ads. Every tech writer ad specifies right
away which software the tech writer should have experience with and
which degree they should have. Somehow employers see value in a college
degree, but why when their other concern is just software experience?
