I went to Andy Lester's 'Pragmatic Job Hunting' talk at YAPC this year. It was pretty interesting. He mentioned some stuff that I hadn't thought about. Here are his slides. The resume portion starts on page 21: http://www.petdance.com/perl/advice-for-job-seekers.pdf
I was surprised that he said NOT to put an objective. The gist of it was that 'objectives' are generic and pretty much the same everywhere. His resume is at http://www.petdance.com/resume/ You might e-mail him for advice, too. Jeremy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will Willis Sent: Wednesday, August 02, 2006 9:14 AM To: Houston.pm located in Houston, TX. Subject: [pm-h] OT: Resume Advice <topic type="off">This isn't exactly a Perl related post or question</topic> I'm in the process of revamping my resume. I've received advice from online sources, school professors, and head hunters, but everyone has a different idea as to what is most important to a resume and how it should be presented. So I ask of you techies and those that hire for technical positions, in your opinion, what makes a good resume, also what common or big mistakes should one avoid when composing a resume? Also, I've got a few specific questions I'd like to get people's opinions on. What order do you organize your resume in? (Profile, Career Objectives, Skills, Employment History, etc...) Specifically, is my skill set (Perl, XML, Apache, etc..) more important, thus come before employment history? How should I summarize past jobs/functions/roles at my previous employers under the 'employment history' section? (Bulleted lists of functions/responsibilities, paragraph style explaining what I do/did, a hybrid of bulleted lists and paragraph style detailing my successes and accomplishments, something else) Should I include a cover sheet? What should it contain? I realize that I'm already asking for you to divulge all of your resume secretes, but I'd be interested too in seeing any resumes that your particularly proud of, and don't mind sharing of course. I'd post mine now, but it's not quite ready for public consumption, hence this lengthy email :) Thanks in advance! I really appreciate any (good) advice yall may have to offer! -Will _______________________________________________ Houston mailing list [email protected] http://mail.pm.org/mailman/listinfo/houston Website: http://houston.pm.org/ _______________________________________________ Houston mailing list [email protected] http://mail.pm.org/mailman/listinfo/houston Website: http://houston.pm.org/
