>>>>> "DR" == Dave Rolsky <autarch@urth.org> writes:

  DR> On Tue, 13 Nov 2007, Ask Bjørn Hansen wrote:
  >> Usually 1-2 pages.  If you are very experienced then 2-3 pages.
  >> 
  >> Everything in the resume should be interesting and relevant though.
  >> As lont as it is, the length isn't so important.

  DR> One way to keep the resume shorter is to start trimming descriptions of
  DR> your oldest positions.

  DR> For example, I have my earliest two positions listed on my resume with
  DR> just employer, title and dates, since presumably my more recent
  DR> positions are going to be more interesting to a potential employer.

that is a decent idea. i have to trim out many jobs because i have had
so many over the years. i still keep some very old ones since the work i
did there is still relevent to my career. but many smaller contracts and
such are totally edited out of the short version. i keep a longer
version around for me. even so my shorter version is about 3 pages.

one thing i have done in helping out my clients is to show them how to
write shorter and punchier job descriptions. this helps in reading and
editing resumes. for example tell me what you were responsible for and
don't tell me all the little technical details about which editor you
used. you designed a foo system that did this. not "i used apache and
mod_perl and the foo module and the bar module and blah blah. i used OO
perl throughout and used a waterfall development methodology except when
it wasn't raining."

uri

-- 
Uri Guttman  ------  uri@stemsystems.com  -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org