[DelightOne]

> There are tons of developers who are good at coding solutions to real world problems in real world situations but simply don't perform well in this type of situation.

What do you propose instead to see whether one can do real world problems in real world situations?

[01100011]

I think he's saying that normally a person isn't coding while someone is watching you. I have no problem implementing a data structure on my own but if you ask me to do it in 15 minutes while you're watching every typo I'll probably freeze up.

[itronitron]

Has anyone ever flipped the script in an interview, asking the interviewer if they can watch them write code at their workstation for an hour so they can get a sense of what it is like to work at the company?

[edhowzerblack]

You can learn a lot about what a developer knows and is capable of by talking to them about the projects they worked on. Ask them detailed questions about the particular problems they dealt with on projects and how they were solved. Ask them to explain core concepts that are intrinsic to the technologies they've worked with. You can also get a feel for their personality this way.

Remember, we're talking about a screening process. Once they come onsite for the real deal you can throw all sorts of stuff at them.