A job posting is the first filter a candidate must (convince themselves that they) pass. It is also the first filter the candidate applies to your organization. One thing I’ve picked up on recently in the job descriptions that pass by me is how many of them list specific tools unnecessarily.

For instance,

  • Instead of having ‘linux’ on the job post, put down ‘unix.’ Do you really care if they have never used linux but are a Solaris god?
  • Instead of having ‘cvs’ (or ‘subversion’), list ‘version control systems’
  • Web automation tools instead of QTP
  • etc.

Sure, some positions might require a specific tool, but unless that need is explicit I think it is better to list the generic type or class of tool. After all, if they know what they are doing, and not just the specific product then they just need to adapt their knowledge to the syntactical nuances of the other app.

In tight markets (like Toronto’s right now) you don’t want to artificially limit the number of people who apply, nor because they do not exactly match the profile you advertise or because they do not want to work with the technology you are using. The second problem is unfortunately one you will encounter more as the seniority of the role you are hunting for increases.