ScriptSave interview questions

The interview process consisted of meetings with the IT Director, Project Manager, HR, and a panel of Software Developers. Before the panel interview, I was given a set of requirements for a building a client website. The requirements consisted of some screenshots (welcome page, data entry, etc.) and general instructions. In the panel interview, I was asked to describe how I would approach the design of each tier (HTML/JavaScript/CSS, ASP.Net/C#, SQL). Specific questions were asked regarding field validation (jQuery), master pages, database design, and SQL commands. General questions about OO programming (Inheritance, polymorhpism, abstract classes), ASP .Net, C#, and web services were also asked. The general questions are not too difficult for a developer with a few years of experience, but might weed out some of the under qualified. I found the development team to be very nice, professional, and enthusiastic about their jobs and the company. This is definitely an ASP .Net/C#/JavaScript shop. The only negative part of the interview is that I had to come back just to meet the Software Manager, who was not available the first time I was there.

Phone screening with IT Director and then on site interview in Tucson, AZ. I was given a different schedule than the hiring manager (IT Director) which led to an hour of sitting in the lobby. Originally I was told the interview would be 3 and a half hours with the option to go to 4 hours if we needed. The IT Director was a nice guy and seemed knowledgeable. The IT Director and I chatted for 15 minutes about the position and his expectations. I felt confident in my abilities and was interested in the position. I spent most of this time asking questions about the software they wrote and the process they went through to test and then deploy. During the group interview with the software developers I quickly realized that I didn't want the job. The questions were straight out of a college book or most likely a google search. I've never been a big fan of not answering questions however I must have said I don't know to 15 questions. It wasnt that I didnt know any of the answers as much as I stopped listening to the questions. The questions reminded my college exam questions where the professor takes the first sentence of a paragraph, removes the key word, and asks you to fill in the blank. I was blown away with how horrible the interviewer was. After 2 or 3 ridiculous questions I quickly decided this wasn't the team for me. Another interviewer handed me a database schema and began drilling me on query syntax which I felt was very effective at weeding out weak candidates. I actually liked the schema questions he asked so much that Im planning to use it in the future when hiring software engineers at my current employer. The panel interview ended with time for a single question before the team left. I was then introduced to the CIO and the head of HR. I spent 30 minutes discussing the company and getting a better feel for the position. The interview wrapped up in 2 hours. Two weeks after the interview I received an email stating another candidate had accepted the position. If I was offered the position I would have turned it down.