Superadmission is a small team building something large. This page is honest about both parts of that.Documentation Index
Fetch the complete documentation index at: https://team.superadmission.com/llms.txt
Use this file to discover all available pages before exploring further.
What the work actually is
The platform is approximately 85% complete. The first live pilot is the immediate priority. The work right now is the kind that determines whether a well-designed system survives contact with reality: integration engineering, pilot operations, policy engagement, design iteration from real student feedback. There is no large team to distribute work across. There is no established playbook for what you will be doing. Most of the interesting problems are ones that have not been solved before — because the infrastructure being built does not exist yet. If you want a defined role with a clear scope and a stable process, this is probably not the right place. If you want to own a real problem with real consequences, it might be.What this stage offers
Proximity to the problem. Superadmission’s research spans 5,247 students, 218 institutions, and 18 states. The founders worked directly with close to 2,000 students before writing a line of code. The work is grounded. You will understand why every part of the platform exists. Ownership that is real. At this size, the work you do is visible in the product. There is no middle layer between a decision and its effect. Infrastructure that matters. India’s admissions system affects every family with a student in higher education. The platform being built here will, if it works, change how millions of students navigate one of the highest-stakes processes in their lives. That is not a pitch. It is why the founders are working on this instead of something easier. Building with people who are serious. Aashrut and Unnati are not figuring out what they want to build. They have two years of fieldwork behind them, a working prototype, and a clear design for what comes next. The work environment reflects that: direct, specific, and focused on the problem.What this stage requires
Comfort with ambiguity. The pilot has not run yet. Not every system has been tested under real load. Some things will break and need to be fixed quickly. Generalist range. At this stage, everyone touches more than their primary domain. An engineer will need to understand the policy context. An operations person will need to understand the product. High tolerance for slow institutional processes. Getting a counselling authority to pilot a new system requires patience that startup timelines do not naturally accommodate. The work is worth doing. It does not move fast. Genuine interest in the problem. This is not a good place to build a resume entry. It is a good place to work on something that has not been done before, with a team that is serious about doing it well.See the Open Roles page for current openings. If nothing fits but you think you belong here, reach out anyway.