4 ms·
I've choked so bad on whiteboarding interviews that I've felt ashamed for weeks; yes, I am one of those people. But then when I broke the anxiety after practic
by cnp 11y ago
I've choked so bad on whiteboarding interviews that I've felt ashamed for weeks; yes, I am one of those people. But then when I broke the anxiety after practice, they became easy. The key is understanding that it's the process over the solution.
However, I'm quite proud of the fact that where I currently work we never ask someone to code on a whiteboard. Rather, we ask them to complete a take home test and then, when they're ready, invite them in to discuss their choices and augment it functionally. This practice is, in my opinion, holistically far more effective at gauging a candidate's competence and ability.
- learc83 11y agoThat is a far superior method for conducting an interview. Even though I'm not terrible at whiteboard interviews, I absolutely hate working while someone who already knows the answers watches over me waiting for a mistake.
- twistedpair 11y agoSadly I was able to find various great solutions to my take home programming assignments after the fact. I submitted my own original solutions, but I'm sure there are others that didn't bother/know how and submitted the other solutions they found online. I'd like to think the interviewer had an exhaustive list of Google search results for the problem, but I sadly doubt it.
- cnp 11y agoWhat I mean about take home test is "build an app that does x y and z, write tests, talk about your choices" -- something that you can't quite google. Take home tests for questions like "explain how to use fn.apply()" wouldn't work :)