This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I think for kids in college and only a few years ago, 1 page is right. Beyond that, more page are fine, especially since these days people tend to have many more jobs than they did 30 years ago when 1 page was the norm. The more infomraiton, the better (with some obvious extremes, but most people don't get too excessive). --Mark email@example.com
I've never hired anyone or been in the position to hire people, but this is what I've heard. One full page or Two full pages. Any more is too much and half pages don't look good. No one is really going to read your 5 page resume when most won't even read your one page resume with any scrutiny. So if you need more than one page, make it two, if you need more than two pages, you need to condense something. Remember, no one gets a job from the resume alone. It's just a way to get an interview.
All: I am of the opinion that for recent college graduates - 1 page is enough - and even then, you may have trouble filling it up. The problem I see - is that college students rush the process and try to "fill up" the page with irrelevant items like health and hobbies - or they throw their references on the resume. I am also of the opinion that a resume should be no more than 2 pages long. If longer, the third page should list company name/location/dates/ your title. However, the first two pages should be crammed with your education - and description of projects. You should include under each company - the technical environment you worked in. Also, you should leave off an objective - just say you are an experienced programmer - experienced in full product development lifecycle. College students should leave the objective on - because it is expected at this point in your career. In today's market - a 2 page resume is fine - not a big deal. No one cares 1 page versus 2. Just make sure you include relevant information. John Coxey (firstname.lastname@example.org)
Originally posted by Michal Harezlak: I am a strong believer in one-page resumes. What do you think?
Don't get hung up on whether the resume should be one or two pages. I look at dozens every week, most hiring mgrs with a pile of resumes to review will spend no more than 10 sec. on the first pass looking over you resume. It has to tell them what they're looking for easily and quickly or it'll likely go in the reject pile. That means nothing smaller that 10 pt type, use bullets to highlight areas of expertise, or bold headings to direct attention to what's important. A skill set list at the top is best because a hiring manager or recruiter can see quickly if you have the skill set needed. Assuming that you pass the first sort, you then need to have enough detail about what you've done and the tools you've used to further qualify you for the position. Although I've seen a few resumes which would qualify as books (not desirable), I've probably passed on more because they didn't give me enough info to tell if the candidate was qualified or not. Two page resumes are the norm.
Writing a resume with over 10 years of diverse experience, I was having trouble covering all the important stuff in two pages. Recalling how the world brightened when a one-page resume showed up in the piles I had read in the past, I decided to try to make a one-pager myself. The results were good, and after determining what was important enough to go into the one-pager, I had a better understanding of how a potential employer would see me. I've got about 20 years of experience now, but the next time I'm serious about preparing a resume, I'll probably prepare both a one pager and a two pager. Whether I send out the long or short version, I'm sure the exercise of deciding what is important enough to say in the one page version will serve me well.
Joined: Feb 16, 2001
Can u please tell me that what objective should I write in my resume. I am a fresh college graduate having no experience.
I like the double-barrel approach of keeping a 1-page resume for seeking very specific project types, as well as a 2-pager to list your full-skill base. Particularly of late, with so many development skills required, it is eay to reach over-kill, when you list every single technology that has touched each of your recent projects. Some "thinning-out" for specific job- or project-types can be titled "A Partial List of Skills ..." Feedback invited - an interesting, relevant topic.
------------------ Tom Hennigan Sun Certified Java 2 Platform Programmer
Tom Hennigan<P>Sun Certified Java 2 Platform Programmer
Somthing which a lot of resum� writers seem to ignore is that the format and the content should depend not only on the particular job (if you are applying for a particular job), but also on the type of employment you are looking for. As a broad generalization, a resum� for a short-term contract position is a very different thing to a resum� for a long-term "permanent" position. Anyone looking to employ a contractor wants, above-all, to know about the skills and appropriate experience you have right now. For a permanent position current skills are not so much of an issue, but vitally important is how well you will fit in with the company culture and how you work with existing employees.
I do review resumes and hire people. I strongly believe in detailed resumes (mine is 3 pages long). For college kids: If you have more information that fits on a page, don't worry about going over one page, The school that I regularly interview has a strict requirment for one page resumes. Because of that we end up getting resumes with margins set to "0" and fonts set to size 8. That's just makes it worse. I tend to ignore the formatting because I am an alumni of that school and know their weird requirments but other people would probably prefer to get two pages.
I have been involved in quite a bit of hiring and I would be surprised if anyone could convince me in one page. Two minimum, four maximum. Go real easy on the personal information stuff. An amazing number of resumes have a personal information bit that says they like eating out and listening to music. Well that puts them in the same basket as 98% of humans. The resume from the chap who is working opposite me right at this moment said he was a big James Bond fan. Excellent conversation started in interview once you have everything else sorted out. Marcus
Exactly true, I was doing hiring jobs throughout last year. To be frankly, I started to read the resumes only when I meet with the candidates. Before the interview, I only spot it and don't care how many pages.
I would have to agree with what a few other people have said, the resume is just a means to get in for an interview. In my previous job (before I even started in IT) I had quite a few chances to interview and hire people. In looking at resumes and trying to decide who gets called for an interview one of my biggest criteria was spelling, grammar, and neatness. If I got a resume with a lot of spelling mistakes or poor grammar then the first reaction was to assume they didn't care. My feeling is that the resume shold be a clear, quick, and easy to read picture of who you are and why they would want to interview you. One or two pages is not of as much importance as content. If the resume you send in is well presented and can be readilly understood then they can assume that you are a clear spoken, level-headed individual that can express themself well. And you have a good chance of getting called in for an interview. It is the interview (or minutes before) where your resume will probably get it's first good reading. If you make use of bulleted sentences, bold headings and the like then you can almost direct the course of the interview. they will mention things that jump out to them or that they remember. Have answers prepared for those questions/topics and you have half the battle won.