Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pur-ee.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!inuxc!pur-ee!ecn-ee!tk
From: tk@ecn-ee.UUCP
Newsgroups: net.jobs
Subject: Job objectives: ffinding the balance - (nf)
Message-ID: <1866@pur-ee.UUCP>
Date: Tue, 15-May-84 01:19:00 EDT
Article-I.D.: pur-ee.1866
Posted: Tue May 15 01:19:00 1984
Date-Received: Wed, 16-May-84 03:44:30 EDT
Sender: notes@pur-ee.UUCP
Organization: Electrical Engineering Department , Purdue University
Lines: 26

#N:ecn-ee:18900002:000:1096
ecn-ee!tk    May 14 22:29:00 1984

-
Could some of you share your thoughts on the subject of stating a
career  objective that treads the fine line between being neither
too specific nor too general? That is, making  the  statement  in
such  a  way  that one doesn't pigeonhole him/herself, but on the
other hand not being  so  general  that  it  appears  the  person
writing  the resume has no idea what they want. To narrow it down
to my own situation, I am entering the job market for  the  first
time,  so I have no previous experience to guide my expectations.
My engineering background is fairly broad, and I am keying on  my
computer  applications background and software design/development
experience; I'd like to market myself in such a way  that  I  can
use  the  breadth of my background to advantage. Is that nebulous
enough? 

Any comments, suggestions, examples, or the like would be greatly
appreciated.  I'd like to hear some advice from both sides of the
fence (i.e. employer and job-seeker). Thanks very much. 
--------
Tom Kirk
UUCP: {allegra|decvax|harpo|ihnp4|teklabs|ucbvax}!pur-ee!tk
ARPA: pur-ee!tk@berkeley