React Easy technical 2 views 1 min read

What are the key features introduced in React 18?

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 React 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

React 18, released in March 2022, introduced several groundbreaking features focused on performance and user experience:

#### 1. Automatic Batching
Batch multiple state updates together (even in async code) to reduce re-renders.

     // Before React 18: Only batched in event handlers
     // After React 18: Batched everywhere
     setTimeout(() => {
       setCount(c => c + 1);
       setFlag(f => !f);
       // Only 1 re-render in React 18!
     }, 1000);
     

#### 2. Concurrent Features

  • useTransition: Mark updates as non-urgent
  • useDeferredValue: Defer expensive re-renders
  • Suspense on Server: SSR with Suspense support

#### 3. New createRoot API

     // Old way (React 17)
     ReactDOM.render(<App />, document.getElementById('root'));

     // New way (React 18)
     import { createRoot } from 'react-dom/client';
     const root = createRoot(document.getElementById('root'));
     root.render(<App />);
     

#### 4. Streaming SSR with Suspense
Stream HTML from server and hydrate components as they arrive.

#### 5. New Hooks

  • useId: Generate unique IDs for accessibility
  • useSyncExternalStore: Subscribe to external stores
  • useInsertionEffect: For CSS-in-JS libraries

#### 6. Strict Mode Improvements
Double-invokes effects in development to catch bugs.

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.
Spotted an error or have an alternative solution?