| I am in a position to interview applicants for development positions. I still chuckle when I think of an interview I had last year... I knew within the first few minutes of this interview that this guy was not for us. He was coming out of a DOS development background (if my memory serves me correctly it was Clipper or FoxPro). The guy had no recent development skills and was telling us he would ramp up quickly for our .NET / SQL needs. The interview lasted about 20 minutes when I asked the question "Do you have any questions for us?" He said "as a matter of fact I do". He opened a folder and pulled out a sheet of questions. It was obviously printed from a website. It was questions like "Why would I want to work for here?". "Please describe to me what job I am applying for?", etc. I thought to myself, "fair enough, I will take the time to answer these questions honestly even though most of them were covered in the previous 20 minutes." When he got to the end of list, he flipped the page to another full page of questions. My head jerked, my eyes opened wide and I shook my head a little. He informed me don’t worry, I don’t plan to ask all of these, which he then proceeded to ask all of them. It was questions like, what do you use for source code control? What do you use to track bugs? Do you practice Agile development? My long winded sheet-1 answers quickly became one and two word answers for sheet two. It was when he flipped the page to page three I lost it. My elbows hit the table, I let out a big SIGH and asked "there are more questions?" I couldn’t believe he had the nerve to ask more questions after the sigh I let out, but he did. I don’t recall exactly how I wrapped it up, and I tried to stay somewhat professional, but more less informed him he was not the right guy for the job. For our business, development skills are important, but do not account for everything. I would say client interaction and people skills rank right up there. |
But your presentation of this story suggests astonishment that someone coming to you for the honour of a job on your wonderful team would have the nerve to care a lot about the environment in which he was working.
The example questions you bring up seem like perfectly reasonable questions to me and I'd be loathe to work somewhere where the manager didn't want to answer them. You'd maybe be surprised by how many places don't use source control at all, or don't have any kind of development methodology, let alone Agile.