RE: Resumes/Interviewing

[Kimberly <JKWilson -at- concentric -dot- net>]

>Date: Wed, 01 Dec 1999 01:18:18 -0500
>To: MAGGIE SECARA <SECARAM -at- mainsaver -dot- com>
>From: Kimberly <JKWilson -at- concentric -dot- net>
>Subject: RE: Resumes/Interviewing
>
>My objective statement, which I call "Desired Situation" is simple, and
it's meant mainly for the contract or contract-to-perm market. (A long-term
career position is a different story.)
>
>Desired Situation: Contract or permanent position as a technical writer,
web author or documentation specialist in a client-server applications
development environment. Contract rate $xx-xx. Available (date, or) two
weeks from acceptance of the position. Home office equipped for
telecommuting and limited business travel is acceptable. Prefer north,
northwest, downtown or airport areas of Atlanta metro area.
>
>It just states a few facts about what *I* want right up front. It helps ME
screen out jobs I don't even want to consider (commute too far away, too
much travel, wrong industry, etc.), which saves all parties time and
trouble. If the market is tighter, or I want to move into a new area of
focus, I just modify the paragraph. 
>
>FWIW
>Kimberly, still in Atlanta GA
>
>
>At 03:51 PM 11/30/1999 -0800, you wrote:
>>
>>> >> Tothscribe (Nea Dodson) asks:
>>> >> What would you think of the following resume layout?
>>> [snip]
>>> 
>>> "Murrell, Thomas" <TMurrell -at- alldata -dot- net> writes:
>>> > I prefer a different format:
>>> > 1. General Statement of My Objective.
>>> 
>>> Statements of objectives are terrifyingly vague.  Objective for what?  The
>>> resume?  (objective:  get the job.)  The job? (objective:  prove I can do
>>> the job.)  Life?  (objective: work in edutainment, make a lot of money,
>>> play with the cats, and collect all the episodes of Buffy tVS.)  
>>> 
>>> All of those look particularly bad when actually written down,
>>> particularly item 3. :>
>