Currently building
Yugaantar 2026 ↗
Technical-team work on Scaler’s annual fest platform, from sign-in to participant records, submissions and staff administration. A successful login is only the entrance: the participant needs a consistent record afterwards, and the staff need enough context to handle imports, claims and follow-up work. This builds on the operational lessons of Ascent, within a different team and platform. The implementation repository is private.
Hermes / HKV ↗
A personal knowledge system built around an entity store, an event log and projections. The question is what an assistant should be able to remember, how a change becomes part of that history, and how useful views can be reconstructed without treating the latest chat message as the only source of truth. The public description stays at that systems level; personal records and private operational details are not part of this portfolio.
ParaPixel DigiServices ↗
Client-platform work as a co-founder of the agency I started with a friend in a hostel room. A website, application or CRM begins with somebody else’s workflow: understanding what they need, choosing the shape of the system, delivering it and staying involved when real use exposes the next issue. Requirements, deployment and maintenance are part of the same engineering responsibility. Client-specific implementation and business details remain private.
Exploring & learning
- Versioned research artifacts and collaboration through ReGit.
- Evidence-aware interfaces in the AgriSense local prototype.
- Developer tools that keep data and control close to the user.
Academic work
Studying computer science at Scaler School of Technology and BITS Pilani. No specific current assignment is published here.
Working together
Team projects include ReGit with Amrit Kang and the Ascent platform. Current public role descriptions are listed on the experience page.
Snapshot source: public GitHub profile. Private implementation details are not included.