What is the never type? | Interview Question

Q: What is the never type?

**Target Audience:** Developers who have seen `never` in error messages and utility types and want to understand what it is and how to use it on purpose. **Difficulty:** Medium **TypeScript version:** Every type claim below was checked by TypeScript 5.4.5 with `--strict`; that `never` arrived in TypeScript 2.0 is cited, not run. > **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 Think of types as boxes of allowed values. `boolean` is a box with two things in it, `true` and `false`. `"red" | "green"` is a box with two strings. `string` is a box with every string. `unknown` is the biggest box: everything fits. Now imagine the **empty box**. Nothing is in it — no string, no

The problem

Question presented to candidate: "What is the never type in TypeScript? Where does it show up on its own, and where would you write it deliberately?"

What a strong answer should cover:

never is the bottom type: the type with no values. It is assignable to every type, and nothing (not even any or unknown values) is assignable to it
Where it appears by itself: functions that cannot return normally, branches where narrowing has removed every member, impossible intersections like string & number, and [] inside an object literal (never[])
Algebra: T | never is T; a conditional type maps members to never to drop them (how Exclude works); key filtering with mapped types
Deliberate uses: exhaustiveness checks, forbidding a property with prop?: never
Traps: a distributive conditional over never gives never, so IsNever needs [T] extends [never]; never vs void vs unknown

Code / implementation expected: Optional — a few type-level checks, or an exhaustiveness helper.

never
void

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 seen never in error messages and utility types and want to understand what it is and how to use it on purpose. Difficulty: Medium TypeScript version: Every type claim below was checked by TypeScript 5.4.5 with --strict; that never arrived in TypeScript 2.0 is cited, not run.

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

Think of types as boxes of allowed values. boolean is a box with two things in it, true and false. "red" | "green" is a box with two strings. string is a box with every string. unknown is the

The solution is hidden so you can try first

10 min read · 10 sections

Run the code

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

TypeScriptThe rules of never and where it appears

Practice

TypeScriptnever in type-level code: filtering unions and IsNever

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.