Aman Kumar Singh — Team Lead & Senior Software Engineer. React, Next.js, Node.js, NestJS, PostgreSQL, Redis, and AWS.
Also searched as Gautam Buddh Nagar.
Noida is where I actually live and work. Sectors 62, 63, and 125 hold a dense cluster of product companies and IT services firms, and the city has quietly become one of North India’s two real tech centres. Noida projects usually start with an in-person kickoff and continue hybrid, because I am based here and can be on site the same day when something needs a whiteboard.
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. This is home — the one city where I am local, not visiting.
Noida is inside my daily travel radius — I am based in Noida, so I can be on site for a kickoff, an architecture session, or a release review and be back the same day. Most engagements settle into a hybrid rhythm: in person when a whiteboard helps, remote for the build itself.
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. Noida is inside my daily travel radius — I am based in Noida, so I can be on site for a kickoff, an architecture session, or a release review and be back the same day. Most engagements settle into a hybrid rhythm: in person when a whiteboard helps, remote for the build itself.
Noida projects usually start with an in-person kickoff and continue hybrid, because I am based here and can be on site the same day when something needs a whiteboard. Concretely, that tends to mean content platforms and publishing workflows that survive a traffic spike, internal platforms and client-facing portals that a services team can hand over cleanly, and multi-tenant architecture, billing, and role-based access that holds up as the customer list grows. 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.
You do, outright. For Noida 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 noida projects usually start with an in-person kickoff and continue hybrid, because I am based here and can be on site the same day when something needs a whiteboard. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Noida client is usually about cutting scope to the part that proves the idea.
Yes. My default is TypeScript throughout — React and Next.js on the front, Node.js and NestJS services, PostgreSQL and Redis, Docker and AWS — but if your Noida team already runs something else, I work in it rather than arguing for a rewrite. Recommending a migration only makes sense when the current setup is genuinely the problem.
The reasoning behind how I build — 200+ articles on architecture, backend, and performance.