What are signs of a bad intviewer?

Perhaps bad methods, makes false assumptions about you very quickly?

I am a 2YOE junior looking to jump into mid level roles. I just had an interview where I was asked what knowledge do I want to improve in the next year. I said system design because I work with microservices but have limited knowledge on how the company’s services were built that way, I want to understand the reasons we use x, y, z instead of a, b, c... The interviewer, I kid you not, spent the entire interview criticizing that statement of mine.

Saying that I only have 2YOE, yet I focus on learning stuff like system design and instead of diving deeper into my existing language Java, I am doing projects in Go? I asked if I can refute, because it’s totally doable to both dive deeper into your existing tech stack and also learn something new, but he said no I don’t accept debate. So I just stayed quiet listening to his rage about how juniors these days pick up a bunch of things instead of trying to be master of a few. Sure there is some truth to that but I passed the technical interview before this one where the interviewer really drilled deeply into the tools I use, so it doesn’t make sense I’m being criticized now.

He also made fun of the way my company’s system was built. He said what kind of solution architect allowed this to happen? The n + 1 problem you said you solve in your resume is completely unnecessary for an app that only receives fewer than 10 visitors a day. I refuted saying that problem exists and harms latency regardless of the size of the data set, he said I’m focusing on fixing the wrong thing. He said if it was him, he would have taken it up to the solution architect saying that the db was structured so stupidly that n + 1 even happens. Then he criticized my school saying you graduated from a school that didn’t teach you to dive deeper into your latency problem.

Anyways, at the end of the interview, he gave me the “advice” to be honest with myself because what I wrote in my resume was “bluffing”: you cannot solve n + 1, you do not understand Java enough to be starting projects in Go,…

I stopped refuting 10 minutes into the interview because he didn’t wanna debate. So I just sat there and took his assumptions. Have you ever had an even worse interviewer than this?