Python Backend Developer | Travel Tech (Amadeus NDC/GDS & Traveltek) | Microservices

We are building an enterprise-grade travel orchestration platform. We are moving away from legacy travel constraints and building a modern abstraction layer that normalises multi-GDS/NDC and supplier payloads into clean, actionable data. We don't just automate everything blindly; we are engineering a "Decision Layer" that allows human experts to pause, review, and validate complex bookings mid-flow before final ticketing. We are looking for a Senior Python Developer who deeply understands microservices, cloud infrastructure, and the specific intricacies of travel APIs, specifically Amadeus and Traveltek, to help build out this core architecture. What You Will Do: Multi-Node Normalization: Build and scale Python microservices that parse and normalize payloads from Amadeus (REST/JSON, NDC, and Cryptic SOAP/XML) and Traveltek, ensuring our core system remains supplier-agnostic. Build the Decision Layer: Engineer stateful backend mechanisms that support asynchronous, pause-and-resume booking states. Complex Orchestration: Handle stateful PNR sessions, automated ticket exchanges, and strict GDS queue logic beyond simple search/book REST flows. Data Mapping: Extract dense XML/JSON payloads, especially rich NDC ancillary data and deliver optimised, structured JSON to our frontend. Cloud & CI/CD: Deploy, manage, and scale these microservices on Azure, maintaining strict version control and CI/CD pipelines via GitHub. Must-Have Experience: Python & Microservices: Deep expertise in designing, building, and deploying modular backend systems in Python. Amadeus GDS & NDC: Hands-on experience with Amadeus Enterprise APIs and integrating New Distribution Capability (NDC) content. You need to understand the jump from stateless Self-Service API calls to managing actual GDS queue logic. Traveltek: Experience integrating Traveltek APIs (flights, cruise, or tour packaging) and mapping their specific schemas. Azure & GitHub: Strong operational experience deploying and managing services within Azure, paired with a solid GitHub-based development workflow. Travel Architecture: A strong track record of abstracting disparate third-party travel suppliers into a unified internal data model. Nice-to-Haves: Interest in decentralised identity (DID) and W3C standards within the aviation space. How to Apply: If you understand the pain points of parsing raw GDS terminal responses into structured JSON, we want to talk to you. At the top of your proposal, please briefly describe a specific challenge you faced when normalising a difficult travel payload (preferably Amadeus or Traveltek) and how you architected the solution in Azure/Python. Generic, copy-pasted proposals will be declined.