Isn't it already? I feel like all of the interview questions come down to things you learned in a Data Structures or Algorithms course. I suppose the design questions aren't necessarily taught in school but presumably you would learn that as you program more.

But the people who'd need that the most are the ones furthest out of school.

I shudder at the thought of ever having to do another programming interview. Well, alternately shudder and laugh. What a joke!

Then we shall call them a sales (or whatever) training, not the CS.

Alternatively we could come up with a better system for interviewing. Instead of concentrating on being able to remember algorithms and write them out in a completely non-normal way (white board) we could, instead, give them a very small project to do then have them come in and explain it, walk someone through extending it and / or work through a problem together. You'd get real experience seeing how they write their code, work with others and their ability communicate.

Drilling someone to do tree traversal or various Big-O exercises doesn't exactly come up in the real world. Yeah performance and understanding data structures is important but that's why you give them something real, see what kind of data structure they come up with and why and go from there.

Well at least in my opinion. I've interviewed a lot of people and have been interviewed myself. I've unfortunately haven't been able to gather the data to see how effective my method is BUT I like it a hell of a lot better.

We used to have something called the "recitation class" one hour a week for solving homework problems out loud. I was under the impression these were making a comeback as classes "flipped" to watching the lectures outside of class. People would skip recitation sometimes because they werent learning new material like in the lectures or doing their problem sets which took enough time already. If these were made more mandatory somehow, they'd be like interviews.