I have no problem brainstorming on a whiteboard with their CTO or senior architect, but I would consider it silly to do puzzle programs or write java with some middle-manager lurking over me
I have no problem brainstorming on a whiteboard with their CTO or senior architect, but I would consider it silly to do puzzle programs or write java with some middle-manager lurking over me
I used to be good at those kind of tests 15 years ago. Now I am orders of magnitude more competent at designing implementing and deploying systems I have way more knowledge in all of those areas, but I get tested on that nonsense. I hardly ever write algorithms (occasionally), as I will look for an appropraite library first.
In general the coding was not the most important part of the interview, just a check for experience and competence. For contrast, when I got my job with NASA 10 years ago the interview was almost entirely coding, and coding minutia in multiple languages. Maybe 30% design and algorithms and 70% code over 3 days of interviews.