3 ms·
> To do well in an interview, then, you need to be able to solve small problems quickly, under duress, while explaining your thoughts clearly. The under duress
by balls187 8y ago
> To do well in an interview, then, you need to be able to solve small problems quickly, under duress, while explaining your thoughts clearly.
The under duress part is the dumbest part of coding interviews.
I understand the approximation of small coding challenges, why explaining your thoughts is beneficial, as is understanding how a candidate approachs problem solving.
Causing duress to a candidate purposefully has no value what-so-ever in the workplace.
- bootlooped 8y agoI think the interview process itself causes duress to candidates intrinsically. There is probably no way to eliminate it completely. That said, there probably is a reason for testing candidates under duress. Some companies may want to push people hard, and knowing they can deal with stress is valuable.
- balls187 8y agoI don't agree that programming interviews are conducted to see how well candidates will fare in a dysfunctional workplace. Anecdotally, programmers thrive in quiet environments where they can have focused uninterrupted time. As open-offices have become the norm, most programmers have headphones they use to isolate background sounds. Constantly peppering candidates with questions while they are trying to do a task that is mentally intensive is not close to the type of stress candidates face on the job. Even the most work-life balanced places do these same types of interviews.