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.
As one of those anal-retentive style watchers, I agree that not using
styles shouldn't be used as a screening tool. An awesome resume
(content-wise) is an awesome resume.
You also gave many justifiable reasons for having screwed up or no
styles.
The real point is that the interviewee should realize that their work
(in Word) will be scrutinized, and they better have a good excuse for
submitting poorly structured Word documents with respect to basic
features that are fundamental to our profession in nearly every tool of
our trade.
The pointed questions that I'll ask in the interview about all the
redefinitions of "normal" become dull quickly when you explain your
conversion process. Your explanation for a weakness will turn into a
strength.
Another secret handshake that was mentioned in the Translation and
graphics thread was linked images. This doesn't apply to resumes but
could apply to other submitted samples. I'd rather have a zip file that
expands into a document and a subdirectory full of images that a huge
doc file with embedded images.
Using the above example of a zip file, another handshake is the
structure of your work. How are your doc files named? How are your
subdirectories organized? What naming convention do you use on the
graphic images and is it conducive to maintenance and translation?
The naming convention used on the submitted file is another secret
handshake. "resume.doc" doesn't cut it. "Jane_doe_resume.doc" is much
better.
Glenn Maxey
Technical Writer
Voyant Technologies, Inc.
1765 West 121st Avenue
Westminster, CO 80234-2301
Tel. +1 303.223.5164
Fax. +1 303.223.5275
glenn -dot- maxey -at- voyanttech -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
