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.
>I've been asked to send a resume with a cover letter >explaining why the company needs me... and my mind is blank >today. Any suggestions?
Some day, somebody is going to write a book about snappy answers to
common job-hunting questions.
Meanwhile, I keep all my cover letters on disk, and cut and paste and
personalize when I need one.
One way I always answer the question of why a tech-writer is useful is
that users always encounter the documentation soon after buying a
product. As a result, their impression of the company and product is
partly determined by the documentation. In other words, good
documentation means good PR.
However, I do wonder: are you being asked to explain why a tech-writer
is needed, or why you should be that writer?
Bruce Byfield (bbyfield -at- axionet -dot- com / bbyfield -at- ca -dot- ibm -dot- com)
IBM Pacific Development Centre
h: (604) 421-7189 o: (604) 293-5781
"I never had the chance to prove them wrong,
My time was short, the story long,
No, I never had the chance to prove them wrong,
It's always them that write the song."
--Oyster Band, "Oxford Girl"