This is probably the single best interview session I've ever had. Give-and-take is always good for easing the process, but in one case I had a programmer actually sit down with me at a laptop and pair program our way through an hour task. Still time pressure, I suppose, but it was vastly more natural and informative than any other interview I've done.
I pressed him and he eventually said "I ran this by 3 Senior Python experts I know. All of them said the code wasn't good." No other details.
Before he even gave me the assignment he made his decision. He lied about asking 3 other people.
Coding assignments are always one sided. Unless someone from the company is going to sit with me and invest equal hours into the project, I will never do another one.
They are used by companies to filter out desperate employees (young engineers who don't have reputation to fall back on, or nothing to lose by doing it) and it signals a lower value to the company.
I disagree with the notion of desperate employee — I’m anything but that, but I prefer a take home to show my engineering worth rather than a whiteboard if those are the two choices. Of course if you’re super famous then you probably won’t get either, depending on the company and it’s processes. That said I’ve been down the M&A path and still got (many) whiteboard interviews.
I would be shocked if any company in the world gives you this choice.
I never take the "a couple hours long assignments" because the scope is never "a couple hours", once company wanted me to build a chat service that would take at least 20 hours of work to get properly done with testing, etc.
I'm talking one that I recall that asked for parsing Apache logs from a stream, displaying moving averages for most popular URLs, aggregates of visitor counts, having high water mark "alerts" for ingress traffic and monitoring rolling averages to "de-alert" when traffic dropped below that, including of course unit tests and documentation...
One, that's more than a couple of hours. And two, that sounds awfully like something you're planning to use, whether I'm hired or not...
I've been at other interviews in which the on-site interview is a walkthrough of the code I'd written, asking questions about why I made various choices. I think this is really a much better way to do programming interviews. It still weeds out people parroting code without understanding it, but it's a better example of what a candidate's actual code looks like -- and for the vast majority of programming jobs, that's probably more important than whether they've memorized algorithms that rarely come up outside other whiteboard tests.
If you want me to spend more than 30 minutes programming for you, that's called work, and I would like to get paid for that.
I think it all comes down to personal pref, but the data seems to show that whiteboard interviews are good to filter middle of the road talent, but top/bottom can look the same.
I get a brain freeze when the clock is ticking. I've been practicing with ticking clock but its still hard.
None of the companies showed even 1% flexibility with their process. They say its a standard and they can't compare candidates if they use different methods for everyone.
It’s amazing what a short assignment can tell you about a person, and it makes the follow up on site productive because there are so many ways to ask about their work.
Personally for Apple I asked specifically to be given one of these instead of the whiteboard, as I get overly stressed in a “pop quiz” type setup. They still ended up pop quizzing me twice, and one of them I didn’t do well on. It was my take home that pushed me over the edge and got me hired.