When would you choose an interface over an abstract class?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of C# conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
Both define contracts that other types implement, but they differ in intent and mechanics.
- An interface declares a contract with no state (traditionally) and supports multiple implementation. Members are public by default, and C# 8+ allows default implementations. A class can implement many interfaces.
- An abstract class can hold state (fields), constructors, and both abstract and concrete methods, but a class can inherit only one. It expresses an "is-a" relationship.
public interface IShape { double Area(); }
public abstract class Shape {
public string Name { get; init; } = "";
public abstract double Area();
public override string ToString() => $"{Name}: {Area()}";
}
Prefer interfaces for capability-style contracts: they are multiple, decoupled and easy to mock in tests. Use an abstract class when implementations share code or state, or when you need to evolve the base with protected members over time.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.