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.
Subject:Re: FrameMaker Required (Was From:Tony Rocco <tony_rocco -at- NAVIS -dot- COM> Date:Wed, 13 Mar 1996 15:49:48 U
RE>FrameMaker Required (Was: Re:... 3/13/96
Hallelujah. All you hiring managers out there reading this list, take note.
Someone without the requisite software skills can learn them if they have
previous experience on a similar app, or are just reasonably intelligent and
motivated. It's the documentation experience that counts the most.
Recruiters, too, need to learn this fact. They look over a resume and if the
right list of software titles isn't there, they discard it and move to the
next one. Geez, give us a tech writers some credit for being able to learn
stuff. After all, that's what our job is aabout anyway, learning new apps,
Date: 3/13/96 07:19
To: Tony Rocco
From: Jim Grey
Robert Plamondon <robert -at- plamondon -dot- com> laments poor hiring criteria:
>The thing that brought Bad Tech Pubs Departments(TM) to mind (and
>caused me to digress from my central digression) was an experience a
>friend of mine had -- she is a highly talented writer, with tons of valuable
>experience. Few potential employers seemed aware of this. Instead, the
>central question seemed to be, "Do you have experience with FrameMaker?"
>There were clearly two pieces of simultaneous brain-failure going
>on in these people's minds:
>1. The most important skill a technical writer has is desktop
> publishing. Experience in technical writing is more or less
>2. Some fundamental barrier exists that makes it impractical to
> train experienced technical writers in the DTP package du jour.
I've never worked for a company that planned well enough ahead to hire temps
at any other time than the last minute. When the deadline looms, managerial
minds think, "There's no time to train a temp in Interleaf, so we'd better
just use this person I found who already knows Interleaf." Fretfully, I
ask, "Yes, but does this candidate have the needed writing experience?"
"Well, s/he has written documentation before," the manager tentatively
offers. Well, I've written code before, but that experience doesn't
automatically qualify me for a temporary position on the software
A manager at one of my former employers was deathly afraid of Interleaf. In
those rare cases we looked for temporary or permanent help, he got the most
excited about resumes that cited Interleaf experience. "We wouldn't have to
train them!" I regularly reminded him that I learned enough about Interleaf
in my first week to be fairly productive.
We can keep reminding our managers at hiring time that the tools aren't hard
to learn, and that skills learned in one DTP package can usually be
transferred to another. This won't solve the problem, but may make it less
jim grey |beebeebumbleandthestingersmottthehoopleraycharlessingers
jimgrey -at- iquest -dot- net|lonniemackandtwangin'eddiehere'smyringwe'regoingsteadyta
My vanity page is now online! Oh boy! http://www.iquest.net/~jimgrey/