I'm all for CS fundamentals, but in many places it's clearly being used as an approximation of good-code-shipping-ability.
I think part of the problem is that you're not really allowed to interview people in a way that holistically assesses their ability, so you end up doing cargo cult-y things that sort of, kind of sounds like they're relevant. For example, when I was at Amazon, we specifically were disallowed from using real-time typing/sharing tools to conduct coding questions.
Nowadays I find that pairing with someone on a limited-scope coding problem, as well as talking deeply about software design and architectural decisions, is the best way to assess. But then again, I'm also no longer interviewing complete newbies - which I think Amazon/Google/Microsoft's recruiting systems are heavily optimized for.
When faced with a candidate who has a dearth of real-world things to dig into, of course you fall back on data structures and algorithms. When you apply this to experienced professionals, who have a long track record that they can talk in depth about, it becomes silly.
When he eventually called back and started the interview, he did not even seem to respond my answers to his questions - it honestly sounded like he was playing a computer game on the other end of the line...
It was blatant disrespect towards me and my time. I'm glad I found an opportunity elsewhere.
Out of curiosity, was there a reason you decided to continue the interview process after this?
They have a post-interview review process, and I gave the recruiter an appropriately negative review.
Some companies have a mythology that every job in their company is like that, even if the actual job being interviewed for is the opposite.
Hardly limited to megacorp CA tech companies. No different than a boring old bank requiring janitor interview candidates to wear a suit and tie.
To be fair, these were "Data Structures 101" type questions. One was literally design a graph structure and write a deep-copy procedure, and that's it. Not exactly "novel." Since I haven't done these in ages, and didn't even pay that much attention when I had the class, I did badly.
Another was a simple string manipulation question that I bombed because I was already stressed out from failing the first so badly, similar to your situation.
I was head-hunted by them initially. Had a casual phone interview within the week. Then scheduled and re-scheduled a technical interview (their fault, three more weeks). Then two weeks later I had another casual phone interview. Then waited two weeks for the on-site six-interview bonanza. I finished those 4th thru 9th interview two weeks ago, and recruiter just told me yesterday to wait for the hiring committee to give a decision in another week.
I failed the first phone interview spectacularly because he asked about data structures and estimating powers of two, and I haven't done any of that after 4 years in the industry. I guess fair enough; if that's what they expect of their employees, I'm not their man.
Overall, a disappointing experience.