I know OOP but don't remember all the points by heart?

Question

OOP

Not so long ago I had an interview and did not expect that I would be asked the principles of OOP. In this regard, I could not name them all (well, I did not repeat them). And as a result, they sent me a link for beginners to study OOP. It was very embarrassing.
As such, with the word OOP, inheritance mostly occurs in memory. But with the rest of the problem. Why? Yes, because in ordinary life, when designing systems, we usually say that we need to inherit a class. And we do not say in ordinary life that here we are abstracting, but here we are encapsulating.
Does everyone agree with me? Or do these principles need to be memorized so that even at night jumping out of bed to call them?

Answer 1

I think that if the interview goes like an exam - it's shit.
You could find out whether you know OOP or not by giving an example of simple classes and asking what is happening there, and from this you can understand what you know.
If it’s not right, you say something, then ask them to reason about how you came to this.

Answer 2

In addition to these 3 OOP principles, there are other 5 principles called SOLID.
And you need to know them too. Moreover, this knowledge is constantly useful in practice.
I agree with them: don't hire someone who doesn't know them.