Identifying Design Patterns in Resumes

Just got an email from a person who calls himself a Senior Java Developer. Two out of five pages were devoted to  describing his skills. Below is an extract from the Skills section:

Java 2 (J2EE, J2SE) rich operational experience
JDBC 2.0. rich operational experience
EJB considerable operational experience
SQL rich operational experience
JSP rich operational experience
JSTL rich operational experience
Servlets rich operational experience
Struts rich operational experience 
GWT considerable operational experience
Spring framework rich operational experience

The list would go on and on. I didn’t even need to interview this candidate – it’s clear that he can’t be senior.  He already violated the Don’t Repeat Yourself (DRY) design pattern.  I can imagine what his code will look like…

8 thoughts on “Identifying Design Patterns in Resumes

    1. That’s right, I was thinking of a loop too.🙂 Why not just group Skills by skill level? it would take a lot less space. I hope this resume was created by some HR rookie (I got it from an agent, actually), otherwise this person shouldn’t even write code.

  1. if (x == 1) { y = “foo” }
    else if (x == 2) { y = “foo” }
    else if (x == 3) { y = “foo” }
    else if (x == 4) { y = “foo” }
    else if (x == 5) { y = “foo” }
    else if (x == 6) { y = “foo” }
    else if (x == 7) { y = “foo” }
    else if (x == 8) { y = “foo” }
    else if (x == 9) { y = “foo” }
    else if (x == 10) { y = “bar” }

    1. What I like in your example is that you use curly braces even if there is just one operator there. Ignoring the braces may lead to the hard to find bugs if the code wil change in the future. But what happened to the semicolons?

  2. Many of the items listed are just meaningless to me. How can one have “SQL rich operational experience”? You can have rich operational experience of motorbike, if you’ve been riding it for years. But regarding SQL, one would better say “Worked with Oracle/MSSQL/MySQL for X years, hands-on experience of ANSI SQL, knowledge of PL/SQL (wrote a lot of analytic stored procedures), deep understanding and experience in query optimization in Oracle and DB2, basic DBA skills (backups /recovery, instance memory tuning, RAC)”. That would be something meaningful and useful.

    What do you think?

    1. I don’t know. There is a chance that SQL made him rich or enriched his life and gave it some new perspective. It’ll remain an unsolved mystery.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s