Software Lead

Full-Stack Developer — PureLuxe Studio

KFT Corporation / PureLuxe International — Mumbai

About the role

PureLuxe International is a luxury travel agency building PureLuxe Studio, an internal operations platform that replaces email/WhatsApp/spreadsheet sprawl with a single source of truth for client history, bookings, and rates. The core build (auth, review-queue pipeline, bookings/clients/trips UI, family management) is in place. We're now hiring a developer to take ownership of the remaining pipeline work and lead the next phases: Offline Rates, Sabre GDS integration, task management, and document handling.

This is a hands-on IC role with real ownership — you'll be working directly with the founder on architecture decisions, not executing a fully-specced backlog.

Mid-term vision: PureLuxe Studio starts as an internal ops platform, but the goal is to evolve it into a client-facing AI-powered OTA (online travel agency) — with WhatsApp as the primary client interface, targeting the premium mass market with the kind of rate intelligence and personalization currently locked inside our internal tools. The person who builds the internal foundation well is the natural person to lead that next phase. This isn't a role where you build one thing and hand it off — the internal system is the foundation for the product.

What you'll work on

Debug and stabilize the email extraction pipeline (Anthropic Batch API–based), including edge cases where extraction succeeds but booking creation silently fails
Build the Offline Rates module from a completed spec — destination- and property-first auto-trigger logic for suppliers outside standard GDS flow
Lead Sabre GDS integration — polling-based PNR sync via QueueAccessRQ
Build the task management system — a 33-task, 8-phase client journey workflow with Gmail-native delivery (draft generation, completion tracking via Sent folder)
Extend the Documents tab — passport/travel document upload with Claude Vision extraction
Maintain schema discipline as the system grows: migrations, RLS, generated columns, dedup constraints

Looking ahead (mid-term):

Help design and eventually build the client-facing layer — a WhatsApp-native "Rate Assistant" that surfaces live rate intelligence directly to clients, positioned against traditional OTAs
Extend the extraction/review-queue patterns you'll have built internally to a context where the "client" reviewing model output is an actual paying customer, not an internal team member — meaning trust, latency, and failure-handling all get much less forgiving
Think through what changes when users go from ~15 trusted internal staff to an open client base: auth for external users, rate limiting, abuse prevention, and (eventually) payment handling

Stack

Next.js (App Router) · TypeScript · Supabase (Postgres + Storage) · iron-session · Anthropic Batch API (Claude Sonnet/Haiku) · Windows/VS Code + Claude Code workflow

What we're looking for

Must-have

Strong TypeScript + Next.js experience, comfortable with App Router, server components, API routes
Real Postgres fluency — not just ORM-level. You should be at home with RLS policies, migrations, generated columns, and unique constraints, and instinctively think about race conditions in concurrent writes
Experience building or maintaining LLM-based data extraction pipelines — and specifically, experience designing for imperfect model output (confidence gating, human review queues), not just calling an API and trusting the result
Comfort working inside an existing, opinionated codebase rather than rewriting it to taste

Strong plus

GDS or travel-industry API experience (Sabre, Amadeus, or similar)
Experience with AI-assisted coding workflows (Claude Code or equivalent) — reviewing and steering AI-generated code, not just accepting or rejecting wholesale
Comfort with ambiguous, evolving business rules (this is a real-world operations system, not a green-field app with a fixed spec)
Experience with conversational/messaging-based product interfaces (WhatsApp Business API, chatbots, or similar) — the eventual client-facing product is chat-first, not a traditional web app
Any exposure to consumer-facing product concerns: auth for external users, rate limiting, abuse prevention, or payments — even if not travel-specific

Not required but nice to have

Gmail API / Google Workspace integration experience
Prior work on booking, CRM, or client-record systems with dedup/merge logic

How we work

Migrations are a hard gate — schema changes are confirmed applied before any dependent logic is wired
We patch scoped, working code rather than rewriting; we start clean only for genuinely green-field features
Dry-run before live for any import/dedup/migration script
Every Supabase write checks the { error } response, not just JS exceptions
Ship a narrow working thing first, then expand — we don't chase completeness in the abstract

To apply

Send your resume/GitHub along with a short note on a time you had to fix a data consistency or race-condition bug — what broke, how you found it, how you fixed it. We'd rather see that than a cover letter