What is structural typing and how does it differ from nominal typing?
Assesses fundamental understanding of TypeScript conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
TypeScript is structurally typed: compatibility is decided by the shape of a value, not by its declared name. If it has the required members, it is assignable.
interface Point { x: number; y: number; }
function log(p: Point) { console.log(p.x, p.y); }
log({ x: 1, y: 2, z: 3 }); // ok, excess property check only on literals
Nominal systems (Java, C#) require an explicit implements/inheritance relationship. Structural typing enables duck typing and easier mocking, but can allow accidental compatibility, which branded types (a property intersection) can prevent when needed.
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.