This week we have a four page Java developer resume that needs help in a bunch of places. Again, I’ve redacted the content to protect the innocent.
SUMMARY
The resume started with a SUMMARY. If you read my resume articles, I greatly appreciate summaries.
- I am a Sr. Java Developer with experience directly managing developers.
- He has extensive experience in the design and development of multi-tier applications using Java, J2EE, $LISTOF15TECHNOLOGIES.
I advise my Resume Raiders clients to avoid the use of first person (“I”), and I further advise any and all humans to never refer to themselves in third person. Using both within adjacent bullets highlights the issue.
As I’ve stated before, we can use implied first person on a resume, where “I am a Sr. Java Developer with…” becomes “Sr. Java Developer with…” and “He has extensive experience in…” becomes “Extensive experience in…“. These types of errors will be forgiven by many screeners and wouldn’t alone be an offense resulting in a deleted resume, but they get the reader to start leaning that way.
The second bullet listing of 15 technologies is another poor choice, particularly when many of these technologies were somewhat specific and rather niche. To say someone has extensive developing apps using Java, Spring, and Hibernate might be easy to believe. When you throw obscure technologies like R or Lisp into the mix (as this person did), it starts to sound like a bit of Buzzword Bingo.
The summary continues…
- Responsible for leading a team of four developers in developing Java based applications.
- Developed web application using $SERVERPRODUCT and $STANDARD compliant $COMPONENT using Java.
- Used $IDE as IDE tool to develop the application and $BUGTOOL for bug and issue tracking
We’ve quickly gone from a proper SUMMARY into a list of specific individual accomplishments more suited for the EXPERIENCE section. The intent of the SUMMARY isn’t to list several details so much as to provide an overview of what is to come.
The first bullet listing leadership is appropriate for a summary, but it should be generalized. We could take the top three bullets and write a pretty good summary: “Senior Java Developer experienced in both building web applications and leading teams of up to four developers.”
You certainly don’t need to reference an IDE in a summary, and it’s a bit redundant to mention that you used an IDE as an IDE or a bug tracking tool as a bug tracking to0l. That’s what the tools do – we know that already.
SKILLS
Next comes a list of 48 technologies divided into three columns of 16, bulleted and in alphabetical order. There are several problems with this.
For one, the bulleting and use of three columns makes it take up about a half page where five lines would suffice if listed using commas. Let’s assume we’re not grading our resume on space efficiency. What else is wrong?
Listing things alphabetically tells the reader absolutely nothing about your skills, because this method places no weight on any individual skill. You could be the world’s most prominent expert on XML, but if you list things alphabetically the reader might never even see that term. Writers should list technologies based on expertise and knowledge from most to least, where the first technologies listed would be considered primary skills and the last ones might be things you’ve been exposed to infrequently.
CONCLUSION
The sad part is that the rest of this resume was actually pretty good. The experience section had some solid accomplishments and a somewhat impressive work history. Hopefully the first impression wouldn’t cause a screener to jump to a conclusion and reject a candidate before getting to the good parts.
The lesson for resume screeners is to try and give the benefit of the doubt with the early material so you don’t miss any positive signals hidden in the end. The lesson for resume writers is to remember that screeners are reading top down, so make sure the material at the beginning is effective in keeping our attention.
| Reference: | Worst Resume: Bad Starts from our JCG partner Dave Fecak at the Job Tips For Geeks blog. |
Excellent article Dave. Definitely an eye-opener for the newbies writing resumes.