Prepare interview questions for evaluating front-end developer candidates during hiring.
Study and practice answers to common front-end interview questions before a job interview.
Identify knowledge gaps in HTML, CSS, JavaScript, accessibility, and performance topics.
Build a structured assessment rubric by selecting relevant questions for a specific role.
This repository is a curated collection of interview questions specifically designed for evaluating front-end web developers. Front-end development refers to everything the user sees and interacts with in a web browser, HTML (the structure of a page), CSS (its appearance), and JavaScript (its behavior). Hiring the right front-end developer can be tricky because the field covers a wide range of topics, and this list helps interviewers pick questions that are relevant to the skills they need. The questions are organized into thematic sections: general web knowledge, HTML, CSS, JavaScript, accessibility, testing, performance, network concepts, live coding exercises, and some lighter "fun" questions. They are not meant to be used all at once, the intention is to select a subset that targets the specific skills a role requires. Many of the questions are deliberately open-ended, meaning they do not have a single correct answer, because they are designed to reveal how a candidate thinks and communicates about technical topics. You would use this resource if you are a hiring manager or technical interviewer preparing to assess a front-end developer candidate. It is also widely used by developers preparing for job interviews, since working through the questions is a useful way to identify knowledge gaps. The repository itself contains the questions as Markdown files. The website version is built with Nunjucks, a templating language for generating HTML from structured text content. There is no runtime application, it is a static document collection. No specific programming runtime is required to read or use the questions.
Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.