[WillySchu]

> ... The problem is only one side is evaluated.

I'm not sure I agree here. Granted I work for quite a small company, so it's pretty different than working at a company with a significant reputation to help candidates make decisions. But when I interview candidates I'm very aware that they are evaluating me whilst I'm evaluating them.

I actually think this is a good thing. It incentivizes me to make the interview a more pleasant experience, and perform it in such a way that it feels collaborative, like a real work situation, and not as standoffish as some interviews can be. That said, we still do ask hard technical questions solved on whiteboards or in code, and setting them up in such a way that the candidates feel comfortable asking questions on things they don't know / are unclear about is definitely challenging.

To be honest, something I think we (as in the software community at large) lose sight of some times is how unique and challenging performing interviews is. We see stories like this pretty frequently, and we're used to the idea that being interviewed is a fairly distinct skill, orthogonal to what we usually perform in our day to day work life. Something that's talked about a lot less frequently (understandably, more of us are getting interviewed than performing them) is that interviewing others is also a separate skill, and one that really isn't practiced or honed enough in my opinion.