re: 5 IT Resume Blunders To Avoid
I think the situation is a little more complicated, both about the work experience and the "leadership" language. One of the problems I have in recruiting is that every good developer (and some not-so-good ones) wants to be a leader. But what I need most of the time is a good developer who's quite happy following a leader. As for the work experience, the author seems to be recommending that you attempt to hide your embarrassing 25 years of experience in IT. First of all, that will only work if you also don't put down the date of your college degrees, which makes it pretty apparent that you're trying to hide something. Focusing on the content of recent, relevant experience, as the author rightly suggests, and eliminating the detail for any positions that are no longer relevant, should impress regardless of the long tail. One thing that really doesn't work is to send out a resume packed with details about your entire work history and assume that an employer will look at it and say, "Well, they did all of this so I assume they can do what I want too." As you get older, it is true that you are less likely to be hired for anything outside of your existing skill set. But skill sets can last a long time; just ask a COBOL programmer.