The role

We're hiring a full stack engineer to ship features across that platform. A membership change, a booking flow, an agent tool: you shape the API contract, implement the service and data work, and ship the React UI members and agents actually use. Both halves need to hold up in review — sound data and API choices, and UI that feels finished.

You're not here to paint tickets: you're here to improve the product. Concierge operations, memberships, bookings, and billing are real business logic with real edge cases. You'll be expected to push back on requirements, notice when a model or a flow is wrong, and care about what members and agents hit in production. Luxury detail matters on both sides of the stack: a clumsy empty state and a query that falls over under a bigger tenant are both broken experiences.

We work AI-native. Coding agents are part of how we build, prototype, and refactor. You still own taste, judgment, and review. Speed without judgment isn't the bar.

What will you do?

• Ship TypeScript features end to end: a vertical API slice on our Hono service — OpenAPI-first contracts, generated types, integration tests — and the React UI that consumes it
• Design the API contract for the features you own, in conversation with web, iOS, Android, and partner clients, including versioning and backwards compatibility when a shipped mobile app depends on it
• Model and query the data those features need in Postgres, with sound transactions, indexes, and consistency boundaries, inside the patterns the platform already uses
• Build the UI in Concierge, LMT, and shared web libraries: forms, multi-step flows, data-heavy screens, loading and error states, responsiveness, and accessibility that meets the existing review bar
• Follow the frontend architecture, design system, and design-token theming that other people own. Propose UX improvements with design and product; implement them in the patterns already there
• Wire integrations, webhooks, and background work when the feature needs them, following existing retry, idempotency, and observability patterns rather than inventing new ones
• Hand platform-scale problems — tenancy isolation, long-running workflows, query performance at 10x, a new integration's failure modes — to the people who own them, with a clear write-up of what you found
• Use coding agents as a default accelerator with clear specs, sharp review, and solid tests
• Communicate clearly for a remote team: design notes, PR descriptions, async updates