If you are deciding whether to talk to me, this page is the short version: what I am good at, how I work, and what it is like to hand me something.
I am a full-stack developer in Ahmedabad, currently building production web applications at NSEG Pvt Ltd and taking on selected work outside it. I work remotely with clients anywhere and in person around Ahmedabad.
What I am actually useful for: products that need one person who can hold the whole thing in their head. Frontend, API, database and the server it runs on. That is a poor fit for a large team with specialists already in place, and a very good fit when you need something to exist and work without assembling four contractors to build it.
Everything on this site is checkable. The case studies describe real systems, the resume lists real outcomes, and the code is on GitHub.
Concretely, what is in the box. Anything not listed is worth asking about rather than assuming.
Multiple full-stack products taken from architecture through to production deployment independently, including the infrastructure they run on.
The area most projects get subtly wrong. Password hashing, sessions and revocation, and role-based access that holds across routing, UI and API in products with five distinct roles.
Diagnosed from measurement rather than instinct. Cutting fifteen or sixteen API calls per page down to one is the kind of change that shows up in server cost, not only in a Lighthouse score.
Docker, Nginx, Linux, TLS, CI on merge, backups and health checks. I run my own infrastructure, so deployment is not a thing I hand to somebody else.
Runbooks, written scopes and case studies. If you cannot operate the thing after I leave, it was not finished.
The same five steps every time. The point of writing them down is that you can tell where a project is without asking.
Thirty minutes on what you are building, who it is for, and what has to be true for it to count as done. You leave with a written scope and a rough shape of the work, whether or not we go ahead.
Data model, API surface, auth model and hosting decided before any feature code. This is where the expensive mistakes get made, so it happens in writing first.
Work ships to a staging URL continuously, not in one reveal at the end. You see progress weekly and can redirect while redirecting is still cheap.
Auth and access control, input validation, rate limiting, error handling and the failure paths that only show up under real traffic. Treated as part of the build, not a later pass.
Containerised deploy, TLS, backups and a written runbook, into your infrastructure or mine. You get the repo, the credentials and a document that explains how to run it without me.
Every claim on this page points at something you can read. These are the three that matter most here.
Live video, recordings and a synchronised in-browser code editor, five roles with distinct permissions, weighted scoring with an audit trail, and production reliability work including idempotent webhooks, a retrying job queue and automated backups.
Read the Commit case studyStorefront and admin built without a framework, deliberately, to work through the parts frameworks hide: sessions, password hashing, cart state, coupon maths, order lifecycles and uploads, deployed as a multi-container Docker stack.
Read the e-commerce case studyFull-Stack Developer since February 2025, from intern to full-time. API call reduction, an admin dashboard with role-based access control, JWT sessions with admin-controlled revocation, and a rich-text editor integration including the image lifecycle around it.
See the full resumeThree shapes cover almost everything. Which one fits is usually obvious within ten minutes of the first call.
You have something specific to build
Written scope, milestones and one agreed price. The most common way people work with me.
Ongoing product work
A set number of days a month against a standing backlog, re-prioritised as the roadmap moves.
You are hiring, not contracting
Open to the right full-time role, remote or in Ahmedabad. The resume is the place to start, and the fastest first message is the one that says what you are building.
There is no fixed price list here, because a number quoted before the scope exists is a guess dressed up as a quote. These are the things that actually decide it:
The questions that come up on nearly every first call.
I take on a limited amount of work alongside my current role, so availability changes. Send a message with what you are building and you will get a straight answer about timing, including when the answer is no.
Both. Remote with clients anywhere, and in person around Ahmedabad where that is useful. Core hours are 10:00 to 20:00 IST.
What you are building, who it is for, and any hard deadline. That is enough for a first call. A design, an existing codebase or a written spec all help, and none of them are required.
Fixed price against a written scope for defined projects, or a monthly retainer for ongoing work. The number depends on scope, integrations and who owns the infrastructure afterwards, so it comes after the first call rather than before it.
Yes. The projects on this site link to their repositories, and the site itself is a full-stack application with an admin CMS, a database and a containerised deploy rather than a static template.
Tell me what you are building and what has to be true for it to count as done. You get a straight answer on fit and timing, including when the answer is no.