Posted by:
ificouldhietokolob
(
)
Date: April 09, 2018 12:45PM
When hiring for a new programmer spot, I read through the mass of resumes first, and pick out ones that seem a good fit.
Then I do phone interviews, typically 5-10 mins. I pick out the best of those.
Then I have them come in, and the first thing I do is give them a test.
It's an on-line programming test. I have a laptop set up with the browser open to that page, ask them to do the test, then walk out, giving them 15 minutes to do it.
But, see, I'm sneaky...the test isn't just a programming test, it's a "how resourceful are you" test and an honesty test. What I want to see is, if they don't know the answer, if they'll look it up (they have a web browser open right in front of them). So I expect them to get 100% right, and then to tell me which ones they looked up because they didn't know/couldn't remember. I want people who know how to find answers if they don't know them.
The results are always somewhat amusing. I get people who score around 85% (which is pretty good, it's a hard test), and then tell me they didn't think to look up answers they didn't know (those folks usually don't get hired). I get people who scored 100%, but deny they looked up any answers (when a quick look at the web history shows they did). Those dishonest people don't ever get hired.
The ones I hire get 100% or close to it, and when I come in, they tell me (without me asking) that they looked up some of the answers on the web (which is often accompanied by "I hope that's OK"), and which ones they did/didn't know.
Interestingly, those folks almost always say, when I tell them looking up answers was part of the "test," that they felt like solving the problem was the top priority. While the ones who looked them up and lied about it, when told, almost always say, "Well, I thought that was cheating!" Yes, and you just cheated and lied about it, did you think I was going to hire you? :)