Aman Kumar Singh — Team Lead & Senior Software Engineer. React, Next.js, Node.js, NestJS, PostgreSQL, Redis, and AWS.
Also searched as Bharat.
India's software economy runs on several distinct engines at once: product engineering in Bengaluru and Pune, global capability centres in Hyderabad, financial platforms in Mumbai and Gurugram, and a tier-2 base in Indore, Kochi, Coimbatore, and Bhubaneswar that has become genuinely competitive rather than merely cheaper. What that means in practice: across all of it, the recurring need is the same: someone senior enough to choose an architecture that will still hold in two years, and hands-on enough to build it. That is the work I do — React and Next.js on the front, Node.js and NestJS services behind it, PostgreSQL and Redis underneath, deployed on AWS.
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. One country, several very different software economies — and I work remote-first across all of them from Noida.
I work remote-first from Noida with clients across India. Every city here is on IST, so there is no timezone gap to manage — same working day, same standup, same-day answers. For a kickoff, an architecture workshop, or a major release, I travel when being in the room genuinely changes the outcome.
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. I work remote-first from Noida with clients across India. Every city here is on IST, so there is no timezone gap to manage — same working day, same standup, same-day answers. For a kickoff, an architecture workshop, or a major release, I travel when being in the room genuinely changes the outcome.
Across all of it, the recurring need is the same: someone senior enough to choose an architecture that will still hold in two years, and hands-on enough to build it. That is the work I do — React and Next.js on the front, Node.js and NestJS services behind it, PostgreSQL and Redis underneath, deployed on AWS. Concretely, that tends to mean catalogue, cart, and order-management systems built for festive-season peaks, production tracking, dispatch, and shop-floor dashboards that are readable at a glance, and admissions, fees, and exam platforms that survive results-day traffic. 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 India 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 India 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 across all of it, the recurring need is the same: someone senior enough to choose an architecture that will still hold in two years, and hands-on enough to build it. That is the work I do — React and Next.js on the front, Node.js and NestJS services behind it, PostgreSQL and Redis underneath, deployed on AWS. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a India 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.