|
|
|
|
|
by _dps
3075 days ago
|
|
I half-agree, but Spolsky also makes an excellent argument in "Hitting the High Notes" [0] that there is disproportionate value delivered from excellence, as opposed to mere competence ("Five Antonio Salieris won’t produce Mozart’s Requiem. Ever. Not if they work for 100 years."). FizzBuzz + short work sample + strong communication skills is probably not that far from optimal if you want to hire lots of people who are competent and work on problems that they have solved before. Note that I said "optimal" and not "good"; this is still a noisy process. But if you're doing something where you need to people to excel beyond what they've done before, and perhaps beyond what your company has ever done before, then I think it's naive to think that additional testing for things like on-the-spot thinking, creativity, and diligence under pressure convey no useful signal. This, in my opinion, is an extraordinary claim and requires strong evidence before anyone should take it seriously. [0] https://www.joelonsoftware.com/2005/07/25/hitting-the-high-n... |
|
The extraordinary claim is that whiteboard testing (or take-home projects, or...well, anything in the current tech interview) does any of those things.
You can't whiteboard-test for excellence. Excellence is both contextual (i.e. it depends a lot on your company, team, culture, etc.), and based mostly on squishy, intangible factors that go beyond "code": picture the brilliant coder who dons his headphones, falls down a hole, and produces a pile of undocumented, complex code of zero business value. It's a cliche, but do we interview for it? No. We ask people to do a graph search on a matrix.
My contention is that we'd do far better with some simple, basic screens for technical competency, and then spending most of our time on communication skills, personality, clarity, organization, planning, business sense and team fit.
...but of course, these are questions with no single correct answer, so engineers are afraid of them.