[QUOTE=wolfman]
I always post this in these threads, but anyone who has a one page resume and works in IT is really hurting their chances. IT is so specialized that recruiters and hirers really want to know the details of what you have done since “Worked with Solaris, Oracle, Tomcat,SUN1, ANT Hibernate, Java, J2EE, on production systems” covers an infinite number of possibilities. You need details of what you have done, for how long, and for each job, so the Manager can see how relevanat what you have done really is. The previous quote will get you about 9000 calls from sleezy recruiters, and thrown in the trash by any Hiring manager or good recruiter.
A resume custom tailored to the job you are seeking should still be about 3 pages, if you have 10 years experience. And if you were a consultant with a bunch of 3 month contracts, it can get ugly.
[/QUOTE]
I disagree. Then again, I work for a small company that doesn’t deal with sleazy recruiters. We keeps our job postings short, sweet, and to the point, and it would be nice if our candidates did the same.
Allow me to quote myself from a previous thread:
[QUOTE=black rabbit]
…
Then a one sentence objective that relates specifically to the position at hand, avoiding phrases like “to provide excellent customer service.”
Then a (concise!) bulleted list of post-secondary positions with the following info: Employer, final title, dates, top three accomplishments.
Then a (concise!) list of post-secondary educational accomplishments and/or certifications, with the following info: Institution, degree/cert received, major, and date received.
Pimply-faced youth may substitute a (concise!) list of functional accomplishments if their relevant work experience isn’t extensive, and flush out the educational side a bit with interesting (but relevant) projects, etc.
…
It’s the format I’ve always used, and I’ve never been turned down for an interview in my professional life.
[/QUOTE]
I care less about whatever particular alphabet soup you’ve touched during any given five minutes of your career then I do about the broad outlines of the projects you’ve worked on, your role in them, and what you learned from the experience. If there are any vitally important acronyms that I feel you should know something about, rest assured that I’ll ask you about them in the interview.
There’s no way that ten years of experience should take up two pages of that, unless you’re hopping jobs every twelve months, which would indicate a bigger problem.