What are branded (nominal) types? | Interview Question

Q: What are branded (nominal) types?

**Target Audience:** Developers who have mixed up two IDs, two units or a raw and a sanitized string, and want the compiler to stop it — explained from first principles. **Difficulty:** Medium **TypeScript version:** Checked with TypeScript 5.4.5 and `--strict`; `unique symbol` dates from TypeScript 2.7 ([TypeScript 2.7 release notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-7.html)). > **How to read this doc:** Every idea is explained in plain language first, then tagged with `📌 Interview term:` so you also learn the exact words an interviewer expects. Type claims are checked by `tsc` (an `Equal ` line or a `// @ts-expect-error` line), and the **Verified** section quotes the real output in full. ## 1. Why This Even Matters — A Story First A hospital pharmacy stores medicine in identical white bottles. The pills inside are different, but the bottles look the same, so the shelves are only safe if nobody ever grabs the wrong one. The fix is not new

The problem

Question presented to candidate: "TypeScript is structurally typed, so a UserId and an OrderId that are both strings can be swapped by accident. How would you make the compiler tell them apart, and what does that cost at run time?"

What a strong answer should cover:

Structural typing: two aliases of string are the same type, so aliases alone give no protection
A brand intersects the base type with a fake property, string & { readonly __brand: "UserId" }, so plain strings and other brands are no longer assignable
Brands are created in one place, a smart constructor or a type guard / assertion function that validates and then casts, so the type means "already checked"
The brand is type-only: zero run-time cost, the value is still a normal string (typeof is "string"), and operations like .trim() or + return the unbranded base type
A unique symbol key and a generic Brand<T, B> helper make brands harder to fake and reusable; units of measure (Meters, Seconds) are a classic use
Alternatives and neighbours: classes with a #private field are nominal, string enums are opaque, and validation libraries offer brand helpers

Code / implementation expected: Yes — define two branded ID types, a constructor for each, and show a call that swaps them failing to compile.

branded-types

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Developers who have mixed up two IDs, two units or a raw and a sanitized string, and want the compiler to stop it — explained from first principles. Difficulty: Medium TypeScript version: Checked with TypeScript 5.4.5 and --strict; unique symbol dates from TypeScript 2.7 (TypeScript 2.7 release notes).

How to read this doc: Every idea is explained in plain language first, then tagged with 📌 Interview term: so you also learn the exact words an interviewer expects. Type claims are checked by tsc (an Equal line or a // @ts-expect-error line), and the Verified section quotes the real output in full.

1. Why This Even Matters — A Story First

A hospital pharmacy stores medicine in identical white bottles. The pills inside are different, but the bottles look

The solution is hidden so you can try first

10 min read · 11 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

TypeScriptBranded IDs and a smart constructor

Practice

TypeScriptA Brand helper, units, validated values and #private classes

Practice

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.