Skip to content
ResortPass

Senior Software Engineer, Backend — Booking Platform & APIs

New York, NY; New YorkUnited States
Senior · Engineering
POSTED 11 AUGVERIFIED 1D AGO
Apply Ask
Role
89 days opentrue age
Posted 11 Aug
Payin text
$190k–210kposted
▼ −1% vs market median $203k
$185k$215k
Market p25–p75
$185k–$215k
New York · n=87 · 365d to 6 Nov
CompanyResortPass →
5open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
2,870open · Senior Backend
Opened · 7d
+1274% of open
All backend
8,405open
All tracked boards · live 9 Nov · n=2,870
Ruby/RailsPostgreSQLElasticsearch

About ResortPass

ResortPass 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 work with more than 2,700 hotel partners across 30 countries. We have served more than 7 million guests and generated hundreds of millions of dollars for our hotel partners. Marriott has signed a global agreement with ResortPass, and Hilton has expanded its partnership with us.

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.

Why this role matters

Most travel platforms are built around overnight rooms. ResortPass is building the platform for everything else a hotel can offer.

A day pass is sold by capacity. A cabana is reserved as a unit. A massage needs a time slot, provider, or room. Events have tickets. Food and beverage may be a product, an add-on, or part of a bundle. Each category has different rules for pricing, inventory, fulfillment, and cancellation.

We need one clear booking domain that supports these differences without creating a separate system for every category. That same inventory must be available through ResortPass, hotel systems, distribution partners, and authorized booking agents.

We are hiring a Senior Software Engineer to lead the technical work and be the primary hands-on builder for the ResortPass API. In your first year, multiple distribution partners and an authorized AI agent should complete real bookings through the same versioned API.

You will evolve a production Rails and Postgres booking system used by millions of guests. The hard work is keeping prices and inventory correct, preventing overselling, surviving retries and partial failures, and reconciling systems when they disagree.

Your ownership and team

You will own the API’s day-to-day technical roadmap and design decisions. In this hands-on individual contributor role, you will write production code, lead focused designs, guide migrations, and operate what you build. You will partner with our Staff Engineer on foundational domain and architecture choices.

You will be the primary builder, but you will not work alone. Other backend engineers will contribute and build supply, PMS, and POS connectors using the patterns you establish. Product, Partnerships, and hotel operations will work with you from requirements through production launch.

This is one of our highest-impact technical bets. What you build will determine how quickly ResortPass can enter new booking channels and categories.

This role works from our NYC headquarters four days per week. The base salary range is $190,000–$210,000, plus equity, based on experience.

What you’ll do

  • Build and launch the external ResortPass API. Define stable, versioned contracts for live pricing, availability, holds, booking creation, changes, and cancellations.
  • Make booking operations safe under real failures. Design idempotency, recovery, webhooks, and reconciliation for retries, timeouts, duplicates, and partial success.
  • Evolve the core booking domain. Create clear models and invariants for products, schedules, prices, inventory, holds, carts, and bookings.
  • Make the platform extensible. Prove that a new category such as events or food and beverage can use the shared booking model instead of requiring a separate system.
  • Own the architecture for supply, PMS, and POS integrations. Create reusable connector patterns so other engineers can add partners without reinventing failure handling and reconciliation.
  • Define the data contracts that keep inventory discoverable through OpenSearch. Search is supporting technology for this role, not its primary ownership area.
  • Operate what you build. Set reliability and latency targets, and add the tests, metrics, dashboards, alerts, tracing, and runbooks needed for a critical booking path.
  • Turn partner needs into durable platform capabilities, explain tradeoffs clearly, and raise the engineering bar through practical reviews and mentoring.
Source · ResortPassFirst seen 7 NovOriginal ↗