What is the difference between interface and type?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of TypeScript 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 describe the shape of an object, with subtle differences:
- interface supports declaration merging and is usually preferred for public object shapes and class contracts.
- type can express unions, intersections, tuples, mapped and conditional types that interfaces cannot.
interface User { id: number; }
interface User { name: string; } // merges -> { id, name }
type Id = string | number;
type Pair = [number, number];
type ReadonlyUser = Readonly<User>;
Practical guidance: use interface for objects that may be extended or merged, and type for unions, aliases and advanced type manipulation. Performance is comparable; pick a convention and stay consistent.
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.