Frontend interviews have become more demanding. Most companies now test JavaScript depth, React internals, TypeScript, performance and a live “machine coding” round where you build a small component. React has also moved on, with 19.2, 19.3 and a stable compiler. This guide covers what to expect in 2026 and how to prepare.

Version facts in this article were checked against react.dev, Microsoft’s TypeScript blog and GitHub’s Octoverse report in October 2026.

What’s new in React that interviewers may ask about

ReleaseDateNotable additions
React 19.21 Oct 2025<Activity />, useEffectEvent, cacheSignal, partial pre-rendering, Performance Tracks in Chrome DevTools
React Compiler 1.07 Oct 2025Stable automatic memoisation
React 19.39 Sept 2026<ViewTransition> and addTransitionType, Fragment refs, use(browser()) to opt out of SSR, Trusted Types support, direct Context rendering from Server Components

You will not be expected to know every API. Do be ready to explain why the React Compiler reduces the need for manual useMemo and useCallback, and what problem useEffectEvent solves.

JavaScript fundamentals (asked everywhere)

1. Explain closures with a practical example.

A closure is a function that remembers variables from the scope where it was created. Common uses are data privacy, function factories, and debounce or throttle utilities. A classic follow-up: why does var in a loop with setTimeout print the same value, and how do let or an IIFE fix it?

2. How does the event loop work?

Synchronous code runs on the call stack. When the stack is empty, the event loop runs all queued microtasks (promise callbacks, queueMicrotask) before the next macrotask (timers, I/O events). Be ready to predict the output order of mixed setTimeout, Promise.then and async/await code.

3. Other common JavaScript topics

  • this binding rules, and call, apply and bind
  • Prototypal inheritance and classes
  • == versus === and type coercion
  • Shallow versus deep copy; structuredClone
  • Debounce versus throttle (often asked as “implement it”)
  • Polyfills for map, filter, reduce, Promise.all or bind
  • Event delegation and bubbling versus capturing

React questions

4. What triggers a re-render, and how do you prevent unnecessary ones?

A component re-renders when its state changes, its parent re-renders, or a context it consumes changes. Reduce wasted renders by keeping state close to where it is used, splitting contexts, and memoising expensive work. With the React Compiler enabled, much memoisation is automatic, but you should still understand why it helps.

5. Why do keys matter in lists?

Keys let React match elements between renders. Using array indexes as keys in lists that can be reordered or filtered causes bugs with state and inputs. Use stable IDs.

6. Explain useEffect pitfalls.

Missing or wrong dependencies, effects that should be event handlers, and fetching without cleanup (race conditions) are all common. In development, Strict Mode runs effects twice to surface missing cleanup. useEffectEvent (React 19.2) lets you read the latest props or state inside an effect without making the effect re-run.

7. Controlled versus uncontrolled components?

Controlled inputs keep their value in React state. Uncontrolled inputs keep it in the DOM and read it through refs or form data. React 19’s form actions make uncontrolled forms with server-side handling more common.

8. Server Components versus Client Components?

Server Components render on the server, can access data directly and send no JavaScript for themselves to the browser. Client Components (marked 'use client') handle interactivity and browser APIs. Frameworks such as Next.js implement this model.

9. How would you manage state in a large app?

Start with local state and context. Use a server-state library (for example TanStack Query) for API data, and a client store (Redux Toolkit, Zustand) only for shared client-only state. Explain the trade-offs rather than naming tools.

TypeScript questions

GitHub’s Octoverse 2025 found TypeScript had become the most-used language on GitHub, so expect TypeScript in most frontend rounds.

  • interface versus type
  • Generics, for example typing a reusable useFetch<T> hook
  • Union types and narrowing; discriminated unions for component variants
  • Utility types: Partial, Pick, Omit, Record
  • What strict mode enforces, which matters now that TypeScript 7.0 (July 2026) turns it on by default

Performance and browser questions

  • Core Web Vitals: what LCP, INP and CLS measure and how to improve them
  • Code splitting and lazy loading; image optimisation
  • Critical rendering path, reflow and repaint
  • Caching: HTTP cache headers and service workers at a basic level
  • Security: XSS, CSRF, Content Security Policy, and why React escapes output (React 19.3 adds Trusted Types support)
  • Accessibility: semantic HTML, keyboard navigation, ARIA basics

The machine coding round

Many Indian product companies run a 60–90 minute round where you build a working component. Common prompts:

  • Autocomplete search with debounce and keyboard navigation
  • Infinite scroll or paginated list with loading and error states
  • Star rating, accordion, tabs or modal with accessibility
  • Nested comments or a file explorer tree
  • Kanban board with drag and drop
  • OTP input with auto-focus between boxes

How to score well: clarify the requirements first, get a working version early, then improve structure, edge cases, accessibility and styling. Talk through your decisions as you go.

A 3-week preparation plan

WeekFocus
1JavaScript depth: closures, event loop, this, prototypes; write polyfills and debounce/throttle from scratch
2React and TypeScript: hooks, rendering, state patterns, React 19.x features; build three machine-coding components under time limits
3Performance, accessibility, security, a frontend system design (for example a news feed or an image gallery), and mock interviews

Frequently asked questions

Do I need to know Next.js for React interviews?

Not always, but many product companies use Next.js or a similar framework. Understanding Server Components, routing and data fetching in at least one framework helps, especially for full-stack roles.

Is the React Compiler asked about in interviews?

It increasingly comes up as a follow-up to questions about performance and memoisation. Know that React Compiler 1.0 (October 2025) automates much memoisation, and be able to explain what memoisation does.

Are DSA questions asked in frontend interviews?

Often yes, usually easy to medium problems on arrays, strings, hashing and trees. Machine coding and JavaScript depth tend to carry more weight than in backend interviews.

Official sources

Leave a Reply

Trending