2026 — present
Asisfera — multi-tenant shift scheduling platform
QA Lead
Impact
The system went from serving a single organization to serving several without any of them seeing another's data — solving the hardest case first: knowing who you are before you've logged in.
The problem
An attendance and shift-scheduling platform needed to serve multiple organizations (multi-tenant) without each one seeing another's data, added on top of a system that wasn't originally designed to be one.
The approach
The API contract between frontend and backend lives in a shared/ package
with Zod schemas both sides import from the same definition — the contract
is validated at runtime on both ends from a single source of truth, not two
copies that can drift out of sync.
The hard part of multi-tenancy wasn't the data model but resolving which organization a user belongs to during login and "forgot my password" flows — moments where there's no authenticated user yet to derive the tenant from, and it has to be resolved beforehand.
The test suite runs with Vitest and Supertest on the backend, Testing Library on the frontend, and Playwright for e2e, all on top of Docker Compose.
Result
The system went from serving a single organization to serving several without any of them seeing another's data — solving the hardest case first: knowing who you are before you've logged in.