A solution to that might be tests, where the company isn't telling you why you were rejected, but it is obvious from something objective.
I.e. if the process aborts after a certain stage, and the first few stages are fairly transparent tech skill evaluations. If it is something as fuzzy as code on a whiteboard, that is more like a human interview, but something like progressive fizzbuzz could be used as a 1h pre-screen.
If all teammate interviews happen pre lunch, then, and you are told to go home before lunch, then it is the team interviews. I guess then exact reason wouldn't be clear to you, though.
An answer saying "our team doesn't like you" would be fine with me even if more details would be welcome e.g. you didn't get the joke about Lisp. After all, I can't be liked by everyone :-)
I.e. if the process aborts after a certain stage, and the first few stages are fairly transparent tech skill evaluations. If it is something as fuzzy as code on a whiteboard, that is more like a human interview, but something like progressive fizzbuzz could be used as a 1h pre-screen.
If all teammate interviews happen pre lunch, then, and you are told to go home before lunch, then it is the team interviews. I guess then exact reason wouldn't be clear to you, though.