I have done a few interviews in my time as well and most of the questions I ask don't have a definitive right or wrong answer. I look for how quickly the answer is given and how it is presented. For instance, one question I as is "You want to update data in one field for 500,000 entries, how would you accomplish this?" There are a few ways to accomplish this but if they say "Do a modify all" without first stating that they would check to see what workflow could fire, I know that this person could be dangerous and has not experienced what could happen when you do this. The other thing that is usually missing in interviews are questions/scenarios that pertain to ones personality and real life experience. For example, one of the questions I ask is "You are a consultant, working on-site and realized that a statement of work was incorrect. In order for the customer to continue with the implementation, it will cost them an additional $50,000 dollars. How do you present this to the customer?" Someone with consulting experience usually responds with something like "First contact the PM and or Sales rep to discuss and allow them to work it out with the customer." Again, there is no right or wrong answer, just bad and good responses that give me an idea of their real world experience. I have seen many times that an individual has the technical know how but is all thumbs when it comes to working with other people and customers. Seth Wrye
________________________________ From: Action Request System discussion list(ARSList) on behalf of arslist Sent: Thu 2/21/2008 3:44 PM To: arslist@ARSLIST.ORG Subject: Re: Interview questions ** Agreed. The answer to a couple of questions doesn't help: 1) Can XXXX be done in Remedy? Answer: Yes Doesn't matter what XXXX is, could be run a floor waxer, it can probably be done. Just how, and is Remedy really the correct tool. 2) How do you do XXXX in Remedy? Answer: 1..N where N is rarely less than 5, and usually contains one or more best practice solutions It is really the ability to recognize what the question is asking, depends on a good question of course, and the ability to discuss various methods and reach an reasonable solution. However, this does require that whoever is doing the interviewing really knows their stuff, and makes it difficult for Human Resources to do screening. ... Daniel p.s. and I still use TR. sometimes and perhaps I shouldn't I'll double check :-) ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thad K Esser Sent: February 21, 2008 3:23 PM To: arslist@ARSLIST.ORG Subject: Re: Interview questions ** The reason I think its a good interview question is that the answer (whatever is given) would help you assess their depth of knowledge. The interviewee might not know what you are talking about, or might start talking about using a TR or DB value in an active link. If they can discuss the issue in depth and explain the concepts, you know they've thought about it. Either way, the answer will help you match the skill level of the job with the skill level of the candidate. Thad Esser Remedy Developer "Argue for your limitations, and sure enough, they're yours."-- Richard Bach To cc Subject __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
