What is this?
A curated list of front-end interview questions covering HTML, CSS, JavaScript, accessibility, testing, performance, networking, and coding exercises that hiring managers can pick from when vetting front-end developer candidates.
A curated list of front-end interview questions covering HTML, CSS, JavaScript, accessibility, testing, performance, networking, and coding exercises that hiring managers can pick from when vetting front-end developer candidates.Is this something I install, or just a document I read?It is just a README/question bank - there is nothing to install or run; you browse the categories and copy the questions you want to ask or study.
It is just a README/question bank - there is nothing to install or run; you browse the categories and copy the questions you want to ask or study.How is the list organized?Questions are grouped into ten sections: General, HTML, CSS, JS, Accessibility (external link), Testing, Performance, Network, Coding, and Fun Questions.
Questions are grouped into ten sections: General, HTML, CSS, JS, Accessibility (external link), Testing, Performance, Network, Coding, and Fun Questions.Should I ask a candidate every question on the list?No - the maintainers explicitly warn against running through every item with one candidate since that could take hours; pick a few that test the skills you actually need.
No - the maintainers explicitly warn against running through every item with one candidate since that could take hours; pick a few that test the skills you actually need.Is this for interviewers only, or can candidates use it too?Both: interviewers use it to vet candidates, and developers can use the exact same list to self-test or prep before an interview.
Both: interviewers use it to vet candidates, and developers can use the exact same list to self-test or prep before an interview.Are the questions multiple-choice or open-ended?Mostly open-ended. The maintainers note many questions are meant to spark discussion and reveal more about a candidate's thinking than a straight answer would.
Mostly open-ended. The maintainers note many questions are meant to spark discussion and reveal more about a candidate's thinking than a straight answer would.Is the list still maintained?Yes, it is actively maintained by @roblarsen with a long list of community contributors and a dedicated contributing guide.
Yes, it is actively maintained by @roblarsen with a long list of community contributors and a dedicated contributing guide.Where are the Accessibility questions?They are not inline in this README - the Accessibility section is kept as a separate linked document.
They are not inline in this README - the Accessibility section is kept as a separate linked document.What are similar projects?front-end-interview-handbook, fe-interview, CS-Interview-Knowledge-Map, markyun, frontend-challenges, blog, junior-recruit-scheduler, professional-programming
front-end-interview-handbook, fe-interview, CS-Interview-Knowledge-Map, markyun, frontend-challenges, blog, junior-recruit-scheduler, professional-programmingWhich topics is it in?hiring, coding-interview, front-end, coding, static-site-generator, interview-questions, interview, best-practices, accessibility, career, skills, testing
hiring, coding-interview, front-end, coding, static-site-generator, interview-questions, interview, best-practices, accessibility, career, skills, testing