Skip to content

Hire a Senior Full Stack Engineer in Kolkata

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

Also searched as Calcutta.

If you are looking to hire a full stack developer in Kolkata, here is the context I work from. Kolkata’s Sector V and New Town hold a large IT-services base, with fintech, education, and media businesses driving most of the product work. Kolkata engagements often involve modernising a working-but-aging system, which is migration planning as much as coding — and the planning is the risky part.

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. East India’s technology centre.

I work with Kolkata clients remote-first from Noida. IST means no handover lag, and I keep a shared board plus a weekly demo so distance never turns into silence — which is the real failure mode of remote work, not the distance itself.

What I build for Kolkata clients

  • Content platforms and publishing workflows that survive a traffic spike.
  • Internal platforms and client-facing portals that a services team can hand over cleanly.
  • Payment flows, ledgers, and reconciliation that has to balance to the rupee.

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

More in West Bengal

Start a project in Kolkata

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 Kolkata?

Yes. I work with Kolkata clients remote-first from Noida. IST means no handover lag, and I keep a shared board plus a weekly demo so distance never turns into silence — which is the real failure mode of remote work, not the distance itself.

What kind of software do Kolkata businesses usually need?

Kolkata engagements often involve modernising a working-but-aging system, which is migration planning as much as coding — and the planning is the risky part. 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 payment flows, ledgers, and reconciliation that has to balance to the rupee. 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.

What does a Kolkata 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 Kolkata and I will come back with a scope and an estimate.

Can you join an existing Kolkata team rather than build from scratch?

Yes, and with an established Kolkata 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.

Who owns the code once a Kolkata project is delivered?

You do, outright. For Kolkata 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.

Read the engineering writing

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