Recently, I have been hearing a lot of resentment about job descriptions. I’ve heard discontent in a recent client training session. I’ve heard it in the last couple of recruiting presentations I’ve attended. And, the disdain from jobseekers is pretty standard fare. Can you remember the last time you did a search on Monster, Indeed, CareerBuilder, whatever, and was pleasantly surprised to read a job description that captured your imagination? I’m not saying that it doesn’t happen, just that it is extremely rare. Such being the case, I made a personal challenge to myself to decode the job description code. I wanted to figure out the best possible way to create job descriptions that convey all of what HR wants to say but, still manages to capture the attention of the jobseeker.
I must admit that after meditating on this problem, my head started to hurt. However, I soldiered on and came up with a few alternatives that I hope will become a trend. One can hope…
Option One: Succinct and sexy
Have you heard of JobGram? I really like the concept of what they do. Instead of writing a job description for you, they make it into an infographic. How cool is that? At a glance, the jobseeker gets the idea of what HR wants to convey. Plus, since its essentially a pretty picture, it works for passive candidates who have a much shorter attention span than active candidates.
Here is an example of a Job Gram!
Option Two: Gamify It!
Check out this Google search:
Surveying the results, here is an excerpt from one of the most popular 2012 blog posts regarding “java.”
JSF 2, PrimeFaces 3, Spring 3 & Hibernate 4 Integration Project
And finally, the most popular Java Code Geeks post for 2012 is this tutorial combining a number of enterprise Java technologies such as JSF, PrimeFaces, Spring and Hibernate. Honestly, this was a bit of surprise to me, but I think this shows how big is the adoption of these technologies by the Java developers world.
Intellij vs. Eclipse
Another battle, this time the battle of IDEs! All developers have their favorite IDE and this article explores the differences between two of the most popular in the Java world, namely Intellij and Eclipse. On the same note, check out What’s Cool In IntelliJIDEA Part I and Eclipse Shortcuts for Increased Productivity
Why I will use Java EE instead of Spring in new Enterprise Java Projects in 2012
Another article that generated a lot of heated arguments. The eternal fight between Java EE and Spring framework. The author lists the advantages of both approaches and explains why he opted for Java EE.
I notice that several of these posts were debating the virtues of one java-related tech verses another. Why not create a landing page where java developers can debate the issues of one technology over the other with the most intriguing comments winning a prize of some sort? The contest could be judged by your CTO and to join in the fray, one must login to the landing page with your LinkedIn account. (Of course, you get where I am going with this?) Recruiters can review the comments made on the page as well as the LinkedIn profile of whomever said it. Recruiters could then have an excuse for following up with the person(s) involved in the discussion; even if they did not win the prize. Make sense?
If you like the idea of this, I have another search you might want to try.
Option Three: Create Your Own Monster (job descripton)!
Okay, this concludes my rant on the issue. I would like to hear your comments. What do you think?