But do you still do it using the book methods taught in college? If the interviewer is okay talking about the concepts instead of the lingo, that seems okay. But don't expect people to remember textbook details for years.

As an aside, I've done many, many interviews, and for a long time my manager insisted on jumping in and asking candidates to recite the components of SOLID and explain them. You can probably guess that very few (none that I can recall) got it on the first attempt. Good candidates could talk about the concepts if you reminded them what the acronym stands for. To me this means the question is useless. Ask about the concepts and skip the trivia.

I don't expect them to remember textbook details either. But I expect people to know how to manipulate and understand an unfamiliar data structure or understand when a given data structure is appropriate for a particular problem domain. I expect people to understand (or be able to derive) when memoization is appropriate. I expect people to understand (or be able to derive) how using different data structures or representations of these data structures might affect memory layout and cache performance.

That's essential stuff, not something to be dismissed as "textbook details".

Sure, but my experience searching for jobs indicates that those forms of questions are very rarely asked. Instead, questions like "in a N dimensional space filled with M points, find the point(s) closest to a given point" or "figure out if this list of pointers has a loop", or "implement quicksort in Java".

If you don't use these as your whiteboard questions, great. But I've not run into you or others like you in my own searching.