Frontend engineer
The language first, then the browser and frameworks, then performance, security and design.
6 of 12 steps ready · 462 questions · about 39 hours of reading
Start the path- Topic
- Chapter
- Planned
- Read by you
- Started
- 01JavaScript183 questions
Every frontend interview starts at the language.
- 02TypeScript63 questions
Typed JavaScript is the default in most teams.
- 03HTML and CSS61 questions
Layout and semantics come up before any framework does.
- 04Browser runtime51 questions
Rendering, events and storage explain most real bugs.
- 05AccessibilityPlanned
Expected of senior frontend work.
- WCAG, planned
- The accessibility tree, roles, and accessible name computation, planned
- ARIA, planned
- Keyboard, planned
- Widget patterns, planned
- Forms, planned
- Dynamic content, planned
- Visual, planned
- Testing, planned
- 06React54 questions
The most-asked framework.
- 07State and data fetchingPlanned
Where most frontend complexity lives.
- Classifying state, planned
- External stores, planned
- Redux, planned
- Lightweight stores, planned
- Server state, planned
- Invalidation and refetching, planned
- Mutations, planned
- Fetching correctness, planned
- Pagination and infinite queries, planned
- Prefetching and hydrating client caches from the server, planned
- 08Next.js50 questions
Server rendering and routing in practice.
- 09Web performancePlanned
Measuring and fixing slow pages.
- Core Web Vitals, planned
- Measurement, planned
- Critical rendering path, planned
- HTTP delivery, planned
- Images and fonts, planned
- JavaScript cost, planned
- Main-thread responsiveness, planned
- Memory, planned
- Profiling with browser DevTools, planned
- 10Web securityPlanned
XSS, CSP and the browser's trust model.
- Browser security model, planned
- XSS, planned
- Content Security Policy, planned
- CSRF,
SameSite, and cookie attributes, planned - Clickjacking and framing controls, planned
- Server-side attacks, planned
- Security headers and HTTPS, planned
- Supply chain, planned
- Secrets, planned
- 11TestingPlanned
What to test and how.
- Strategy, planned
- Test runners, planned
- Test doubles, planned
- Async code, planned
- Component testing, planned
- End-to-end testing, planned
- Coverage, planned
- Flaky tests, planned
- TDD and testing legacy code, planned
- 12System designPlanned
Frontend design rounds at senior level.
- The method, planned
- Scaling, planned
- Data at scale, planned
- Consistency, planned
- Consensus and leader election, planned
- Reliability patterns, planned
- Distributed transactions, planned
- Classic designs, planned
- Frontend system design, planned