Something just feels inherently broken when the act of just doing the job isn't the same practice (training) necessary to interview for that same job. Why should I have to learn to "crack the coding interview"? I'm not trying to trick teams into thinking than I better than I am or know more than i actually know because I spend the last few days memorizing a few algorithms I never use.

I'm certainly not saying that teams don't take into account a candidates experience, OS code or his/her ability to discuss complex, role relevant, topics in great detail -- i'm just saying that no matter how high you rank in all these other areas, at most companies (including mines), it really doesn't matter if you can't reverse a linked list on the spot ¯\_(ツ)_/¯.

I just tend to believe that solving algorithms (especially under pressure) is a specific skill just like everything else, not a general test of programing "ability" -- so unless the job requires that you write algorithms every day then we should broaden the traits that we test for. That said, having interviewed a lot of candidates myself, it is truly difficult to consistently identify good well rounded candidates.