Not saying this applies to you, but for print format I would say: ideally stick to one single page. After 5 years working in software, evolving through different tech stacks, I have yet to find a reason to have two pages in my CV, for a few reasons.
My experience from 5 years is only tangentially relevant anymore. No one cares if I worked a lot with jQuery 5 years ago. That means I don't need to write in detail about old jobs
If I would write detailed descriptions of each job, I would repeat myself a lot.
Most recruiters are not skilled enough to understand or care about long detailed resumes. They go with labels and buzzwords.
Initial interviews always discuss my CV anyway. I always get questions on the line of "So you listed ; tell me more about it; how did you feel working with it?".
Everyone knows the meme that says no one ever goes to the second page on Google - the same applies here. It's fine to add an extra page with interesting information, like side projects, hobbies, list of conferences where you spoke, etc, but everything relevant to the job you're applied should fit in the first page.
Note: you should probably add print-friendly CSS or a download to your resume in PDF.
Not disagreeing with your points but I have seen some people prefer to have relevant projects listed as well. Wouldn't adding projects add at least one more page?
Yes, they are definitely relevant. But it's all about picking what information deserver prime CV-estate. I don't think your comment goes against what I said.
With that said, if you are the type of guy that does 10 things at once - e.g. you have a full-time programming job, then a part time tutoring, then you organize the local dev meetup, talk in conferences, contribute to open source, etc, maybe you really can't fit everything in a single page while still having enough detail for each entry. But from my experience, 9/10 people don't have such busy lives.
I'm a developer-turned-business owner who loves to explore the right tools for the job. I enjoy writing and documenting my journey. I use code as one of the tools to solve real problems.
Definitely agree with all of your points! I'll work on the print/PDF version. I initially made this to be a downloadable PDF, but after a long time of tickering, it never really worked how I wanted it. But I'm glad you confirm that it's important enough to actually go through with it.
Thank you for your in-depth comment.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not saying this applies to you, but for print format I would say: ideally stick to one single page. After 5 years working in software, evolving through different tech stacks, I have yet to find a reason to have two pages in my CV, for a few reasons.
My experience from 5 years is only tangentially relevant anymore. No one cares if I worked a lot with jQuery 5 years ago. That means I don't need to write in detail about old jobs
If I would write detailed descriptions of each job, I would repeat myself a lot.
Most recruiters are not skilled enough to understand or care about long detailed resumes. They go with labels and buzzwords.
Initial interviews always discuss my CV anyway. I always get questions on the line of "So you listed ; tell me more about it; how did you feel working with it?".
Everyone knows the meme that says no one ever goes to the second page on Google - the same applies here. It's fine to add an extra page with interesting information, like side projects, hobbies, list of conferences where you spoke, etc, but everything relevant to the job you're applied should fit in the first page.
Note: you should probably add print-friendly CSS or a download to your resume in PDF.
Not disagreeing with your points but I have seen some people prefer to have relevant projects listed as well. Wouldn't adding projects add at least one more page?
Yes, they are definitely relevant. But it's all about picking what information deserver prime CV-estate. I don't think your comment goes against what I said.
With that said, if you are the type of guy that does 10 things at once - e.g. you have a full-time programming job, then a part time tutoring, then you organize the local dev meetup, talk in conferences, contribute to open source, etc, maybe you really can't fit everything in a single page while still having enough detail for each entry. But from my experience, 9/10 people don't have such busy lives.
Definitely agree with all of your points! I'll work on the print/PDF version. I initially made this to be a downloadable PDF, but after a long time of tickering, it never really worked how I wanted it. But I'm glad you confirm that it's important enough to actually go through with it.
Thank you for your in-depth comment.