Project: Multi-tenant billing platform
You have written that the billing platform was multi-tenant. Walk me through how one tenant’s data stays invisible to another.
Why they ask: Resume claims multi-tenant architecture experience · Very likely
Every table carried a tenant id, and all queries went through a repository layer that injected it from the request context, so no query could be written without it. On top of that we turned on row-level security in Postgres as a second net, in case application code ever got it wrong. For noisy neighbours we rate-limited per tenant at the gateway. If I were building it again for larger customers I would look at a schema per tenant, because the single-table approach made per-tenant backups harder than I expected.