html version is horribly aligned, fyi. apart from containing a litany of information... a scary amount of information... I believe the rule of thumb is that a resume/cv should be no longer than 1 page... but that as we get older... we have that much more time to account for... but still more than 1 page... my experience is that most recruiters usually chuck the hefty, lengthy resume/cv... in lieu of the crisp, concise, 1 page resume/cv... but that's just me...
No, I say stick with two. You just can't get enough relevant info onto one page, at least not for a programming job (where there's no associated portfolio or anything).
I know that when I edit resumes/cvs for clients... the turnaround is supposed to be one page... even if shrinking the font and widening the margins... It used to be that 2 pages was accepted... then people with 2 pages, pushed it to 3... and to 4 and so on... justifying the increase with extensive experience... which in my opinion, is kinda redundant at the time of the interview... I mean, a resume/cv should have some meat... but if it is explicitly detailed... how do you interview with any kind of elaboration?
I went down that road once, and it was an unmitigated disaster. There just wasn't the space to get into what I did at former jobs, so it just turned into "I worked here and there and this other place" which doesn't tell anyone much of anything about what I actually did, or what I'm good at. Whereas even with the details, there's still plenty of ways to go into further detail in the interview, or talk about how you did stuff, or whatever.
Like I mentioned, this is largely because there's no space for a portfolio; if you say "I designed this site" or "I took this photo", I can go to that site or look at that photo and see what you can do, so you don't need to say much more. But if I say "I worked at NITI", that doesn't tell anyone anything.
Anyway, the co-op department at Waterloo suggested two-page resumes for most CS people (not for first-year co-op students, for instance, but at least for me in particular when I had my resume critiqued a couple of years ago), so it's not universally shunned yet. It's nice if you can manage it, but I don't think Stirling's resume would fare all that well.
Well, as this is a second version of my CV, I don't see why I can't take Nancy's advice and try to make a 3rd version which fits on one page. It would take some major reorganizing, but it may be doable.
Touche, I guess. But if you feel like it's just not informative or eye-catching enough, don't waste several months of your life like I did by only giving out that version. I don't think anyone looking for someone with your skills will discard your resume because it spans two pages.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2005-06-28 12:11 am (UTC):) Nancy
no subject
Date: 2005-06-28 02:55 am (UTC)no subject
Date: 2005-06-28 03:45 am (UTC)no subject
Date: 2005-06-28 03:50 am (UTC)no subject
Date: 2005-06-28 04:14 am (UTC)Like I mentioned, this is largely because there's no space for a portfolio; if you say "I designed this site" or "I took this photo", I can go to that site or look at that photo and see what you can do, so you don't need to say much more. But if I say "I worked at NITI", that doesn't tell anyone anything.
Anyway, the co-op department at Waterloo suggested two-page resumes for most CS people (not for first-year co-op students, for instance, but at least for me in particular when I had my resume critiqued a couple of years ago), so it's not universally shunned yet. It's nice if you can manage it, but I don't think Stirling's resume would fare all that well.
no subject
Date: 2005-06-28 04:54 am (UTC)no subject
Date: 2005-06-28 06:10 am (UTC)