Full Stack Engineer focused on building production-ready applications — from REST APIs and real-time systems to React frontends and server-rendered apps. I care about how systems are structured, not just that they work.
Currently deepening my understanding of AI integration , system design, and cloud infrastructure — with the goal of building smarter, more scalable products.
Frontend React - Next · Angular · Vite · TailwindCSS · Redux · Context API · GSAP · Socket.io (client)
Backend Node.js · Express.js · MongoDB · Mongoose · SQL - REST APIs · Socket.io · Passport.js · JWT
Auth & Uploads JWT · Cookie-based Auth · Google OAuth · Tokem Auth - Cloudinary · Multer
Payments & Email Razorpay · Nodemailer
BaaS & Tools Appwrite · Git · Postman · Render · Vercel
Currently Learning AI/ML Integration · System Design · AWS / Cloud Infrastructure
| Project | What it is | Stack | | Scribbly | Full-stack note-taking app with JWT cookie auth and search | Node · Express · React · MongoDB | | IntelliSocial | Social media backend with Google OAuth, Socket.io, and AI features in progress | Node · Express · MongoDB · Socket.io | | Ecom Backend | Production e-commerce API — cart, orders, Razorpay payments, Cloudinary images, admin panel | Node · Express · MongoDB · Razorpay | | visionBoard | Pinterest-style pinning app with boards, follows, and image uploads | Node · Express · MongoDB · EJS | | Gatherly | Real-time chat app — one-to-one and group chat with online presence tracking | Node · Socket.io · MongoDB | | NoteWave | Full-stack blog platform with Appwrite BaaS and Redux state management | React · Redux · Appwrite | | UdhaarPe | Digital khata app for shopkeepers — tracks credit without manual entry | Angular · TypeScript | | Hotel Odisej Clone | High-fidelity frontend clone with GSAP scroll animations and Locomotive Scroll | HTML · CSS · GSAP |
I don't just write code that runs — I think about how it's organized and why. Most of my backend projects use a DAO layer to keep database queries out of controllers, middleware for cross-cutting concerns like auth and validation, and separate config files for third-party services. It's not over-engineering — it's just making things easier to work with six months later.
On the frontend I care about state predictability, loading states that actually make sense, and UIs that give users feedback when something happens. Small things, but they add up.
Right now I'm studying system design patterns and cloud infrastructure so I can own more of the stack — from the database schema to the deployment pipeline.
- Building AI-powered Products
- Understanding how system design Wroks — scaling, caching, load balancing, distributed systems
- Understanding AWS — EC2, S3, Lambda, and cloud deployment patterns
- Open to remote roles at product-focused startups
I build things that work, structure things that last, and document things that matter.