Skip to content

Hire a Senior Full Stack Engineer in Meerut

Aman Kumar Singh — Team Lead & Senior Software Engineer. React, Next.js, Node.js, NestJS, PostgreSQL, Redis, and AWS.

Meerut’s sports-goods and publishing industries are digitising distribution, which in practice means order management and dealer portals. What that means in practice: dealer and distributor portals with role-based access are the pattern I see most from Meerut, and permissions are where they usually get complicated.

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. Under two hours from Noida.

Meerut 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.

What I build for Meerut clients

  • Dealer portals, order management, and export documentation.
  • Catalogue, rights, and distribution systems for a title list.
  • Production tracking, dispatch, and shop-floor dashboards that are readable at a glance.

The stack I work in

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

Start a project in Meerut

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.

Frequently asked questions

Do you take on projects from clients in Meerut?

Yes. Meerut 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.

What kind of software do Meerut businesses usually need?

Dealer and distributor portals with role-based access are the pattern I see most from Meerut, and permissions are where they usually get complicated. Concretely, that tends to mean dealer portals, order management, and export documentation, catalogue, rights, and distribution systems for a title list, 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.

How long does a first version take for a Meerut project?

A focused first version is typically 6–12 weeks depending on scope. Given that dealer and distributor portals with role-based access are the pattern I see most from Meerut, and permissions are where they usually get complicated. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Meerut client is usually about cutting scope to the part that proves the idea.

Can you work with our existing stack in Meerut?

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 Meerut 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.

What does a Meerut project typically cost?

It depends on scope, so I quote per project rather than publishing a rate card. Before any money changes hands you get a fixed scope and timeline for phase one — you should know what you are buying before you agree to it. Email aman97aman@gmail.com describing what you want built in Meerut and I will come back with a scope and an estimate.

Read the engineering writing

The reasoning behind how I build — 200+ articles on architecture, backend, and performance.