Was contacted with the job description through Hired. I felt that I was missing several key prerequisites of the job, and the location was not ideal for me, so I politely declined. However, the recruiter insisted that hiring manager wanted to speak to me, so I agreed to go ahead with it. I figured that it would be good practice either way.

There were two interviewers, one who I assume was a manager, and the other an engineer, who kept mostly quiet except to ask a few technical questions at the end. Unfortunately, he was difficult to understand due to the fact that he had a strong accent, and his microphone was also of poor quality as the sound was muffled.

I got the usual "tell me about yourself" initial question, to which I gave a brief summary of my career thus far. I assumed they would want me to go into more detail about the projects I'd worked on, but instead started reading off a slew of behavioural questions off of his monitor. I was not prepared for this and unfortunately, I'm not one of those people who are able to dream up stories on the fly, so I did poorly. I'm also someone who does not feel that answers to these questions are indicative of how great of an employee one is/can be, so it tells me a lot about the company when they're heavily focused on such things.

After that, they asked me to rate my various skills on a scale of 1 to 10, then began to ask me obscure programming questions. When I was unable to answer those, I was thrown some softballs about OOP in general.

What are the fundamentals of OOP?