| "Like a skilled surfer, I wanted to learn to ride the high pressure waves that came with interviews." Yeah, bro, that's not surfing. Good surfers respect the big waves. No coder is going to respect a bad interviewer. But I trudged on through the article and ran into this gem: "There will be times when you’re stuck. And this could be caused by a number of reasons: you don’t have the requisite knowledge, incorrect assumptions, missing details, and so on. "I used to think that at such times I was being judged by how fast I could come up with a solution. So I would be quiet, thinking, not communicating with the interviewer, just thinking. "And this is where a lot of us get it wrong. I get it, you need some alone time to think. But sorry to burst your bubble, that alone time is not when you’re being interviewed by a person. "Yes, your interviewer wants to see that you can come up with a solution, but one thing you must not forget is that they also want to see that you can collaborate with other team-mates to come up with a solution. While companies want rock-stars, they also want team-players. "Since your interviewer is a friend, a buddy, a team member who’s on your side and means well for you (Refer to 4), talk to them while you're figuring it out." Yeah, the interviewer is definitely your friend, and you have to work with them as a team in the interview. This advice is gold. If you do not feel that they are a friend, you can politely ask to end the interview for personal reasons. No use interviewing further, for the same reason you can end a date if you are no longer comfortable. |