71
Is a skill based resume a killer?
My job is about helping others in the workforce. Occassionally I get a client whose field is outside my wheelhouse and I can only take an educated guess on the details of that field. Recently I recommended to my client (a software programmer) that he consider changing his chronological resume to a skill based resume.
My reasoning is that some of his jobs covered similar duties so rather than saying he had 5 years experience in X program at this place and another 7 years at that place I was recommending that he combine them to say he has 12 years experience in X program total . Additionally, it would streamline his resume to less than 2 pages and make it easier to read.
However, he posted on a couple of job boards and the feedback he received is that a skill based resume looks like he is hiding something. It is true he has been out of work for the past 3 years and I don't recommend advertising that right out the gate - but that isn't something I considered in my recommendation.
So HR (especially in IT) - does a skill based resume raise red flags? When should I consider this or dump it?
is it a resume killer. If I had to pick: Yes. IMO, it is because that is not what most applicants use, therefore it is not what most reviewers expect to see. I prefer to help people create a truthful, but mindfully edited resume in the format of a reverse chronology format. Sometimes the actual content may use the format to highlight things that are not actually that chronological. The reviewer has merely ASSUMED that and already seen the bits we spotlighted. The result is that the candidate comes across as the best fit that they can and the reviewer often has some follow up Qs that warrant a call or interview.
PS, barely any job would call someone with 12 years over 5-7 unless they state it explicitly. If anything, that's a liability in itself.
PS, IMO a resume should be no more than 1 page. This is not the same as less than 2. I'm ruthless!
Hats off to anyone who can decipher the countless 3-letter acronyms on a developer's resume. Huzzah. LOL
As a Software Engineer... sure I want to know your skills, but I REALLY want to know how you applied them to contribute to your projects in a meaningful way.
Also, I know I am often looking for where you worked and how long you worked there. When you organize it in a task based manner it is like asking me to do all the math to put your entire work history together.