I agree it seems OP is bad at interviewing, as well as some others who have replied to OP. It would be better to view the interviewing process as a game with a

I agree it seems OP is bad at interviewing, as well as some others who have replied to OP. It would be better to view the interviewing process as a game with a weird set of rules, half of which you don't even know when you join the game. Realize your chances of winning the game (i.e. getting the job) are generally not increased by ferociously attacking the rule book. Also, from the companies perspective, if you can't even accept their interview process. How on earth are you going to accept all of their other wacky corporate rules you will have to comply with day-by-day. On your first day you will probably be like "I have to put my opening brackets WHERE? Dude, that's sick..." or "I can dig the spinning in my seat three times before committing code, but why the hell can't I commit when the line count of the commit is negative?" You will not make a good corporate slave.