Hire a Senior Full Stack Engineer in Lakshadweep

Yes. Remote-first from Noida, on IST, with an on-site visit to Lakshadweep 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 is not a preference here, it is the only design that works. Everything else follows from that constraint. Concretely, that tends to mean accessible public-facing platforms with audit trails and documented handover, booking engines, availability logic, and seasonal pricing, and catch logging and cold-chain tracking on very limited bandwidth. 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.

A focused first version is typically 6–12 weeks depending on scope. Given that offline-first is not a preference here, it is the only design that works. Everything else follows from that constraint. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Lakshadweep 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 Lakshadweep 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.

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