I don't think all interviews should use it but for us it was good for filtering out candidates who would not perform in those situations.
I don't think all interviews should use it but for us it was good for filtering out candidates who would not perform in those situations.
Whiteboard coding is also a different kind of pressure. I can't imagine a situation where someone who already knows the answer is watching over your shoulder critiquing you while you work on a problem.
right? unless you are in downtime mode, there's really something wrong with your schedule/deliverables/tasks.
writing code is not a race, it's more of a marathon where you have to be at a healthy pace to get to the end, otherwise you will not be able to finish.
I think it's unlike any real situation, and you're fooling yourself that one kind of stressor is like another.
This sounds like an incredibly toxic working environment, where developers are either being allowed to create fires on production systems, or management is completely incompetent or both.
Also, being able to "handle it" has nothing to do with anything in this discussion. I'd much prefer to hire someone capable enough to not need to "handle it" than someone proud of the fact that they often s*it the bed but are willing to jump up and do the laundry under pressure.
I personally enjoyed it but it's not for everyone.
I think it comes down to expectations - in an interview I have to focus on impressing my audience and that's always there. In real life, I can focus fully on the actual problem being solved.