OOP and Database Fundamentals

What they ask

The developer loop is short: a phone screen, a technical interview with the team lead and a supervisor, then HR. The technical questions are described as medium level and cover databases, OOP and a bit of behavioural probing, with machine learning basics appearing when it is on your CV. Questions in this area, for example:

OOP. Explain the four pillars with a code example for each. Abstract class vs interface, and when you would choose each in a payment module. What is polymorphism at runtime vs compile time? How would you model Employee, Manager and Contractor so payroll code does not need if chains?

Databases. What is normalisation and what problem does third normal form solve? Primary vs foreign vs unique keys. Write a query returning departments with more than five employees. When would you add an index and what does it cost?

If ML is on your CV. Overfitting and how you detect it, why you split train and test, and the difference between classification and regression, kept at a conversational level.

Behavioural. A time you fixed a production issue, and how you handled a disagreement with a teammate about design.

What they look for

Clear definitions with your own examples, and comfort switching between code and data questions. The process moves fast (offers within days), so a confident, tidy performance matters more than depth in one topic.