When timetotrade were hiring we needed a Java developer. We created a Java program that would compile and even run, but was horrifically inefficient. First task

When timetotrade were hiring we needed a Java developer. We created a Java program that would compile and even run, but was horrifically inefficient. First task for the interviewee - how would they rewrite it. It had spelling mistakes, a mixture of variable naming schemes, differences in syntax ( brace inline, one true brace ). If just you as the tech guy leading the interview create that test and hand it to the rest of the team you'll have a benchmark. We gave a programming task before the candidate got their foot in the door. I believe we did generation of Pythagorean triples. Once again, we wrote one internally for comparison. Grab the latest version of mono and write something similar in C#. I don't have any experience with COM objects, I imagine the above would work for them too. Ultimately it's going to depend on what you want from a successful candidate. If you want someone who lives and breathes work then it's going to be attributes A, B and C. If you want someone outgoing, active, social then you want attributes D, E and F. There might even be some overlap. Basic questions are going to be - development environment, source control preference, latest languages dabbled with, interests outside programming. Don't think I've had an interview where I haven't been asked at least them.