Team
People who have run this problem before
We are a privately held company and we are not publishing individual profiles yet — named ones are coming. In the meantime we would rather you judged the team by the work, which is already public and already checkable.
Engineering leadership
Our engineering leadership comes out of IIT and Meta, with more than twenty years each building and operating large distributed systems — the kind where a single bad assumption shows up as an incident rather than a failing test.
Why this team builds this product
Multi-tenant isolation, field-level access control, audit and transactional rollback are not novel problems. They are problems this team has already solved several times, at a scale where getting them wrong is expensive and public. Supero is the attempt to solve them once, properly, and stop rewriting them per application.
How we work
Remote, across the San Francisco Bay Area and Bengaluru, with one deliberate overlap window rather than a handoff wall. Almost everything is written down — which is why the writing matters to us more than it usually does at this stage.
Judge us on this instead
Three things you can check in about ten minutes, without talking to us.
The applications
Sixteen of them, running at real URLs, generated by the same pipeline and governed by the same substrate.
supero.dev/appsThe engineering writing
Long-form pieces on the problems this team actually hits — including one on a permissions bug we found in our own API.
Read oneWhat we do not do yet
Our security page names its own gaps. That section is the reason the rest of it is worth reading.
supero.dev/securityWe are hiring
Several roles at once, across backend, full-stack, infrastructure and developer support, plus one internship. There is also a build challenge that replaces the screening call — it works even if your CV would not otherwise get past us.