Journey
How I got here.
The origin story, the college leadership roles, and what I do outside the terminal - separated from the work itself, which lives on the other pages.
Background
How I got into software engineering
I started with problem solving through competitive programming - 1350+ problems across LeetCode, Codeforces, and CodeChef - and that habit of breaking down hard problems stuck. It pulled me naturally toward backend engineering, where the problems are about concurrency, data consistency, and holding up under load. I care about writing code that is simple to reason about, easy to monitor, and dependable when it matters most.
Leadership Roles
Engineering is a team sport. These roles shaped how I think about ownership, communication, and building things that last beyond any single person.
President | WCE-ACSES
Led the departmental club, organized national-level events with 1000+ participants, and improved cross-team execution workflows.
Chief Coordinator | Vision'25
Managed operations for a national-level technical symposium and led event execution for 1000+ participants across logistics and stakeholder coordination.
Technical Team | WCE ACM
Built hackathon registration tooling, curated assessments, and coordinated ACM Hackathon operations with real-time participant support.
Advisory Member | WCE MLSC
Founding member of WCE MLSC (2024-25). Helped design the board structure and protocols, assisted in conducting events, and contributed to organizing domain-specific workshops.
Beyond Code
Life outside the terminal
I was President of WCE-ACSES and Chief Coordinator of Vision'25, running national-level events with 1000+ participants. That work taught me that good engineering and good coordination share the same root: clarity, ownership, and not panicking when things break. Outside all of this, I play badminton - inter-college winner and two-time inter-zonal selection.
