OOP · CS Fundamentals
OOP Concepts & Interview Questions
OOP interviews rarely ask you to define encapsulation or inheritance directly anymore — they ask you to make a design decision (abstract class vs. interface, exception vs. return code, when composition beats inheritance) and justify it, or to spot why a class hierarchy or exception design has gone wrong. Ediky's OOP question bank is built around exactly that: 49 questions, almost entirely scenario and design-judgment style.
49
Questions in Ediky's CS bank
1 (single consolidated course)
Video lectures
Scenario & design judgment, AI-evaluated
Question style
Ediky's OOP video content is currently one consolidated "Complete C++ OOPS in 1 Shot" course rather than a multi-lecture series like DBMS or OS — the 49-question bank is the deeper resource here.
What to actually study
- Abstract class vs. interface — when each is the right tool, not just the syntax difference
- Inheritance vs. composition — recognizing when a hierarchy should be flattened
- Exception design — which failures deserve a checked exception vs. a return code
- Constructor design — spotting an overloaded, poorly factored constructor
- Class design under real constraints — e.g. modeling a stateful system like a chess engine with undo/redo
Real questions from Ediky's OOP bank
Actual question titles from Ediky's CS Fundamentals bank:
- "Choosing Between an Abstract Class and an Interface for a Plugin System"
- "Class Design for a Chess Engine with Undo/Redo and Check Detection"
- "The Constructor With Nine Parameters, Six of Them Null"
- "A Class Hierarchy Explodes Combinatorially — Redesign It"
Practice OOP design questions
49 OOP questions in Ediky's CS Fundamentals bank — design judgment, not definitions.
Open CS Fundamentals