> why do you have your work experience dating back to the 80s?
I kind of disagree. It’s not like people are printing out or even reading back that far. May as well include it, but certainly don’t expect people to read it.
I’m currently hiring and reading a lot of resumes. I rarely read past the first 2-3 pages, but sometime when I’m curious go back to learn more about career path. Has someone been programming for 30 years? Or started as a dba or a support tech?
I think it depends on the risk of including it. If you worked for an embarrassing employer or maybe don’t want people to guess your age, remove old stuff. But otherwise, I suggest just spending more effort on making the first page relevant.
I'm not an expert but your implicit premise that it's OK for a cv or resume to have multiple pages surprises me.
One page! Put the most recent relevant stuff on one page and send that. I don't agree with the idea that it's OK to include more info because people don't have to read it. They do have to read it because it might contain a red flag.
Every word you type is making work for someone, and if it's not then why write it?
With digital files, I don’t think it makes more work. Different people want different things and it’s hard to know who will be reading.
For my resume, I add on new items after each position or paper or new thing or whatever. So I’m just adding on new sections every few years. If I was starting fresh I probably wouldn’t write pages and pages.
I agree that the first page should contain all essential information. But as for the extra pages, people only read if they have some reason.
The issue what that is I have no idea what his focus is and how does it help you determine whether I would be a good hire for your company to know I did C (and FORTRAN) in the 90s?
I would like to know if you did C or FORTRAN in the 90s because it’s different than if you were building houses.
Someone who has been programming for 25 years, starting in the trenches is different from someone who changes careers in the 00s and learns programming.
And I prefer some context to know what someone means as if it was just a line for “FooCorp 1995-2000, Programmer” does that mean FORTRAN or excel macros?
How I designed systems in the early 2000s when procuring hardware had large up front costs including building an on prem server room with raised floors and non water fire suppression systems is different from how I design systems now when I can create my entire server infrastructure by using a text editor and creating a yaml file.
The considerations I take about scalability, RTO vs RPO and my entire system design and process decisions change when I have unlimited capacity and the ability to scale to zero.
My experience programming in 65C02 assembly in the 80a doesn’t make me a better developer today.
For what it is worth. I disagree completely. Your programming in assembly in the 80s made you what you are today. I am actively in a hiring role, and interviewing seemingly constantly. I want the full job history. My team and I read the complete resume.
I kind of disagree. It’s not like people are printing out or even reading back that far. May as well include it, but certainly don’t expect people to read it.
I’m currently hiring and reading a lot of resumes. I rarely read past the first 2-3 pages, but sometime when I’m curious go back to learn more about career path. Has someone been programming for 30 years? Or started as a dba or a support tech?
I think it depends on the risk of including it. If you worked for an embarrassing employer or maybe don’t want people to guess your age, remove old stuff. But otherwise, I suggest just spending more effort on making the first page relevant.