What does structural typing mean in TypeScript, and where can it surprise you?

Explains assignability by shape, excess-property checks, and the gap between compile-time compatibility and runtime identity.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

TypeScript is structurally typed: a value is assignable when its shape satisfies the target type, even if it was declared under a different name. Extra properties are usually allowed on an existing value, although a fresh object literal receives an excess-property check that catches likely mistakes. These are compile-time rules; they do not add runtime tags or validation.

Full answer below

Practice focus

A sound TypeScript mental model without implying nominal identity or runtime validation.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
TypeScript normally asks whether a value has the required shape, not whether it explicitly declared membership in a named type.
TypeScript is structurally typed: a value is assignable when its shape satisfies the target type, even if it was declared under a different name. Extra properties are usually allowed on an existing value, although a fresh object literal receives an excess-property check that catches likely mistakes. These are compile-time rules; they do not add runtime tags or validation.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
If a function needs { id: string }, an object with id, name, and can be passed because it contains the required member. But writing that larger object directly as a literal where only is expected may trigger an excess-property error. I treat that check as typo protection, not as a guarantee that objects never contain additional fields.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Assuming values must explicitly implement a TypeScript interface.
Treating excess-property checks as exact-object enforcement everywhere.
Claiming TypeScript types exist at runtime.
Using assertions to suppress shape errors without investigation.

What does structural typing mean in TypeScript, and where can it surprise you?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Skill areas

Human editorial direction

Was this drill useful?

Found this answer useful?