I built a frontend interview practice site focused on real UI work (not just LeetCode)
I kept seeing the same pain during interview prep:
- Tons of sites = algorithms first, UI later
- Frontend questions are often “real work” prompts (state, events, async, rendering, performance)
- It’s hard to practice in a structured way without drowning in tabs/spreadsheets
So I built FrontendAtlas — a practice hub where you can solve frontend-focused questions and build interview momentum.
👉 Try it: https://frontendatlas.com/ and also here https://frontendatlas.com/coding
What makes it different (in one minute)
Instead of “solve 200 random problems”, the idea is:
✅ Frontend-realistic prompts (UI logic, state, DOM/events, async flows, components)
✅ Clear progression (so you don’t get stuck doing only easy or only hard)
✅ Senior-friendly framing (trade-offs, edge cases, performance mindset)
If you’ve ever thought “I can code, but interview prompts feel… different”, that’s what I’m targeting.
What you can practice
A few examples of the type of stuff I care about:
- JavaScript fundamentals that show up in real interviews (closures, async, events)
- DOM manipulation & event delegation
- Component/state patterns (the “UI brain” stuff)
- Performance-ish thinking (rendering, memoization, unnecessary work)
- Framework-oriented practice (Angular/React style patterns)
Who it’s for
- Frontend devs who want job-realistic practice
- People preparing for mid/senior roles
- Anyone tired of grinding generic puzzles and wants “frontend muscle” instead
I’d love feedback (so I don’t build in a cave 😅)
If you take a quick look, I’d love your thoughts on:
1) What’s missing from a great frontend practice experience?
2) What kinds of prompts feel most “real interview” to you?
3) What would make you come back weekly?
Link again: https://frontendatlas.com/coding
Thanks 🙌
Top comments (0)