A Front-End Interview Prep Resource That Actually Answers the Questions

You've got a front-end interview coming up. You've read the same list of "50 most common JavaScript questions" a dozen times, and you still don't feel ready. The problem isn't finding questions—it's finding answers that actually explain the reasoning behind them. The interview-questions repository by Yauhen Kavalchuk takes a different approach: hundreds of questions organized by topic and difficulty level, each accompanied by a detailed video answer.

What It Does

This repository is a collection of technical interview questions for Junior, Middle, Senior, and Lead front-end and full-stack developer positions. The questions are grouped into thematic files, and within each file, they're further organized by difficulty level: Junior, Middle, Senior, and Lead.

The level designation is worth understanding. According to the README, a question's level represents the minimum level at which an answer is expected. A Junior question is fair game at a Middle or Senior interview too—it's a floor, not a ceiling. The levels were determined using skill matrices for JavaScript developers (both front-end and full-stack), adjusted for the complexity of each specific question.

The topics covered are broad. Web Technologies (HTTP, APIs, storage, CSR/SSR, PWA), Architecture (MVC, MVVM, microservices, DDD, microfrontends, FSD), Security (XSS, CSRF, CSP, JWT, CORS), Browser Rendering, OOP and Functional Programming, HTML, CSS, JavaScript, JS in Browser, Async JS, ECMAScript, Accessibility, Performance, and TypeScript. The question counts vary significantly—JavaScript has 94, HTML has 76, CSS has 70, while Browser Rendering has just 7. This suggests the collection reflects actual interview patterns rather than an attempt to pad every topic equally.

Each question comes with a video answer. The README mentions that some videos are gated behind an access mechanism, with a link to instructions on how to get access.

Why It's Cool

• Video answers change the preparation dynamic. Reading a written answer is fine, but watching someone explain a concept—especially one as visual as, say, the event loop or browser rendering—is a different experience. You get tone, emphasis, and the natural flow of an explanation. For topics like async JavaScript or CSS layout, this matters.

• The leveling system is honest. The README doesn't pretend every question is equally important for every role. It explicitly states that a question's level is the minimum where it's expected, and that levels were calibrated against actual skill matrices. That's a more useful framing than the typical "beginner/intermediate/advanced" labels that mean different things to different people.

• The topic coverage is unusually complete. You don't often see a single resource that covers security (XSS, CSRF, CSP, JWT, CORS) alongside accessibility (WCAG, ARIA, screen readers, focus management) alongside architecture (DDD, microfrontends, FSD). Most interview prep materials pick a lane. This one doesn't.

• It's a living collection, not a static list. The repository is organized as a set of markdown files, one per topic. That structure makes it easy to navigate to exactly what you need—if you know you're weak on TypeScript or performance, you can go straight to those files.

• The question counts tell you something. The distribution across topics—heavy on JavaScript, HTML, and CSS, lighter on architecture and performance—reflects where interviews actually spend their time. It's a subtle signal about what to prioritize if you're short on preparation time.

How to Try It

1. Go to the repository: https://github.com/yauhenkavalchuk/interview-questions

2. Browse the topic files. Each one is a markdown file in the questions/ directory. For example:

   • questions/js.md for JavaScript
   • questions/css.md for CSS
   • questions/security.md for security topics
   • questions/architecture.md for architecture

3. Within each file, questions are grouped by level (Junior, Middle, Senior, Lead). Start at the level you're targeting, but don't skip the lower levels—they're often asked at higher-level interviews too.

4. For video answers, follow the link in the README about accessing the videos. Some are public, some require access.

5. If you find it useful, star the repo. The README asks for it, and it's a reasonable ask for a free resource.

There's also a YouTube channel linked in the README with more materials, which is worth checking if you prefer video content.

Final Thoughts

This isn't a course or a structured curriculum—it's a reference. You won't get a guided path from "I know nothing" to "I'm ready for a Senior interview." What you get is a well-organized, honestly leveled set of questions with video explanations, covering a wider range of topics than most interview prep resources bother with.

It's best for developers who already have some foundation and want to identify gaps, or for those who learn better by watching explanations than reading them. If you're preparing for a specific interview and you know the company focuses on, say, JavaScript internals and performance, this gives you a direct way to drill into those areas. If you're just starting out, the Junior-level questions across topics will give you a sense of what's expected, but you'll probably need additional structured learning alongside it.

The repository is free, open, and maintained. That's a good combination for a resource you'll likely return to more than once.