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.
> Jennifer writes:
> Would they automatically turn you down if you didn't list these software
> skills being that the entire universe (not just our field) is pushing
> technical skills? Or would they be trend-savy enough to know that this
> the way things are going, if there indeed is a trend?
> I would hope I wouldn't be turned down at least for an interview, if I
> didn't slap "FrameMaker" somewhere in the resume. What are your thoughts?
I currently do some interviewing and screening of applicant, and did
quite a bit at my former job with a consulting firm. While it may seem
archaic to list software skills, and can become cumbersome, I generally
think it is a good idea to do so, particularly if the requisition or ad
specifically request tool skills. Some tool skills are harder to come by
than others, so you might want to be selective.
On the other hand, I consider any good, experienced tech writer
trainable and wouldn't pass on a candidate because that person didn't have
experience specifically with Rational SoDA or Adobe FrameMaker (both of
which my shop uses). Previous experience with either could serve as a tie
breaker or help get the interview, however.
curtis_ward -at- dbs-systems -dot- com