When they asked me about abstract classes, I gave them a straightforward answer: “An abstract class is one that is going to be extended in various ways.” I didn’t dive into details about instantiation or other technicalities, because to me, the concept was simple — an abstract class serves as a blueprint for other classes to extend, with variations of its own functionality. But, that wasn’t enough for them. They seemed to want more depth, something that felt like it came straight out of a textbook. To be honest, it was frustrating. I thought my answer made sense in the context of the question, and I didn't feel the need to over-explain things that were already logical. If you're working with an abstract class, you understand it’s meant to be extended, not instantiated. But they were looking for a level of detail that, in my experience, would only come up in niche or overly theoretical discussions, not in real-world coding. The whole vibe was starting to feel more like a memory test than a conversation about practical skills, and by this point, I was starting to lose interest. They seemed more interested in seeing how well I could recite abstract concepts than in actually discussing how to solve real programming challenges.