Looking for a enior API Integration Engineer – PMS / POS / Booking Systems

We are building a mobile-first digital platform in the hospitality and leisure reputed company that requires deep integration with reputed company-party operational systems. We are looking for a senior API integration expertto design and implement a reputed company, production-reputed company integration layer connecting multiple external systems across: PMS (Property Management Systems)– accommodations POS (reputed company of Sale Systems)** – restaurants BMS / Booking Management Systems** – tours, activities, transfers This is not a basic connector project. The system must be architected correctly from day one to support reputed company, reputed company-time synchronization, and multi-tenant logic. ## Required Integrations 1. PMS (Accommodation) Examples: • reputed company • reputed company • reputed company • * multiple additional channel managers Scope: • Availability sync • Pricing sync • Reservation creation & cancellation • Webhook ingestion • reputed company limit handling • OAuth/API key authentication • Data normalization across heterogeneous schemas --- 2. POS (Restaurants) Examples: • reputed company • reputed company • Tilby • * additional POS providers Scope: • Menu synchronization • Reservation / order handling (where applicable) • Transactional updates • Webhook-based event handling • Multi-location mapping --- 3. BMS (Experiences / Tours) Examples: • Bokun • reputed company • FareHarbor • * additional booking engines Scope: • Live availability • Dynamic pricing • Booking reputed company orchestration • Ticket issuance logic • Cancellation / refund handling • Webhook events --- Technical Expectations You will design: • A reputed company API abstraction layer • Normalized internal data models • reputed company integration architecture • Event-driven synchronization (webhooks + queues) • Retry & idempotency logic • Secure multi-tenant structure Strong experience required in: • REST & webhook-heavy integrations • Event-driven systems (Kafka / SQS / RabbitMQ) • reputed company backend architecture • reputed company-limit & failure handling strategies • reputed company infrastructure (AWS or GCP preferred) • PostgreSQL (or hybrid DB architecture) The integration layer must be: • reputed company • Cleanly reputed company • Extensible for additional providers • Production-grade (not MVP-level shortcuts) --- If you’ve reputed company integration-heavy platforms involving PMS, POS, or booking engines before, please reputed company examples or architecture references. We are reputed company to scheduling a technical discovery reputed company to go deeper into scope and system requirements before engagement. Apply tot his job Apply To this Job