[billnguyen]

Love this! Was in a coding interview once where they just gave you a problem and you were given laptop and time to code out a solution using whatever you would normally use ie stack overflow. First interview I've had where I felt like it was a fair test of my programming capabilities.

Of course this requires that you design the question in a way that is not completely google-able, but real world programming is not just about solving a trick question but being able to be resourceful enough to find a real working solution.

[yeukhon]

I guess I should say restricted gooling. I like take home interviews. It's harder because you are given more time and more personal space and psychology tells us we will try to design the best algorithm, the most scalable, yet complex solution. If I were to conduct such interview, such solution can be a red flag.

But you know, interview is hard. I also think interview questions don't have to change a lot. I heard Box always asks people to design an evaluator. I thought that wasn't so hard but when I started thinking about an evaluator, I started getting distracted by all the cases, even when I wanted to just implement a state diagram.