| > Sounds like stress doesn't impact you, even in interview settings No, it sounds like you didn't read the top of the thread, where we're specifically discussing Whiteboard Prompts. I agree interviews are stressful; I disagree with the argument that "Whiteboard Prompts" are so much higher stress than the rest of the interview that we can't conclude anything from them about the candidate. I further argue that if one can't perform in a Whiteboard Prompt, wherein the entire goal is to have the type of conversation about a problem that engineers are paid to have about problems rather than coming to a code solution, than one will probably be difficult to work with in any situation which involves some pressure. Some classic examples of equally high pressure situations as talking to an interviewer you don't know but who is probably on your level include things I do each week: * speak with stakeholders about progress * opine to stakeholders about complexity of features, timelines and methodologies of their implementation, and possible blockers * work with my team & extended team members to give Code Reviews, where often they are my direct report or someone else's direct report So, I conclude that if one is able to excel technically, but completely unable to handle this socialization aspect of interviews, than in a large corporation where you frequently have rotating casts of external stakeholders, this implies you will not be fit for any of the work interfacing or collaborating with colleagues outside the team. This implies this person will be a low performer if hired into this team. Call it a "ridiculous strawmen" if you want, but I don't see why we should completely discard testing of someone's ability to interact in new situations, otherwise surely I could argue in the ridiculously reductionist way you are interpreting my multiple, specific comments elucidating my stance that TripleByte has solved the interviewing problem. |
The only point I am trying to make is that yes, interviews are very different than the other scenarios that you mentioned.
Here's one reason: in an whiteboard problem solving session, the other person has explictly prepared something that they know more about than you. On top of that, you are both aware of this fact. This almost never happens in a normal work-collaboration. A collabaration happens because both parties have something to offer. If not, they'd be explaining to you, and not the other way around.