I interview a lot of developers, and have interviewed for years. There are some other arguments in this thread (about laptops etc) which may have a bearing on some candidates, but i dont feel are important. To cover all bases, i only look for 3 things. 1 - evidence that the person is smart (evidence through stories they tell that you can probe, articles they have written, talks, code samples etc) 2 - evidence that they can get something finished. You need somebpody who has experience of actually seeing a job through to the end. there are quite a few in my experience who bail out when the going gets tough. These you dont need 3 - has already been mentioned, but somebody whoyou think you will get along with. Doesnt have to be a new best buddy, but you will spend more thime with this hire than your family, so at least make sure you dont hate them. As for a tech exam, i like to take a scenario (how would you design a lift system/car engine/river etc in code). this means that hey cant learn something off, and makes people think on the fly. you can take a challenge like this in loads of different directions and get some surprising answers!! Lastly, i would recommend thsi book, Smart and gets things done by Joel Spolsky. Its a great little guide. here are some great links from the book: Sorting Resumes[^] The Phone Screen[^] The Interview[^] Hope some of this helps!

Hi Venky. I have nothing to hand here, but i remember that you can use a delegate to run the thread, and then a callback function which will terminate it. Im not sure how often this thread is getting created, but even if it is only once, it is good practice to terminate the thread when it has completed its job. Cheers Mark.