Hiring NIGHTMARES…it can happen to YOU24 Apr
At a recent gourmet cooking club party with friends, I asked the group if they had ever made a bad hiring choice.
As a former manager myself, I knew the question would strike a nerve. Even after you extricate yourself from the mess caused by a poor hire, the memories never leave. And we’ve all been there, from the programmer who blows you away in the interview with her knowledge and charm but who, once on the job, doesn’t even know how to do the most basic of tasks, to the help desk tech who seems so astute in the interview but whose on-the-job social skills lead you to believe he was raised in a cave somewhere.
In response to my question, my friend Tara submitted the following hiring horror story. Tara is a former IS manager for a small company in Aston, PA. Other names have been changed to protect the incompetent. Here’s Tara’s story:
The background
The cast of our tale includes one overloaded manager doing programming, managing IT, managing a subcontractor or two, and just for kicks, co-managing a new system implementation. There’s also one very busy systems administrator who is working a punishing 60- to 70-hour week.
The good news…
Upper management decides we need some help and says I can hire a programmer (aka database developer) who can take a project and run with it from start to finish. We’re looking for someone who doesn’t need a lot of supervision, can deal successfully with end users, and can make sure management knows what resources are needed to complete projects on time. Oh, and by the way, this person also needs programming skills.
The IT group (all two of us) comes up with a job description and a set of questions for the interviews. The questions are designed to tell us what programming skills and experience the interviewees have, if they are a cultural fit for our company, and whether they have the independence and initiative to manage their own projects with minimal oversight. They are similar to questions we’ve used in the past—open-ended and worded so the interviewee needs to use examples of past work to give us some real answers, not just fluff.
Things aren’t looking good; qualified candidates are scarce. The few interviews we grant are lackluster and clearly don’t fit the bill. Finally Mr. Kaserda applies; Charles (Chuck) Kaserda, that is. Chuck easily moves through our questions, with plenty of examples of previous work, some of it based on “we” did this, and some on “I” did that, so we’re thinking this guy is a team player who can work on his own, as well.
He has the right skill set, so we schedule a second interview that involves having him sit down at a computer to actually demonstrate what he can do. After looking at some information, he tells me how he would construct a report from it, and he is at ease using the tools of the trade.
He also seems to have satisfactory answers as to why he’s moved through several jobs in the last few years, including a job with our direct competitor, which means he must know something about the way our business works. I tell my boss to pay him whatever it takes to get him in here; I think he is the one.
(To be Continued…)








































