|
|
|
|
|
by jnorthrop
1711 days ago
|
|
I agree with your sentiment. I was 51 when I last applied for a job at a new company. Initially I was getting very little interest in my resume. Then I cut out the first 10 years of my career from my resume (and LinkedIn), and downgraded the oldest position listed from a Senior Lead to just a developer -- essentially making me appear 40 instead of 50. Within a couple of weeks I started getting responses. And it is not like my work from 1990-2000 wasn't valuable. I worked on a complex large scale analytics system in the early 90's and migrated to large scale web-based applications in the later half of the decade. I'm proud of that work and have some interesting lessons and stories from that time period, but they are telltale of my age and were working against me. |
|
Senior developer positions are more common now, in part from title inflation but also the rise of more complex online interactions and businesses. By cutting the senior bit out of your resume, you no longer look overqualified for the more numerous junior / "regular" developer positions.
While your work from the 90's is likely very interesting, for many companies the soft skills and lessons learned will be more applicable to whatever role they have available, best included as a summary.
I promise that most hiring managers aren't going to read a 10 page resume, or even a 4 page one. 9 times out of 10, they just want to answer a simple question: should the team take time to find out more about this candidate? If the first page of your resume doesn't answer that, it likely won't make the cut.
On a final note, "30 years experience" really isn't a great sign. I have indeed worked with the type of person who has basically had the same experience over and over for 30 years, not growing, learning new technical or leadership skills, etc. That is totally fine for many positions, but it is mark against them for many others.