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:Mistaken job requirements, take II From:"Geoff Hart (by way of \"Eric J. Ray\" <ejray -at- raycomm -dot- com>)" <ght -at- MTL -dot- FERIC -dot- CA> Date:Fri, 29 Jan 1999 08:07:28 -0700
Continuing the thread, Elizabeth Vollbach noted <<When all else is
equal, hire the guy with more tool knowledge. But, most often, all
else isn't equal. And most often, a good tech writer doesn't get her
foot in the door unless she has lots of experience with FrameMaker
and RoboHelp. And, to most employers, it seems, that experience is a
no.1 requirement and matters more than writing ability.>>
I think you've raised an important point, because raw talent usually
doesn't become true competence until you've obtained some experience
in the trenches that teaches you how to apply that talent. So as an
indirect clue, listing experience with (say) Frame is a good way for
an employer to be reassured that you've been around long enough to
get to the competent stage. Admittedly, it's not always the best way
to judge someone's talent, but it is a good clue... though hopefully
one of many that you use in making your decision.
--Geoff Hart @8^{)} Pointe-Claire, Quebec
geoff-h -at- mtl -dot- feric -dot- ca
