Project structure and boundaries
Comes up in: Frontend system design, Hiring manager
This concept is being written. It gets the full five steps — explanation, predict, interview angle, practice with tests, and review cards. Here is exactly what it will cover, so you can study it elsewhere in the meantime.
What it covers
- feature-based folders
- public APIs per feature
- dependency rules (lint-enforced)
- monorepos (Turborepo/Nx) awareness
- shared UI kit vs feature code
Words you will know
What you will practise
- restructure a sample app
Interview questions this answers
- How would you structure a large React application with 10 teams?
- How do you keep a shared component library consistent across teams?