I tend to take my laptop with code on for the client to look at, if they question who coded it etc then I have the History of the files etc. I have had a "given this spec, given this domain model, code this unit test to prove this".
GE
GE
-
-
Techy questions are fine of course, and maybe a short written test at interview (30 mins or so). I would not entertain anything like the chess test above, or a test lasting several days.
Concerning online tests, I would probably decline now, after a bad experience with a client in Oxfordshire. They had an online test outsourced to some testing company, which I completed at home. Problem was the questions were obviously not written by a Unix expert, and were often ambiguous or naive, incorrect in themselves, with no right answer. At the end of the test I opened another tab in my browser and the site fed some rude text into the new tab accusing me of cheating (which I did not).
Unprofessional garbage the lot of it, and I fed that back to the agent (not using the word garbage).Comment
-
Don't expect much
I have given four tests in the past. In the first, I scored 99%. I appeared for the same one a year later and scored 98%. I then also appeared for a different one and scored 96% (I will come back to the fourth one later in the post.)
Neither of the tests resulted in anything. One of the tests measured ability on server-side programming and concepts in which I scored 99% and 98% to which the company said they are looking for somebody stronger. I got the impression that the manager was looking for a 100%+ score.
The fourth one was more of a problem solving exercise for which I was given few hours. The exercise was to display a certain text based on input conditions. The exercise did not mention anything else. Nothing with regards to Unit Tests in particular. I clarified this and was told to just come up with a simple algorithm. I wrote an application which worked as required. In the interview, I was asked why there are no unit tests. I replied saying the exercise did not specifically mention this and I was not told about this either when I clarified. I also said I've kept the application simple, brief and to the point. The interviewer was expecting a complete enterprise level application built using IoC dependency injection frameworks, unit tests, multiple layers, documentation, etc. to be done. In other words, he was expecting me to put in 98% of the time in designing the framework and 2% to write the actual algorithm.
This is a tricky situation. If you come up with an enterprise level application packed with frameworks, multiple layers, unit tests for an extremely simple exercise, you may be asked why have you done all this extra for such a simple and quick thing? Alternatively, if you don't this, you may be asked why you haven't. It is therefore better to ask about any expectations before attempting to unleash your potential.
The exercises do not result in anything and are merely a waste of time. If you have professional certifications on the same subject, please mention so and refuse to undertake an additional test covering the same concepts. The fact that a professional body like Cisco, Microsoft, Adobe, etc. has certified you in a particular subject should be enough for the company to waive the test for you.
Furthermore, if somebody has a lot of experience (~ 15 years), testing the same person on the subject s/he specialises is an insulting joke.Comment
-
I only show them a project that is 100% my own property. So not a problem. Should have said earlier to be honest.Originally posted by TheFaQQer View PostComment
-
For my current (perm) place the interview was a chat with the programming manager and my potential team leader. They just asked me to talk them through how I got into programming and then about various jobs I had done, projects I had worked on etc.
Then they gave a spec and asked me to write code to meet it. They gave me an hour and then came back in with their technical director. I had not completed the spec and they assured me that no one ever does and then began to talk through my code. We went from UI design all the way down to compiler optimisations for STL containers.
It was actually a good interview. They told me afterwards that the main thing that determines whether they hire the candidate is how well they get on with them and whether they can explain technical issues. How good they are at the actually programming side just reflects how much money they will offer.
It took just over 3 hours.
My previous client's interview (when I was still a contractor) lasted exactly 17 minutes and they offered me the gig.
It is a very different world!
Comment
-
Originally posted by unixman View Post
I've never done an online test and would refuse something that took as long as that unless they paid me for my time.
I usually get a quick verbal test on a phone interview or written test in a face-to-face. One time I got on well straight away with the manager (I was asked if I liked curry & beer in the interview lol)but still had to do the techy bit. While I was writing, the techy guy went for coffees and the manager started rattling off the answers. Turns out the manager was living away from home during the week and was looking for a drinking buddy.
I don't think I made a profit during those 6 months as it all went behind the bar.
Comment
-
Life is too short for technical tests. Either they hire your services or they don't. It is a risk they take, like the ones we take with agencies.
I, personally, will hand the client a long rusted barge pole if I am asked to take a technical test.
Having said that it depends on the role and how you try to sell yourself.Comment
-
Must admit interviews that are long drawn out with loads of stupid tech questions are usually crap. Best interviews are short, get to know you type ones.Rhyddid i lofnod psychocandy!!!!Comment
-
Have you ever been interviewed by bobs? I suggest that you don't miss that once-a-life experience!Originally posted by psychocandy View PostComment
Comment