> I am genuinely wondering if I am bad, or if it is those "coding challenge" that are inappropriate. Neither. Did you read the article? One of the things the

> I am genuinely wondering if I am bad, or if it is those "coding challenge" that are inappropriate. Neither. Did you read the article? One of the things the author learned was a key thing that most people who complain about this kind interview don't understand. > 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. I'm sure there exist interviewers who sit there and let you sweat trying to come up with something that you don't know. But most interviewers, at least at places that require a steady stream of quality engineers and thus have invested a lot in their interview pipeline, only expect you to know the fundamentals. They may ask you to implement a TCP handshake... but they want to see how you approach the problem. If you know how to do it by heart, that'll be to your credit. But if you don't, it's expected that you work with the interviewer to collect requirements. Seeing how you make progress on a problem you don't already know how to solve is exactly why you're there.