**Why Both Exist:** Interface = contract only (pre-Java 8). Abstract class = partial implementation + state. Interface = multiple inheritance of type; abstract = single inheritance + shared code. **Choices:** Use interface for: capability (Serializable, Comparable),...
This easy-level Python/Coding question appears frequently in data engineering interviews at companies like Meesho. While less common, it tests deeper understanding that distinguishes strong candidates.
Start by clearly defining the core concept being asked about. Interviewers want to see that you understand the fundamentals before diving into implementation details. Structure your answer with a definition, then explain the practical application with a concise example.
Why Both Exist: Interface = contract only (pre-Java 8). Abstract class = partial implementation + state. Interface = multiple inheritance of type; abstract = single inheritance + shared code.
Choices: Use interface for: capability (Serializable, Comparable), polymorphism. Use abstract class for: template method, shared state (protected fields), base pipeline stages with common setup.
Production: Prefer interfaces + composition. Abstract for framework base classes (e.g., AbstractReader with connect/read template). In data eng: Reader/Writer interfaces; AbstractBatchProcessor with shared retry logic.
Want feedback on your answer?
Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer — FreeAccording to DataEngPrep.tech, this is one of the most frequently asked Python/Coding interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.