I think the irrelevant CS problems are an okay test to see someone's style and thought process where they shouldn't be too worried about solving the problem (th

I think the irrelevant CS problems are an okay test to see someone's style and thought process where they shouldn't be too worried about solving the problem (they should have at least a meager basis of understanding to begin with) and can spend time cleaning up, and preparing their thoughts for presentation. I think this is fine as one of multiple measures. I graduated from CS, and the only reason I knew anything at all about how to handle multi-tier architecture is because I was employed previous to my graduation. How do you keep configuration from being a mess? Hard coded values all over the place, etc. CS courses give you the theory needed for getting started down a path of understanding, but it does not make you understand, nor does it actually prepare you for the real world. Data structures are one thing, micro services, unit testing, configuration management, dependency injection, and persistent storage are beasts all unto themselves.