TypeScript Interview Preparation Learning Path
Strengthen TypeScript reasoning beyond syntax, including narrowing, generics and scalable type design.
Free learning path by InterviewGround — a frontend interview readiness platform.
What frontend interviews test
TypeScript questions usually start small — why does this assignment error? — and quickly move to design: how would you type an API response that can be loading, failed or successful, so that impossible states cannot compile?
Senior candidates are expected to explain the trade-off between strictness and ergonomics, and to know where types stop protecting you at runtime.
What you should know
Inference
When TypeScript infers literal versus widened types, and when an annotation helps or hurts.
Narrowing
typeof, in, instanceof, equality and truthiness checks, and how control flow refines a union.
Discriminated unions
Modelling state machines so each state carries only the data it really has.
Generics
Constraints, defaults and inference from arguments — and when a generic is unnecessary.
Utility and mapped types
Partial, Pick, Omit, Record and building your own mapped transformations.
Exhaustiveness and type guards
never checks in switches and user-defined guards for data crossing a boundary.
Recommended learning order
- 01
Type system basics
Inference, unions, literal types and structural typing.
- 02
Narrowing and modelling
Control-flow narrowing, then discriminated unions for UI and request state.
- 03
Reusable types
Generics with constraints, utility types and mapped types.
- 04
Design practice
Type a real API client or form model and explain where runtime validation is still required.
Questions you should be able to answer
- How would you type request state so that data cannot be read while it is still loading?
- What is the difference between unknown and any, and when would you choose each at an API boundary?
- How does an exhaustive switch with never protect you when a new variant is added?
- When does adding a generic parameter make an API harder to use rather than safer?
Common interview mistakes
- Using type assertions (as) to silence errors instead of narrowing, hiding real bugs.
- Assuming types validate JSON from the network — they disappear at runtime.
- Modelling state with several optional booleans, which allows contradictory combinations.
- Reaching for complex conditional types when a simple union communicates intent better.
Free learning resources
Free resources from their original publishers. InterviewGround does not own or host them.
The TypeScript Handbook
TypeScript
The official guide to the type system. Prioritise the chapters on narrowing, object types, generics and type manipulation for interview preparation.
Sign in to save progress. Completion is self-reported.