FrontendBackendGeneral
Monorepo
Also written as Turborepo, Nx
Keeping multiple projects or services in a single shared code repository, instead of splitting each into its own separate repo — makes sharing code and coordinating cross-project changes easier, at the cost of a larger, more complex repo.
Think of it like
Like one shared office building housing several different companies, versus each company having its own separate building across town.
Junior or senior?
Junior sounds like
Repeats that 'code sharing is easier' in a monorepo.
Senior sounds like
Names a specific tradeoff their team actually hit — build times, tooling complexity.
Ask them
“What made your team choose a monorepo over separate repositories, and what did that choice cost you?”