InterviewPrepInterviewPrep· Job Insights

Frontend Developer technical round: JS, browser and React

The Frontend Developer technical round goes beyond writing components: it probes JavaScript fundamentals, browser internals, CSS layout, framework knowledge and performance. Interviewers want depth, not just familiarity with a framework's API. Below is how the round runs, the areas tested, worked strong-versus-weak answers, and how to rehearse the concepts that separate strong frontend candidates.

Start a free mock interview →

What the round tests

Frontend technical rounds sample across the stack that runs in the browser. Frontend engineers who cover the boundary with UI/UX Designer Jobs — layout, accessibility, motion — tend to interview strongest at product companies.

  • JavaScript core: closures, the event loop, promises and async/await, prototypes and 'this'.
  • Browser internals: the DOM, rendering, reflow versus repaint, and event delegation.
  • CSS: the box model, flexbox and grid, specificity, and responsive layout.
  • Framework depth: React rendering, hooks, keys and reconciliation, or the equivalent in your framework.

The signal they want is someone who understands why the browser behaves as it does, not only which API to call.

Question archetypes

Certain conceptual questions recur because they reveal depth quickly.

'Explain the event loop and the output of this setTimeout/promise snippet.'

They test whether you understand the microtask versus macrotask queue.

'What causes a re-render in React and how do you prevent unnecessary ones?'

They probe state, props, memoisation and key usage.

'Why does this CSS not centre the element?'

A practical layout debug that tests real understanding, not memorised tricks.

Strong vs weak answers

Question: 'What is a closure and where would you use one?'

Strong: 'A closure is a function that retains access to variables from the scope in which it was defined, even after that scope has returned. I use closures for data privacy, like a counter factory, and in event handlers and hooks to capture state. The gotcha is stale closures in React effects, which is why the dependency array matters.' It defines, applies, and names a real pitfall.

Weak: 'A closure is a function inside a function.' It is technically incomplete, gives no use case, and misses why closures matter. Interviewers use the follow-up to expose the shallow understanding.

How to prepare

Prioritise depth in fundamentals over breadth of libraries.

  • Master the event loop, closures and async behaviour until you can predict output.
  • Be able to debug CSS layout and explain specificity live.
  • Understand your framework's render cycle well enough to optimise it.

Because interviewers push follow-ups on every answer, rehearse explaining concepts aloud with examples. A free AI voice mock interview on InterviewPrep generates a frontend mock from your CV and a real job description, then scores your explanation clarity, pace and filler words, so your answers stay precise when the questioning goes deeper.

Frequently asked

How deep does JavaScript knowledge need to be?
Deep enough to predict async output and explain closures, the event loop and 'this' with examples. Interviewers use follow-ups to separate memorised definitions from real understanding, so be ready to apply each concept and name a common pitfall, not just recite it.
Do I need to know CSS well for a frontend technical round?
Yes. Expect practical layout questions using flexbox and grid, specificity puzzles and debugging why an element will not position correctly. CSS is often where candidates who lean entirely on frameworks get exposed, so keep your core layout skills sharp.
Is React knowledge enough, or do I need vanilla JS too?
You need both. Framework depth matters, but interviewers probe the JavaScript and browser fundamentals underneath, since those explain why React behaves as it does. Understanding the render cycle and reconciliation without the framework abstraction is what signals real competence.
How do I answer performance questions?
Connect them to browser behaviour: reflow versus repaint, minimising re-renders, code splitting, lazy loading and reducing bundle size. Explain how you would measure the problem before optimising. Interviewers value candidates who profile rather than guess at bottlenecks.
What separates a strong frontend candidate here?
Explaining the why behind browser and framework behaviour, applying each concept to a real scenario, and naming pitfalls unprompted. Candidates who only know API surface struggle on follow-ups, while those who understand the underlying model stay precise as questions deepen.
How do I filter frontend roles on Naukri Jobs?
Search for the specific framework you know (React, Vue, Angular) rather than the generic frontend developer keyword; JD-level framework match dramatically improves your shortlisting rate and cuts irrelevant recruiter calls.

Related prep

Frontend Developer Coding Round Practice · Software Engineer Technical Round Practice · Software Engineer System Design Interview Practice · Software Engineer Coding Round Practice

Reading about it isn't practice.

Run a real AI mock interview built from your CV and a live job description — scored feedback on your answers, pace and filler words.

Start your free mock interview →