Question 1

Feature-based folder structure vs type-based (components/hooks)?

Accepted Answer

Feature folders scale better by colocating related UI, hooks, and tests. Type-based folders become dumping grounds. Shared UI stays in a design-system package.

Question 2

How do you design a design system with React?

Accepted Answer

Primitives with a11y, tokens, composition APIs, documented variants, and strict versioning. Avoid business logic in DS components. Provide headless + styled layers if needed.

Question 3

Handling cross-cutting concerns (auth, analytics, errors)?

Accepted Answer

Providers at the app shell, route guards/loaders in the framework, centralized error boundaries. Keep feature code free of SDK spaghetti via thin adapters.

Question 4

When to introduce microfrontends with React?

Accepted Answer

Independent deployability across teams outweighs complexity—rare for small orgs. Prefer modular monolith with clear package boundaries first.

Question 5

Lead: code review standards for React PRs?

Accepted Answer

Purity of render, effect necessity, a11y, perf hotspots, test coverage for logic, API boundaries. Reject prop-drilling explosions and untyped any. Prefer incremental refactors.

Architecture React Interview Questions

Other React interview topics