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.
On Wed, 1 Dec 1999 12:03:46 Lydia Wong wrote:
>Connie writes, in part:
>So, first show us you meet our requirements. Then start telling us all about
>yourself, how you can grow and learn, what you like in life, what kind of
>thinker you are, etc. That's what the interview is for. ; )
This post really hits the nail on the head, in my opinion. Many posts go on and on in detail about what should and shouldn't go into a resume without examining the simple fact of what a resume is for.
Basically, a resume is an advertisement you send to a company that convinces them to give you an interview. That's it, it is your ticket to interview at the company. If the information you include in the resume furthers that cause, include it. If you are trying to be exhaustive in listing your accomplishments and skills, you may simply bore the reader and still not convince them.
The most important question you need to answer, is why should that company want to interview you? And the answer is in their job listing.
My 2 cents..
techwriter -at- my-deja -dot- com