[wesleyb]

I had a full loop with Google last year. It was awful. The guys were really aggressive and incredibly offensive, reminding me time and time again that they hated the company I worked for. Which is fine if it's your personal opinion, but don't invite me to your offices only to insult my employer. Kinda silly, really.

I can't help but wonder that maybe the interview process is broken. Can you really gauge how effective a dev is based on his might at solving a few programming problems on a whiteboard?

I've seen the strongest candidates in this field end up being the worst devs (bad team players, no design docs, not adhering to spec, crap unmaintanable code), and vice versa. Which makes me wonder. Anyone using any interesting techniques out there other than the standard "here's a tricky problem, now solve it"?