4 ms·
I think most people that are opposed to coding interviews feel that way because they don't feel confident in their ability to do those interviews well, whereas
by dqpb 8y ago
I think most people that are opposed to coding interviews feel that way because they don't feel confident in their ability to do those interviews well, whereas they do feel confident in their ability to "get work done".
Here's the thing though. Let's say you're the one giving the interview to two people who claim to be able to get shit done. One is able to code up a solution quickly and the other struggles, producing less, or producing something that's flawed. Sure, that second person might actually be productive under the right circumstances, but that doesn't matter because the first person already proved they can code.
That's the whole point of interviews, getting high signal in a short period of time. If you think coding interviews don't provide high signal than propose something better that costs the same amount of time.
- Retra 8y agoYour resume, Github account, demonstration of previous projects, ability to discuss problems you've solved, references from previous coworkers & instructors... The whiteboard is not providing "high signal". Everything else is. The whiteboard is providing low signal, and taking quite a bit longer to do it.
- jcbrand 8y agoThis doesn't take into consideration how much studying and preparation the person who produced a solution quickly did compared to the person who took longer. If that person studied much more, then they weren't really "quicker", they were just better prepared. Perhaps that's still a reason to hire them, but not everyone has time to study lots of programming puzzles before an interview, and this is then less a measurement of speed, and more of preparedness. It also doesn't take into consideration whether the whiteboard problem being presented is at all relevant to the job being offered.