Monorepo vs. Micro-Frontends
Both come up when large frontend teams talk about 'splitting things up', so they sound like rival choices. They answer different questions. A monorepo is about where code is stored: many projects kept in one repository so they can share code and change together. Micro-frontends are about how a website is built and shipped: one site split into pieces that separate teams build and release on their own. A company can use both at once — micro-frontends kept in a monorepo is common — so neither one implies the other.
How to tell them apart on a resume
Monorepo (where code lives)
Nx, Turborepo, Lerna, pnpm or Yarn workspaces, Bazel, shared libraries, build caching, CI speed-ups — often a platform or developer-experience focus.
Micro-frontends (how the app is split)
Module Federation, single-spa, independent deploys per team, a 'shell' or host app, shared design system across teams — usually a large product with many frontend teams.
The question that settles it
“Was the problem you solved about keeping many projects in one repository, or about letting separate teams release parts of one website independently — or both?”
Read the full definitions
Open the full tool for the other look-alike pairs, role profiles, and the JD decoder.