roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Reason about TypeScript's type system the way interviewers probe it, from narrowing to type-level programming. Covers types and interfaces, generics, utility and mapped types, and tsconfig and builds.
384 of 384 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 384 new. 0 cut, outside your plan.
Few loops give TypeScript a slot on the schedule. The questions arrive inside a frontend or Node.js conversation, and the side of the stack the job sits on decides what follows the opening `any` against `unknown`. Frontend loops stay near components: typing props and event handlers, modelling loading, error and loaded states as a discriminated union so an impossible combination fails to compile, writing a generic select whose callback knows the item type. Full-stack loops push toward the edge of what the checker guarantees: a request body typed as `User` that nothing validated, what an `as` assertion does and does not check, and why a type shared by client and server still needs a runtime schema behind it. Teams that publish packages or own a monorepo build ask about declaration files and module resolution, and why a library typechecks for its authors and breaks for its users. Angular and NestJS shops add classes and which decorator model their framework compiles against. Blockchain teams keep the same core and add the numbers: token amounts outgrow `number`, so `bigint` and contract calls typed from an ABI come up. Each of those interviews usually spends most of its time elsewhere, in the browser, a framework, HTTP or a chain. For the whole job rather than its type questions, prepare from the [Frontend Developer](/roadmaps/frontend), [Full Stack Developer](/roadmaps/full-stack), [JS Full Stack Developer](/roadmaps/javascript-full-stack) or [Blockchain Developer](/roadmaps/blockchain) roadmap, each of which carries those other rounds alongside this one.
Say each answer before you reveal the one on the card, and where you can, type it into an editor with `strict` on: the compiler settles a type question faster than rereading does, and `strictNullChecks` changes the right answer to many of the early ones. The tree itself is explained on the topic's hub, whose [primer](/topics/lang-typescript) says why its parts come in the order they do; read the explanations there, and keep this plan for rehearsal. Juniors are judged mostly on [narrowing](/topics/lang-typescript-unions-narrowing): getting from a union to one member through `typeof`, `in` or a shared literal tag, and saying why `unknown` demands that step while `any` skips it. Middle candidates are separated in [generics](/topics/lang-typescript-generics), less by declaring a type parameter than by predicting what the compiler infers for it and choosing the constraint that keeps a function safe without making it awkward to call. Senior rounds reach [conditional types](/topics/lang-typescript-utility-mapped-types-conditional-types) early, `infer` and distribution over unions included, and then ask what that cleverness costs: errors nobody can read, and a checker that slows the editor. With an application interview close, importance is the one control worth moving: drop nice to know from its range, and the hours go to what a product team's loop reaches rather than the far edges of the type system. How the event loop orders a resolved promise is a JavaScript question rather than a type question, and belongs to the [JavaScript roadmap](/roadmaps/javascript).
Few loops give TypeScript a slot on the schedule. The questions arrive inside a frontend or Node.js conversation, and the side of the stack the job sits on decides what follows the opening any against unknown. Frontend loops stay near components: typing props and event handlers, modelling loading, error and loaded states as a discriminated union so an impossible combination fails to compile, writing a generic select whose callback knows the item type. Full-stack loops push toward the edge of what the checker guarantees: a request body typed as User that nothing validated, what an as assertion does and does not check, and why a type shared by client and server still needs a runtime schema behind it. Teams that publish packages or own a monorepo build ask about declaration files and module resolution, and why a library typechecks for its authors and breaks for its users. Angular and NestJS shops add classes and which decorator model their framework compiles against. Blockchain teams keep the same core and add the numbers: token amounts outgrow number, so bigint and contract calls typed from an ABI come up.
Each of those interviews usually spends most of its time elsewhere, in the browser, a framework, HTTP or a chain. For the whole job rather than its type questions, prepare from the Frontend Developer, Full Stack Developer, JS Full Stack Developer or Blockchain Developer roadmap, each of which carries those other rounds alongside this one.
Say each answer before you reveal the one on the card, and where you can, type it into an editor with strict on: the compiler settles a type question faster than rereading does, and strictNullChecks changes the right answer to many of the early ones. The tree itself is explained on the topic's hub, whose primer says why its parts come in the order they do; read the explanations there, and keep this plan for rehearsal.
Juniors are judged mostly on narrowing: getting from a union to one member through typeof, in or a shared literal tag, and saying why unknown demands that step while any skips it. Middle candidates are separated in generics, less by declaring a type parameter than by predicting what the compiler infers for it and choosing the constraint that keeps a function safe without making it awkward to call. Senior rounds reach conditional types early, infer and distribution over unions included, and then ask what that cleverness costs: errors nobody can read, and a checker that slows the editor.
With an application interview close, importance is the one control worth moving: drop nice to know from its range, and the hours go to what a product team's loop reaches rather than the far edges of the type system. How the event loop orders a resolved promise is a JavaScript question rather than a type question, and belongs to the JavaScript roadmap.