Larson, I totally agree about the skills list. Just listing a skill without telling me:
1). what you did with it 2). when you did it 3). what level of proficiency you performed this skill is meaningless. I like to see a "3D resume." If you mention "I've worked within a large data center environment," that tells me nothing. Large to you, may be small to me. Tell me "I've worked within a large data center environment with 1200 linux servers supporting the following services: apache web hosting, DNS, qmail, load balancing, Oracle, etc." On top of that, I want confirmation that the candidate's role was to support each of these services not just that the candidate has breathed air in the same room where these services could be found! I know that sounds obnoxious but I really don't mean it to be. I read resume after resume where people list skills in a skills list that are found "around" them but for which they have no real-world experience. If that comes out in an interview, it's not a good reflection on the candidate. Make life easy for me and I'll be more than happy to talk to you about a job! Try to see things from a recruiters perspective... You have to give depth to your resume (i.e., how many, how long, at what level, etc.) for us to really make sense of your resume. As I've said, I personally really dislike cover letters but maybe that's just me. I want it all wrapped up in a simple package (i.e., the resume). I have only had a few people do this, but I really like getting a side-by-side breakdown of what I asked for and what they've done. It shows me that they have read the job description and can make meaningful connections between their skills/experience/knowledge/attitude to what I need. I don't care if this is in the form of a table right smack at the top of the resume. I'd take this over a skills list any day of the week! Todd > -----Original Message----- > From: Larson Rider [mailto:[EMAIL PROTECTED] > Sent: Monday, February 06, 2006 11:21 AM > To: Todd Cranston-Cuebas; Adrian Howard; L-Perl-Jobs-Discuss > Subject: RE: should a resume have a "Reason for Leaving" > line? general resume assessment request > > Todd. excellent points. I agree, > > The synopsis I speak of is a very short paragraph telling the > reader what they are about to read and guiding them to your strengths. > > One pet peeve I have about resumes is when a technology list > is used and the technology is not re expressed in the resume. > Makes the list practically worthless. I do not recommend > technology / skill lists. Put them in each job is generally better. > > I have found that most people do not know how to write a > cover letter. I suggest writing one like a head hunter's > presentation: tailored just to the position it's for and > directly to the point. > > Here is a sample using my formula when I present a candidate: > > Hello _______, (Use name of person you are sending it to, > whenever you can get it) > > Attached is my resume for your Perl Test Automation need. (Or > Perl need, for less specific presentation) > > I have a Masters in __________ (name school is renowned), 13 > years total experience and 7 years in Perl with the last 2 > years using Perl for Test Automation. > > I found your position particularly interesting because you > are employing Perl to do _______________ at a greater level > than most companies that I have seen. (say something > technically interesting about the job, specific is good) > > I have decided to change my career path for mostly > contracting to full time employment. I have been in a string > of startups that lost funding and now I am looking for a > company where I can make a significant ongoing contribution. > > Best regards, > > > Name and contact information > > ***** > > That's just a sample of a style that has served me well for a > very long time. Hope it helps. > > Lars > > > >
