4 ms·
That's the analogy I use when people complain that whiteboarding doesn't mimic/approximate they day-to-day job. If you're the casting director for a play you're
by frostmatthew 8y ago
That's the analogy I use when people complain that whiteboarding doesn't mimic/approximate they day-to-day job. If you're the casting director for a play you're going to have auditions, you're not going to cast people based (solely) on their resume and having a conversation about their acting background. But auditions are very different than an actual performance: there's no audience or costumes or props, the lighting is completely different than what it will be, you're reading from a script, you may be the only person on stage while the other roles are read offstage, you're being accompanied by a piano instead of a full pit orchestra, you're mostly standing in one place instead of moving to established blocking, and so forth. The point of an audition isn't to mirror performance night, it's to get an idea if you're capable of acting/singing/dancing/whatever. Likewise the purpose of whiteboarding isn't to mirror the day-to-day work, it's to get an idea of your problem solving capabilities (some might argue it's also to see if you actually know how to code, but personally I feel that's what the technical phonescreen is for).
- nunya213 8y agoI agree with the sentiment but almost no other profession does this. Could you imagine a Surgeon being forced to "Audition" for his job? "Here perform heart surgery on this guy for us, if he lives you get the job."
- frostmatthew 8y ago> I agree with the sentiment but almost no other profession does this Almost no other creative profession doesn't do this. Our profession is much more similar to actors and musicians than it is to doctors or lawyers. You also have to factor in practicality and gatekeeping (for lack of a better word) - it's not very practical for a doctor to perform mock surgery for an interview, whereas it's very feasible asking someone to write some code on a whiteboard; and if you're a surgeon you have things that indicate you know how to perform surgery at a much higher level of confidence than knowing someone can problem solve (well) just because they list "developer" on their resume, surgeons have to go to many years or medical school, they have to spend time in residency, they have to pass their boards, if software development had the equivalent of all this (and I'm not necessarily saying it should) then yes there'd be much less need for "auditions" in our field.
- learc83 8y ago>Almost no other creative profession doesn't do this. This is only true for a very small subset of creative professions. Actors and musicians perform in front of an audience. That's their job--they are performance artists. Asking them to perform in front of you is very similar to what they'll actually be doing day to day. A much better analogue is a creative profession that doesn't involve performance art. Interviewing an illustrator, a graphic designer, a writer, or an architect generally involves looking through a past portfolio of work with the interviewee. In general they aren't expected to perform on the spot in front of an audience because that's not part of their job.
- frostmatthew 8y ago> Actors and musicians perform in front of an audience Some actors/musicians. Movie actors never perform in front of an audience, TV actors usually don't perform in front of an audience, studio musicians rarely perform in front of an audience - these professions have auditions (unless you're an A-list actor, but I'm sure most software companies would hire John Carmack without an "audition" so we likewise do the equivalent). But more importantly I think you missed my point, in that the audition for these professions are under very different conditions than what you'll actually be doing "on the job" (one of the bigger complaints with whiteboarding seems to be that it doesn't closely mirror the actual work). > Interviewing an illustrator, a graphic designer, a writer, or an architect generally involves looking through a past portfolio of work with the interviewee That'd be fine if the point of the technical interview was to determine they know how to write code, but it's not IMO. As I mentioned above it's to determine they're capable of problem solving, because that is the important part of what we do (you should also obviously make sure a candidate knows how to code before you hire them, but that's the point of the phone screen).
- learc83 8y ago>Movie actors never perform in front of an audience, TV actors usually don't perform in front of an audience, studio musicians rarely perform in front of an audience - these professions have auditions This is only true for an extremely limited definition of audience. Movie actors most certainly perform in front of an audience. There are hundreds of people on the set. Even a small indie film has a few dozen people on set. It's the same for TV actors. Studio musicians also have plenty of people watching over their shoulders while they perform, and they're expected to be able to do so on the spot without preparation. >As I mentioned above it's to determine they're capable of problem solving, because that is the important part of what we do That's the important part of nearly everyone's job. Architects, graphic designers, engineers, sales people, mechanics, plumbers. There's nothing special about programming in this regard. We've just convinced ourselves that our industry is so special that of course we need weird hazing rituals. Everyone else seems to get along fine without treating people from new college grads to programmers with 20 years of experience like this is their first job. Can you solve this artificial problem that I already know the answer to right now in this time boxed, needlessly adversarial situation situation while I watch over your shoulder and critique you?