← All open source projects

Front-end Developer Interview Questions

h5bp/Front-end-Developer-Interview-Questions

Front-end Developer Interview Questions is a collection of questions for HTML, CSS, JavaScript, and web-platform knowledge.

Forks 11,031
Author h5bp
Language Nunjucks
License MIT
Synced 2026-06-27

What it is

Front-end Developer Interview Questions is a large collection of interview questions for interface development. It covers HTML, CSS, JavaScript, accessibility, performance, security, networking basics, and general engineering topics.

It helps not only interviewers. Candidates can use it as a map of gaps: which topics they can explain clearly and which ones are shallow.

How the material works

Questions are grouped by topic, and many are open-ended. That matters because a good interview discussion often reveals reasoning, tradeoffs, and experience.

The collection does not suggest asking everything. It helps choose questions for a role and level: markup, browser behavior, language, UI architecture, testing, or performance.

Preparation plan fragment

This example shows how to turn the list into topic-based preparation rather than memorized answers.

Language: Markdown
## Week focus
- HTML semantics and forms
- CSS layout: flex, grid, cascade
- JavaScript runtime and async code
- Accessibility basics
- Performance: loading, rendering, caching

What is inside

The repository contains the questions, topic structure, contribution material, and project history from HTML5 Boilerplate.

The strength of the format is neutrality: it is not tied to one framework and keeps web-platform fundamentals visible.

Practical context

The best way to use the list is answering with experience, not memorized phrases. A question about CSS Grid, events, or accessibility becomes stronger when the candidate explains a real tradeoff.

Strengths and limits

The main strength is breadth. It covers HTML, CSS, accessibility, browser behavior, and engineering habits, not only JavaScript.

The limit is that questions alone do not prove practice. A good interview still needs real examples, small tasks, and code discussion.