Building systemsthat don't just work.They scale.
I design and build APIs, backend systems, payment infrastructure, and full-stack products engineered for real-world scale.
An engineer who thinks in systems.
I'm a full-stack developer with 3+ years of experience building scalable Node.js backend systems and payment platforms serving thousands of users.
My focus sits at the intersection of backend architecture and product engineering: RESTful APIs, authentication, databases, AWS infrastructure, and the frontend that ties it together. I care less about any single framework and more about how the pieces fit: where state lives, what a service owns, and what happens when an API has to change without breaking the clients depending on it.
Increasingly complex systems.
Three years, three engineering environments, each one raising the stakes on scale, compliance, or the number of moving parts a single service has to coordinate.
ABSS LLP
August 2025 - PresentFullstack Developer
Building a SaaS ERP platform: custom billing systems, discount engines, and GST-compliant invoicing for inventory-heavy businesses.
- Enabled generation of 5,000+ e-invoices and e-way bills
- Reduced manual effort through streamlined workflows
- Built flexible billing and pricing logic for a SaaS ERP platform
Enstead
September 2024 - July 2025Fullstack Developer
Worked on EpicPay, a payment solutions platform serving 10,000+ users, building backend microservices designed to evolve without breaking existing clients.
Epoch Software Services
May 2023 - August 2024Backend Developer
Worked across multiple products spanning mobility, marketplace, and travel, from real-time vehicle tracking to commission-based marketplace payments.
RAS
Car rental platform with end-to-end booking management, real-time vehicle tracking, and route optimization.
EventBazaar
Marketplace platform connecting hair stylists and customers, with stylist verification, product management, and a 15% commission model.
Destify
Intelligent travel booking platform covering flights, hotels, and activities.
Engineering problems, solved end to end.
Four systems, four different pressures: flexible pricing, evolving payment APIs, real-time location, and a two-sided marketplace. Hover any diagram to trace how a request moves through it.
Custom Billing & Discount Engine
- The Context
- ABSS LLP's ERP platform needed a billing layer flexible enough to handle varied customer pricing, add-ons, and India's GST compliance requirements, all without hardcoding logic per customer.
- The Challenge
- Pricing wasn't uniform. Customers needed custom discount rules, optional add-ons, and Razorpay-based payment collection, all while generating compliant e-invoices and e-way bills at volume.
- The Engineering Approach
- Designed a pricing pipeline that composes base pricing, add-ons, and discount rules as discrete, ordered steps rather than one tangled calculation, so new pricing logic could be added without touching existing rules. Integrated Razorpay for payment collection and wired the flow into GST-compliant invoice generation.
Hover a node to trace its connections
EpicPay: Payment Infrastructure
- The Context
- EpicPay is a payment solutions platform serving 10,000+ users, requiring identity verification, secure authentication, and real-time client notifications on top of a Node.js backend.
- The Challenge
- The platform needed to keep shipping new capability (ID verification, selfie authentication, admin tooling) without breaking mobile clients already integrated against existing API contracts.
- The Engineering Approach
- Built backend microservices on Node.js and AWS Lambda behind versioned RESTful APIs, so new endpoints and behavior changes could roll out under a new version while older clients kept working against the version they were built for. JWT handled authentication; WebSockets pushed real-time state to clients and admin systems.
Hover a node to trace its connections
RAS: Car Rental Platform
- The Context
- RAS is a car rental platform needing end-to-end booking management alongside live vehicle location, not just a booking form bolted onto a map.
- The Challenge
- Bookings needed to reflect real vehicle availability, and customers needed accurate tracking and routing once a rental was underway.
- The Engineering Approach
- Built the booking engine in Node.js against MongoDB for availability state, and layered the Google Maps API on top for live vehicle tracking and route optimization, keeping booking logic and location logic as separate concerns that meet at the vehicle record.
Hover a node to trace its connections
EventBazaar Marketplace
- The Context
- EventBazaar connects hair stylists with customers as a two-sided marketplace, requiring trust (verification), catalog management, and commission-based payments.
- The Challenge
- The platform needed to support two distinct user types plus admin oversight, verified stylist onboarding, product management, location-aware discovery, and a working commission model on top of real payments.
- The Engineering Approach
- Built on Express.js and MongoDB with distinct flows for customers, stylists, and admins. Stylist verification gated marketplace participation; Google APIs handled location-aware discovery; Stripe handled payment capture with a 15% commission split processed on top of each transaction.
Hover a node to trace its connections
How I think about engineering.
Build for Change
Software requirements change.
Good architecture is not about predicting everything. It is about designing systems that can evolve without forcing a rewrite.
APIs Are Long-Term Contracts
An API is not just a route returning JSON. It is an agreement between systems.
Versioning, backward compatibility, consistency, security, and developer experience are the terms of that agreement.
Scale Is an Architecture Problem
Before adding more servers, understand the bottlenecks.
Data flow, database design, service boundaries, caching opportunities, and infrastructure constraints. Scale is decided long before load hits.
Complexity Should Be Intentional
Avoid unnecessary abstractions.
Use complexity only when the problem actually requires it.
What I write about.
Writing about the engineering problems behind the code: from API evolution to designing real-world billing systems.
The stack, as a system.
Not a list of badges. A request's actual path, from interface down to infrastructure, with tooling running alongside all of it.
Have a system worth building?
Whether it's a new product, a complex backend problem, or a system that needs to scale, let's talk.