Aman Kumar Singh — Team Lead & Senior Software Engineer. React, Next.js, Node.js, NestJS, PostgreSQL, Redis, and AWS.
Also searched as Silvassa and Daman.
This territory is a dense industrial belt of manufacturing units feeding Gujarat and Maharashtra supply chains, packed into a very small area. Production tracking and dispatch systems that have to work on a factory floor — on shared terminals, with gloves on — not just in an office browser.
I am Aman Kumar Singh — a Team Lead and Senior Full Stack Engineer based in Noida with 6+ years of experience, 15+ production applications shipped, and teams of 5–10 engineers led. An unusually dense manufacturing belt for its size.
Dadra and Nagar Haveli and Daman and Diu engagements run remote-first from my base in Noida, with a scheduled on-site visit for kickoff or a major release when it is worth the flight. Everything is on IST, so there is no timezone gap — same working day, same standup.
Frontend
React.js · Next.js · JavaScript (ES6+) · TypeScript · HTML5 · CSS3
Backend
Node.js · NestJS · REST APIs · Web API · Microservices · MVC · OAuth
Databases
PostgreSQL · MySQL · MongoDB · Redis · SQL
DevOps & Cloud
AWS · AWS SQS · Docker · Kubernetes · CI/CD
Ways of working
Agile · Scrum · Code Review · System Design · Mentoring · Payment Integrations
Tell me what you are building and the rough timeline, and I will come back with a scope and an estimate for a first phase — not a generic proposal.
Yes. Dadra and Nagar Haveli and Daman and Diu engagements run remote-first from my base in Noida, with a scheduled on-site visit for kickoff or a major release when it is worth the flight. Everything is on IST, so there is no timezone gap — same working day, same standup.
Production tracking and dispatch systems that have to work on a factory floor — on shared terminals, with gloves on — not just in an office browser. Concretely, that tends to mean lot tracking, production planning, and export order management, consignment tracking, routing, and multi-party coordination, and production tracking, dispatch, and shop-floor dashboards that are readable at a glance. The stack is React and Next.js on the front end, Node.js and NestJS services behind it, PostgreSQL and Redis for data, and AWS for deployment.
Yes, and with an established Dadra and Nagar Haveli and Daman and Diu team that is often the better arrangement. I have led teams of 5–10 engineers and spent a lot of time in code review and mentoring, so joining an existing codebase to raise the standard — testing, CI, module boundaries, review culture — is familiar work rather than a compromise.
You do, outright. For Dadra and Nagar Haveli and Daman and Diu work in particular — where I am usually not in the building — I plan the handover from the first sprint: readable module boundaries, a written architecture note, and setup documentation your team can follow without me. Ongoing support afterwards is a separate arrangement, never a dependency I engineer in deliberately.
A focused first version is typically 6–12 weeks depending on scope. Given that production tracking and dispatch systems that have to work on a factory floor — on shared terminals, with gloves on — not just in an office browser. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Dadra and Nagar Haveli and Daman and Diu client is usually about cutting scope to the part that proves the idea.
The reasoning behind how I build — 200+ articles on architecture, backend, and performance.