Frontend Developer Interview Questions and How to Answer Them

Candidates often prepare framework trivia and then get asked how the event loop orders a promise and a timeout. This section covers the fundamentals that nearly every frontend loop checks, before any framework appears. Expect questions on the language, then on what the browser does with your code.

• Closures and scope: what a closure captures, and why a loop with var logs the same value repeatedly.
• The event loop: the order of synchronous code, microtasks (promise callbacks) and macrotasks (timers).
• this and binding: how arrow functions differ from regular functions, and what bind changes.
• Rendering pipeline: what triggers layout versus paint, and why reading layout inside a write loop causes thrashing.
• Events: bubbling, capturing, and event delegation on a long list.
• Networking: CORS, caching headers, and what happens between typing a URL and the first paint.

Language-specific depth is covered in the JavaScript, TypeScript and React question banks in the question banks hub.

These three areas separate frontend specialists from generalists, so interviewers probe them directly.

• CSS layout: when to reach for Flexbox versus Grid, how specificity resolves conflicts, and how a stacking context affects z-index.
• Responsive design: media queries versus container queries, and building mobile-first.
• Accessibility: semantic HTML before ARIA, keyboard focus order, labelling form inputs, and colour contrast.
• Performance: Core Web Vitals (LCP, INP, CLS), code splitting, image formats, and lazy loading.
• Security: cross-site scripting, why you escape user content, and what a Content Security Policy does.

A good answer names the trade-off. "I would use Grid here because the layout is two-dimensional" beats a list of properties.

Most loops include a practical build. A typical prompt: build an autocomplete input that fetches suggestions, debounces keystrokes, supports arrow-key navigation, and ignores stale responses. The interviewer watches how you structure state, handle loading and error cases, and keep the component accessible.

Front-end system design is the senior version. You might be asked to design a news feed or a collaborative editor: where state lives, how data is fetched and cached, how you paginate, and how the component tree is split. A frontend engineer interviewing for a senior role at a product company might spend the whole hour on the feed, and the strongest answers talk about loading skeletons, optimistic updates, and what happens on a flaky mobile connection.

For the live-build format itself, see the interview types hub.

Practice out loud. Frontend rounds reward narration: saying why you chose a controlled input, or why you debounced at a given point, is part of the score. Build three or four small widgets from scratch with no framework, then rebuild one in the framework you list on your resume.

A spoken rehearsal with an AI interviewer that asks follow-ups is available on the mock interview page. During a live video call, SubcueAI can surface structured answer points from the conversation, but it has clear limits: proctored assessments, recorded screens, and company-managed laptops are out of scope, and a shared screen during a live build shows whatever is on it.