Just ask people to actually code something right then and there. A lot of people can talk bullshit, but just watching them work on Fizz Buzz for 5-10 minutes can tell you all you need to know.

I just googled FizzBuzz, and I'm shocked that's actually a thing.

Why not take a snippit of coding, remove a good portion of it and ask them to fix it?

I'd have to prepare questions based on the languages that the applicants are familiar with, or else they'd take too long reading.

(and I'm too lazy for that)

what about asking them what kind of security counter-measures they'd code up in case of an attempted intrusion?

i can think of a few (including my theoretical <but only theoretical b/c it wouldn't technically be legal to implement> program i nicknamed Abaddon... which would launch a counter measure that'd lock open a hacker's system then systematically fry each piece of their hardware until all that was left of the intruding hacker's computer would be fried slag
<.<

>.>


ummmm

if you would like some help thinking one up feel free to shoot me a note ^_^

..huh.

It's been awhile since we've heard from you...
Hope everything's going/gos alright.

sorry about your butt being sore, lol

Trick question:
Q: Are Java objects pass by value, or pass by reference?

It's a bit late now, but it seems like I didn't need any tricky questions anyway; one guy stated off with a talk about his history as a rugby player for 15 minutes to 'introduce yourself', one girl talked about gaming as the very first thing said, etc. across 6 people.

that sounds most unfortunate. Makes me wonder if I could actually get a job if those are the types of people who are applying!

(then again, I do enjoy to talk, sometimes....)

oh, by the way. Of the pitfalls of asking "puzzle questions" in an interview:


http://www.codeslate.com/2007/01/yo.....survivors.html