TypeScript Easy technical 1 views 1 min read

What are the basic data types in TypeScript?

Peer-reviewed by HireXTech Technical Panel • Updated for 2025/2026 hiring • Editorial standards
Practise this track
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

TypeScript adds static typing on top of JavaScript, categorizing data types into primitives, composite structures, and special utility types:

### 1. Primitives:

  • boolean: true or false.
  • number: 64-bit floats (42, 3.14) and binary/hex values.
  • string: Textual strings ('hello').
  • bigint: Large integers (100n).
  • symbol: Unique identifier primitives.

### 2. Complex & Structural Types:

  • array: Homogeneous lists typed as number[] or Array<string>.
  • tuple: Fixed-length arrays where each element has a known type: [string, number] (e.g. ['Alice', 25]).
  • enum: Named constants (enum Direction { Up, Down, Left, Right }).
  • object: Non-primitive types (Record<string, any> or explicit interfaces).

### 3. Special Utility Types:

  • any: Disables type checking completely (avoid in strict codebases).
  • unknown: Type-safe counterpart of any; requires type narrowing before usage.
  • void: Indicates functions that return no value.
  • never: Represents values that never occur (e.g. functions that always throw or infinite loops).
  • null & undefined: Represent absence of value, strictly checked when strictNullChecks: true.

Candidate Response Strategy & Interview Tips

  1. Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
  2. Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
  3. Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
  4. Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.
Related Topics & Skills
Spotted an error or have an alternative solution?