Senior Node.js Developer: Zenoti Booking API Integration

We are a premium facial spa company with 10 locations across New York, DC, and Miami, expanding to 19. We are migrating our booking platform and need a strong integration developer to build the booking flow against the Zenoti API, starting this week. WHAT YOU WOULD BUILD Our website already has a booking experience our guests know. We are replacing what sits behind it. Your job is the integration layer, not the design: - Service and location catalog reads - Availability search across multiple locations - Appointment creation, edit, and cancellation - Guest lookup and creation - Checkout, including the payment step - A thin middleware layer so the front end is not calling the vendor API directly There is no design work. The front end exists. You are wiring it to a new backend. MUST HAVE - Deep REST API integration experience, ideally with a booking, scheduling, or appointment platform (Zenoti, Boulevard, Mindbody, Booker, Vagaro, or similar) - Strong Node.js and modern JavaScript - Comfortable working alongside a WordPress front end - Experience integrating a third-party payment step and a working understanding of what different approaches do to PCI scope - You have shipped something with a real, immovable launch date and can talk about what you cut to make it NICE TO HAVE - Direct Zenoti API experience - Multi-location or franchise systems - Experience designing against hard API rate limits - Data migration or reconciliation work between two platforms TIMELINE AND COMMITMENT - Start: immediately - Launch: September 1, hard date - 30 to 40 hours per week through launch, with availability for a lighter support period after - You will work alongside our existing development partner. Clear ownership boundaries will be set on day one. Ego-free collaboration is a requirement, not a preference. HOW TO APPLY Generic proposals will not be read. Answer these four in your response: 1. Describe a booking or scheduling platform integration you shipped. Which platform, what did availability lookup actually look like, and what broke in production that you did not expect? 2. When integrating a third-party payment step, how do you decide between handing off to the vendor's hosted payment page versus collecting the card on your own front end? What does each choice change about PCI scope? 3. Hypothetical: you have a hard API rate limit of 60 calls per minute enforced across your entire organization, shared with other integrations. How do you design a multi-location availability search that stays under it and still feels instant to a guest? 4. Send a short Loom or a link walking through a booking flow you built. Live is better than a repo. Also tell us your earliest start date and your real weekly availability between now and September 1. TERMS - NDA before any system access - Staging access only until the first milestone is delivered and reviewed - Work for hire, all IP assigned - No subcontracting or offshoring of the work without written approval - Hourly with a weekly cap, agreed in advance