Frontend Engineer Interview Prep

An interview prep path for frontend loops. Frontend interviews split into two tracks - a practical round (build a component, write a hook, debounce a search box) and a generalist round (algorithms, system design at the edge). This path covers both: TypeScript and framework depth first, a lighter algorithms floor, practical frontend coding, and the system-design topics that show up when the box you are designing is a browser.

Frontend EngineerMid~45h7 sections23 items

Section 1 of 7

JavaScript and TypeScript fundamentals

Frontend loops probe the language before the framework - closures, the event loop, type narrowing, generics. If an interviewer can shake you on `this` or `Promise` ordering, the framework questions never land. Anchor the language first.

01MCQTypeScript questions (25 suggested)Multiple choice category

Section 2 of 7

Framework depth

Rendering models, reconciliation, state management trade-offs, hydration. Interviewers care less about API recall and more about whether you know why the framework does what it does - and what it costs.

01MCQFrontend Frameworks questions (25 suggested)Multiple choice category

Section 3 of 7

Algorithms floor

Frontend loops still ask algorithms, just lighter than backend ones. You need the core patterns - hash maps, two pointers, traversal - to be reflexive, not a deep DP repertoire. Cover the floor and move on.

Section 4 of 7

Coding: strings and arrays

The generalist coding round in a frontend loop is almost always string and array manipulation. These warm-ups lock in the patterns interviewers reach for - frequency maps, sliding windows, in-place rearrangement.

Section 5 of 7

Coding: frontend practicals

The round that actually decides frontend offers: build a component, write a hook, control async behavior. Narrate the accessibility and re-render decisions as you go - that commentary is what separates mid from senior.

Section 6 of 7

System design at the edge

Frontend system design is about what happens between the user and the origin: caching at the CDN, real-time sync, typeahead latency budgets, feed rendering. These four walkthroughs cover the designs frontend interviewers actually ask.

Section 7 of 7

Behavioral: collaboration and craft

Frontend roles sit between design, product, and backend - behavioral rounds screen for how you handle that seam. Have a story for each theme: a disagreement you resolved, feedback you gave, ambiguity you structured.

Browse other learning paths

Three role-targeted paths are live: Backend, SRE / DevOps, and ML Engineer. More are on the way - if you have a role you want covered, let us know.

View all paths →