Exactly. When I'm reviewing resumes - I _really_ don't care (or even want to know) that you flipped burgers during one summer break in college in the '80s or that 15-20 years ago you wrote web backends in PHP or maintained logistics software in Cobol. List your last two or three jobs - selectively highlighting/editing(and, if your referees will go along with it, embellishing them) them to emphasis the specific skills and experience needed for the role you're applying for.
While a "35 year career in Silicon Valley" might sound impressive to some people (and perhaps rightly so), as a hiring manager I probably don't care about any projects/technologies you worked on in 1983... I want to know whether you can do the project I need delivered now. Tell me what you worked on last year and in the last 5 years - skim over or leave out the rest.
(If you're dealing through recruiters instead of directly with hiring managers, you've got a different set of problems - the solution to which is probably ignore the recruiters and don't play that game - surely a 35 year career has left you with a network that can bypass those rent-seeking gatekeepers?)
While a "35 year career in Silicon Valley" might sound impressive to some people (and perhaps rightly so), as a hiring manager I probably don't care about any projects/technologies you worked on in 1983... I want to know whether you can do the project I need delivered now. Tell me what you worked on last year and in the last 5 years - skim over or leave out the rest.
(If you're dealing through recruiters instead of directly with hiring managers, you've got a different set of problems - the solution to which is probably ignore the recruiters and don't play that game - surely a 35 year career has left you with a network that can bypass those rent-seeking gatekeepers?)