I'm a Computer Science undergraduate who cares more about why a system is built a certain way than about shipping another CRUD app. I like digging into the reasoning behind design decisions — not just what a feature does, but the thinking that shaped it.
- 🏗️ Currently deep-diving into system design — SOLID, design patterns, queues, caching, idempotency, and the trade-offs behind them
- 🌐 Building with the MERN stack, moving toward production-grade patterns and deployment workflows (Kafka, Redis, Docker, CI/CD)
- 🎯 Goal: To build products that are not just deployed, but also implement scalable techniques and efficient patterns — making them reliable, secure, and available to all users. Working toward 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.
|
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. |
Voice deepfake/spoof detection system (Smart India Hackathon project) with dual PyTorch/ONNX inference engines supporting English and Indic languages. |
|
Started as a Streamlit + CrewAI prototype, now being rebuilt as a full MERN application with expanded system-design components. |
Full-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.