Github · GitHub Repository Radar
h5bp Front-end-Developer-Interview-Questions
A list of helpful front-end related questions you can use to interview potential candidates, test yourself or completely ignore.
Stars
60,869
Forks
10,984
Watchers: 60,869
Language
License: MIT License
Repository Radar Score
54 / 100
Growth
- 7d
- +0
- 30d
- +0
- %
- 0.0%
Not enough metric snapshots yet to chart growth for this repository.
Score breakdown
- popularity 89
- growth 0
- activity 55
- freshness 100
- community 66
Need help integrating this stack?
Our team builds with modern open-source stacks. Tell us what you are shipping.
Get a quote →This repository contains a number of front-end interview questions that can be used when vetting potential candidates. It is by no means recommended to use every single question here on the same candidate (that would take hours). Choosing a few items from this list should help you vet the intended skills you require.
Note: Keep in mind that many of these questions are open-ended and could lead to interesting discussions that tell you more about the person's capabilities than a straight answer would.
You can read more about this project & its history here.
- General Questions
- HTML Questions
- CSS Questions
- JS Questions
- Accessibility Questions (external link)
- Testing Questions
- Performance Questions
- Network Questions
- Coding Questions
- Fun Questions
The project is currently maintained by:
Feeling inspired? Check our Contributing guide to get started!
Copyright (c) Contributors of the Front-end Developer Interview Questions
Repository Radar analysis
Deterministic insights derived from public metadata and our observations — not personal testing or reviews.
Why this repository is interesting
- High absolute popularity (60,869 stars) signals broad adoption.
Who should use it
- Developers working primarily with Nunjucks
- Teams exploring AI tooling, agents, or ML infrastructure
Potential use cases
- Reference or evaluate Nunjucks open-source approaches in this domain
- Prototype AI/agent workflows or study reference architectures
Strengths
- README present in our index
- Declared license: MIT License
- Substantial fork count (10,984) suggests reuse and contribution interest
Limitations / considerations
- Insights are derived from public metadata and our observations — not a substitute for code review
What to watch
- Re-check last push, issues, and releases on GitHub before production adoption
Strong signals: Strong community interest
Source: GitHub (public metadata) + Repository Radar analysis. We do not claim ownership of third-party repositories.