Aashrut Sharma

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.

He also designed the institutional intake workflows: how colleges receive pre-verified student records, how seat matrices are structured, and how the system signals vacancy to institutions in real time.What makes that range possible is where the knowledge came from. Aashrut did not study the admissions problem. He operated inside it.

​

From ground operations to infrastructure design

Before writing a line of platform architecture, Aashrut ran an admissions consultancy, CollegeCult, that worked directly with approximately 2,000 students through live counselling cycles. Every intake interview, every preference list, every deadline tracked, every document cross-referenced was done by hand, for a real student, with a real outcome riding on it. That experience produced something that no amount of user research produces on its own: an operational understanding of exactly where the system loses people, and why. Not at the level of “students find it confusing”, but at the level of which specific step, in which specific counselling, under which specific timing constraint, causes students who should have gotten there to not get there. He also spent significant time on the institutional side, working with admissions officers at colleges to understand what the intake process looks like from their end. What the administrative overhead of running document verification looks like at scale. Where coordination breaks down between the institution and the counselling authority. What a well-designed intake flow would need to do differently for officers to trust it. That dual picture, student journey and institutional journey, is what Superadmission’s architecture is built on. The platform is not designed from the outside looking in at admissions. It is designed from inside the operation looking at what the operation should not have to do.

---

​

What he has built

Public documentation: docs.superadmission.com

---

​

How he thinks about the problem

Aashrut’s framing of the admissions problem is infrastructure-first, not product-first. His reference point is not “how do we improve the student experience inside the existing system”. It is “what shared layer underneath the existing system would make the experience a non-issue”. That framing leads to different design decisions. A product optimises for what students can do within the current architecture. Infrastructure removes the architectural constraints. The difference shows up in the allocation engine: rather than helping students navigate a fragmented multi-counselling process, the engine is designed so that honest preference expression always produces the best possible outcome. The problem students currently hire consultants to solve is eliminated by the design. He applies the same logic to the institutional side. Colleges should not need to run their own document verification for students who have already been verified. Admissions officers should not be reconciling intake data with counselling databases manually. These are coordination failures that belong in the infrastructure, not in every institution’s admissions office.

---

​

Background and recognition

AFS Intercultural Programs, Delhi Chapter Head — Managed intercultural exchange engagements and hosted participants from diverse global backgrounds.

• Italy Host: Feb 2022 – Dec 2022
• Germany Host: July 2024 – Aug 2024
• Korea Host: March 2025 – April 2025

IEEE Technical Director (2024–2025) — Defined technical roadmaps and provided senior leadership across strategic planning, technical standards, and operational execution. Independent research — Ongoing work on sovereign digital infrastructure for admissions: workflow design, seat allocation logic, OCR-based verification systems, and policy-aligned public infrastructure models under NEP 2020.