When should you use a type annotation, a type assertion, or satisfies?

Separates declared variable types, unchecked developer assertions, and compatibility checking that preserves useful inferred types.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

A type annotation declares the type a variable or parameter should have and checks assignments against it. A type assertion tells TypeScript to treat a value as another type without runtime validation, so I reserve it for cases where I have evidence the compiler cannot express. satisfies checks that an expression is compatible with a type while usually preserving the expression's more specific inferred type.

Full answer below

Practice focus

Whether the candidate knows which constructs ask the checker for proof and which simply override it.

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
These forms may appear beside the same expression, but they make different promises and preserve different amounts of inference.
A type annotation declares the type a variable or parameter should have and checks assignments against it. A type assertion tells TypeScript to treat a value as another type without runtime validation, so I reserve it for cases where I have evidence the compiler cannot express. satisfies checks that an expression is compatible with a type while usually preserving the expression's more specific inferred type.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For a route map, annotating it as Record<string, Route> may widen useful literal keys. Using satisfies Record<string, Route> checks every value but keeps the known keys for later lookup. By contrast, does not validate JSON and can move the failure deeper into the application. I parse unknown input before assigning a trusted domain type.

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

Calling a type assertion a runtime cast.
Using satisfies as if it changed the runtime value.
Assuming an annotation always preserves literal inference.
Using as to accept unvalidated network data.

When should you use a type annotation, a type assertion, or satisfies?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next in path

Prerequisite

Skill areas

Was this drill useful?

Found this answer useful?

Human editorial direction

When should you use a type annotation, a type assertion, or satisfies?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next in path

Prerequisite

Skill areas

Start a conversation

Was this drill useful?

Found this answer useful?

Human editorial direction