Hire a Senior Full Stack Engineer in Manipur

Yes. Remote-first from Noida, on IST, with an on-site visit to Manipur when a kickoff or release genuinely benefits from being in the room. Progress stays visible through a shared board and a weekly demo rather than status emails.

Offline-first design and multilingual support are requirements rather than enhancements, and they change the data model, not just the UI. Concretely, that tends to mean catalogue, order, and weaver-payment tracking, patient records, appointments, and access control that is genuinely strict, and accessible public-facing platforms with audit trails and documented handover. 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 Manipur 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 offline-first design and multilingual support are requirements rather than enhancements, and they change the data model, not just the UI. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Manipur 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 Manipur 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.