Software Engineer, Backend Booking Platform & APIs

Staff Software Engineer, Backend Booking Platform & APIs

New York, NY

Resort Pass is redefining what it means to be a hotel guest. We give people daytime access to pools, beaches, spas, cabanas, and other hotel experiences without an overnight stay.

We have proven the demand. Now we are building the booking and distribution platform that can bring hotel experiences to many more guests, categories, and channels.

A day pass is sold by capacity. A cabana is reserved as a unit. A massage needs a time slot and available resources. Each has different rules for inventory, pricing, and cancellation. Those rules must remain correct wherever a booking begins.

We are hiring a Staff Engineer to lead the evolution of our booking platform and external API. You will help distribution partners and authorized AI agents book the same inventory as Resort Pass guests.

You will build on a production Rails Open Search and Postgres system while shaping important decisions about its future. What you build will determine how quickly we can launch hotel and spa partners and new experiences. You will see your architectural choices through to real bookings and help other engineers build on them.

Your ownership and team

Reporting to the Head of Engineering, you will lead architecture and the technical roadmap for the booking domain and external API. This is a hands-on individual contributor role: you will write core production code and guide implementation with other backend engineers.

Our Distinguished Engineer will be your partner on architectural decisions that affect the wider platform. You will work directly with the Head of Engineering and engineering leads on priorities, sequencing, and capacity.

With Product, Partnerships, and hotel operations, you will assess partner requirements and plan launches. Your judgment will help determine what belongs in the shared platform, where a simpler integration is sufficient, and what to defer.

• A partner times out after requesting the last available cabana. How can it determine whether the booking succeeded, retry safely, and give the guest a clear answer?
• A massage needs a time slot, provider, or room, while a day pass uses capacity. Which concepts should they share, and where should their booking rules differ?

• Evolve clear models and boundaries for products, pricing, availability, holds, and reservations. Represent category differences explicitly and use real requirements to guide what becomes shared.
• Build and launch a versioned external API for pricing, availability, holds, booking, changes, and cancellations. Establish access controls, documentation, and a practical path from partner testing to production.
• Make booking operations reliable through retries, timeouts, and partial failures. Design idempotency, concurrency controls, webhooks, and reconciliation to prevent duplicate bookings and inventory errors.
• Establish reusable patterns for supply, property management, and point-of-sale integrations. Make data ownership and failure handling clear so engineers can add connectors and diagnose problems consistently.
• Lead incremental migrations in our existing system. Set reliability and latency targets, test important failure scenarios, and ensure the team can observe, operate, and safely roll back changes.
• Help engineers take ownership of larger problems through focused design reviews, pairing, and mentoring. Explain tradeoffs, resolve decisions across team boundaries, and follow the work through production.

The first priority is to prove a dependable…