"Code Review" session only tests wether I'm a computer or not. Simply putting game developers into tests and ask the output of the code is out of touch with today's standards. We do not live in 90s anymore. We learn about tools and programs and we put together projects, we have much more tools in our possession that we can use as complimentary gadgets. Simply reading 35 lines of code and solving weather the output is "x" or "y" does not indicate problem solving skills, that's what calculators or computers are good at.

The interviewer shows you some C# code snippets and asks you the outputs of the code. It is mostly related to Object Oriented Programming and Big O Notation of the algorithms.