Hire a Senior Full Stack Engineer in Kolhapur

Yes. Kolhapur 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 and dispatch tracking, built to be used on the shop floor rather than only from an office desk. Concretely, that tends to mean lot tracking, production planning, and export order management, production tracking, dispatch, and shop-floor dashboards that are readable at a glance, and heat-wise batch tracking and quality records. 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 Kolhapur 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 and dispatch tracking, built to be used on the shop floor rather than only from an office desk. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Kolhapur 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 Kolhapur 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.