Tools Experience

Bob is often asked in interviews what it is he'd like to be doing. Having done many interviews on both sides of the table, Bob knows that the thrust of the question is most likely Here's the tools we're using - interested?. Many companies use this to attract and hold workers, and that's fine. But having used so many different tools in his professional life, Bob is convinced that a tool is just that - a tool, and no one tool is so much better than another that it overcomes the short-comings of the rest of the job.

However, there still needs to be a listing of the products, languages, tools, and such that Bob has used in his professional life:

There are certainly more technologies that Bob has been exposed to, but these are the ones that have formed the cornerstones of the projects he's been doing for the last couple decades, or so. While we could list tools like Lotus Notes, DB2, Visual Age for Java, and a host of others, Bob's level of expertise in those tools is only as a casual user, and not as a serious developer.

Which bring us to a point. We have found that there's a danger in focusing on specific tool experience. And it is often seen at it's worst in the interviewing process. When it comes to most resumes, most people load up on the things that they've only been exposed to for a short time - just to make the resume look better. While it's not immoral, not quite ethical, either. We have chosen to list only those things Bob has intimate working knowledge of. So his resume list is correspondingly shorter. And that is the crux of the problem - others with much less real experience will appear to be better qualified than Bob.