I've recently come to learn that three to five-page resumes are common (and possibly standard, especially for contractors) for developers, so I'm overhauling mine. I'm relieved to no longer have to jam everything into one page. For now I'm just shooting for two pages, but whatever number, this makes for new considerations...
One is that I've also recently learned that capabilities (languages, software, technologies) should be on the first page, and even first, before experience.
But THAT means that my experience will need to span from the bottom half of page one to the top half of page two, followed by education, awards, clients, etc.
My question is, is it awkward to have experience spanning multiple pages? I've always felt that experience should come first, but I guess that was an assumption.
I see TONS of examples of developer resumes that are just one page, and I've seen experienced friends' resumes where TONS of information is crammed all on one page. But I thought a resume was a summary, and that non-100%-relevant information should be omitted in favor of more relevant information for a resume (in contrast to a CV where nothing is summarized).
I should note that that recruiter may be as unclear as I am on this. I did ask about resume vs CV, and he didn't answer that directly, but continued referring to my application material as a 'resume'.