I'm a Computer Science undergraduate who cares more about why a system is built a certain way than about just shipping another CRUD app. I like understanding the reasoning behind a design decision — not just what a feature does, but the thinking that shaped it.
🏗️ Currently deep in system design — queues, caching, idempotency, and the trade-offs behind them 🌐 Building with the MERN stack, moving toward production-grade patterns (Kafka, Redis, Docker, CI/CD) 🎯 Goal: land a high-impact SDE role at a product company by shipping projects that hold up under real technical scrutiny, not just demo well
Building and deploying full-stack systems, backed by an understanding of how they scale.
- Student Record Management System — Full-stack MERN platform with 3 role-based portals, event-driven payments (Kafka + idempotent consumers), Redis caching, Socket.IO real-time features, JWT + TOTP MFA, and CI/CD via GitHub Actions.
- VoiceShield — Voice deepfake/spoof detection system (Smart India Hackathon project) with dual PyTorch/ONNX inference engines supporting English and Indic languages.
- Federal Job AI Assistant — Started as a Streamlit + CrewAI prototype, being rebuilt as a full MERN application with expanded system-design components.
- Dayflow HRMS — Free-stack HRMS built with a 4-person team for an Odoo hackathon.
Right now I'm working backward from the fundamentals — OOP, then SOLID, then design patterns — and testing each one against real practice problems before calling it understood. The goal is to make the system-design work above something I can actually defend in a room, not just something I shipped once.