4 ms·
You need to display your skills, period. I have hired over 20 developers in the last 6 months and received over 30 resume for every 1 good resume. I did not hav
by csel 16y ago
You need to display your skills, period. I have hired over 20 developers in the last 6 months and received over 30 resume for every 1 good resume. I did not have time to read everyone's work experience explanation either on the first run. I could only spend less than a minute on a resume. So we rely a lot of the Skills section.
- Put it on a table. Include how many years you have been working on a specific skill. It will be helpful to list when was the last time you used that skill. So that is the first cut.
- After going through the skills section, we look at the Employment history and what you actually did with those skills that you listed. Then you get a telephone interview and possibly invitation to an in-person interview.
You are not going to get into the interview list if the HR person does not know what you are skilled at. Trust me, they are not going to use the interview as a discovery session. They don't have time for that, especially when there are other candidates who were clear in displaying their skill sets.
- hapless 16y agoYou rely a lot on the skills section, and you have an HR person doing the initial filter. Your process is exactly what causes people to fill resumes with buzzwords. "I touched a prior version of fizzbuzz, once, at 3am" is still going to put fizzbuzz on the resume, so your HR person doesn't chuck it in the circular file. This is the kind of process that guarantees a lack of clarity on the part of the applicant.