What are unknown, any and never?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of TypeScript conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
- any disables type checking. It is contagious and should be avoided; use it only as an escape hatch.
- unknown is the type-safe counterpart of any: you can assign anything to it, but you must narrow before use.
- never represents a value that can never occur, such as a function that always throws or an exhausted union in a switch. It also appears as the bottom of the type hierarchy.
function fail(msg: string): never { throw new Error(msg); }
function assertNever(x: never): never { throw new Error('Unexpected: ' + x); }
Using never with exhaustive switch checks is a common interview talking point.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.