Guide · Open source
How to use Front-end-Developer-Interview-Questions for hiring and self-testing
Updated · written with AI from the project's own documentation and checked against our catalogue data
Front-end-Developer-Interview-Questions, from the h5bp project, is a list of front-end web development questions you can use to interview candidates, test your own knowledge or ignore entirely. It is a set of questions, not software, so there is nothing to install or run. This guide shows you how the list is organised, how to choose a few questions, and how to use them well.
Front-end Developer Interview Questionsh5bp/Front-end-Developer-Interview-Questions · ★ 60.9k · MIT Install options & downloads Quick start
- 1Open the project homepage. Go to the project homepage to read the questions online without installing anything.
- 2Pick the topics you need. Look at the table of contents and choose the topics that match the skills you want to assess.
- 3Clone the repository if you want a local copy. Run the git clone command from the README to download the files to your computer.
- 4Choose a small set of questions. Select a few questions across topics, since the README says using every question on one candidate would take hours.
- 5Run the discussion. Ask the questions, then follow up on the reasoning behind the answers rather than checking them against a key.
What is in the question list?
The repository is split into topic files. The README's table of contents lists General, HTML, CSS, JS, Accessibility, Testing, Performance, Network, Coding and Fun questions. Most topics link to a markdown file inside the src/questions folder, such as src/questions/html-questions.md. The Accessibility section links to an external set of questions instead.
The README is clear that you should not use every question on one candidate, since that would take hours. Choosing a few items should help you check the skills you need.
- General Questions
- HTML Questions
- CSS Questions
- JS Questions
- Accessibility Questions (external link)
- Testing Questions
- Performance Questions
- Network Questions
- Coding Questions
- Fun Questions
How do you read the questions?
The README notes that many questions are open-ended. They are meant to start a discussion that shows how a person thinks, rather than to be marked against a single right answer.
The project does not provide model answers, so judge responses by reasoning and clarity rather than by matching an answer key.
How do you get a copy of the questions?
You can read the questions online at the project homepage. If you want a local copy, the README gives this command to clone the repository.
Cloning requires git on your computer. The README does not list any other prerequisites.
git clone https://github.com/h5bp/Front-end-Developer-Interview-QuestionsHow do you build an interview from the list?
Start by listing the skills the role needs, such as CSS layout, accessibility or testing. Then pick a few questions from the matching topic files rather than working through the whole list.
Use a mix of topics so that one candidate is not assessed on a single area. Because the questions are open-ended, follow up with questions about why the candidate chose a particular approach.
- Write down the two or three skills that matter most for the role.
- Choose a few questions from the matching topic files.
- Mix a technical topic with a discussion-style question.
- Leave time for follow-up questions.
How can developers use the list to test themselves?
Developers preparing for front-end interviews can read the questions and answer them out loud or in writing. Because there are no answer keys, compare your reasoning with reference material you trust.
The Fun Questions and Coding Questions files give a lighter or more practical way in if you want to warm up before a harder topic.
How can teachers and mentors use the questions?
Teachers and mentors can use the questions as discussion prompts on web fundamentals. The open-ended style suits group talks where students explain their reasoning.
The list is not a course, so pair it with your own lessons or materials if you need a full curriculum.
What people use it for
- A hiring manager building a front-end interview process picks a few HTML, CSS and JavaScript questions.
- A developer preparing for a job interview tests their knowledge of accessibility or performance.
- A mentor uses open-ended questions to start a discussion on networking basics.
- A team keeps a shared pool of questions and selects different ones for each round.
Frequently asked questions
Is Front-end-Developer-Interview-Questions software I need to install?
No. The project is a list of questions, and the README says no code is run. The install method is read-online, so you can read the questions on the homepage or clone the repository for a local copy.
Does the project have answer keys?
No. The README describes many questions as open-ended and meant to lead to discussion rather than a single right answer. Judge responses by reasoning rather than by a model answer.
What license is Front-end-Developer-Interview-Questions under?
The project is licensed under MIT, as stated in the project information. The README links to a LICENSE.md file in the repository.
What topics does the question list cover?
The list covers General, HTML, CSS, JS, Accessibility, Testing, Performance, Network, Coding and Fun questions. Accessibility questions link to an external collection.
How many questions should I use in one interview?
The README says it is not recommended to use every question on the same candidate. Choosing a few items from the list should help you check the skills you need.
Are there alternatives to this question list?
The project information lists no comparable projects. For a complete course rather than a question list, you would need a separate learning resource.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This list suits hiring managers who want a shared pool of open-ended front-end questions, developers testing their own knowledge, and mentors who want discussion prompts. It is not a good fit if you want software to run, answer keys, or a full curriculum.
Install options & downloads