Software Architect, Air Supply and Search (GDS - Sabre first)

Software Architect for Air Supply Domain

We are hiring a hands-on Software Architect to fully own the Air Supply domain end-to-end. You will define the normalized supply layer over Sabre, build production-grade flows from search to ticketing, and lead a small backend team (initially 2 to 3 engineers).

You will establish clear integration contracts with adjacent platform domains, including:

• Economic Core
• Risk, Policy, and Control (future integration surface)
• Order and Lifecycle orchestration

What You Will Own

1) Search normalization and pricing consistency

• Design a deterministic normalized model over Sabre shopping and pricing responses
• Define representations for itineraries, segments, fare components, and fare construction
• Normalize pricing breakdowns (base fare, taxes, surcharges)
• Support branded fares, restrictions, and ticketing time limits (TTL)
• Ensure pricing consistency across search, reprice, booking creation, and ticketing

2) Lifecycle integration surface

• Define explicit lifecycle transitions and state contracts
• Design idempotent flows and reconciliation strategies
• Prevent price drift and economic mismatches
• Create clear contracts with the Economic Core
• Keep the lifecycle surface policy ready without embedding policy logic

3) Production-grade Sabre integration

• Own shopping, pricing, PNR creation, and ticketing integration
• Define retry and reconciliation strategies
• Handle partial failures and session constraints
• Ensure stability under real production traffic

4) Technical leadership (hands-on)

• Lead architecture and execution for this domain in a lean team
• Write critical parts of core logic and prototypes yourself
• Review designs and code, enforce integration contracts
• Prevent domain leakage across platform domains
• Drive execution from design to production in a startup environment

Required Experience (Must Have)

• Deep hands-on Sabre experience in production
• Ownership of air shopping, pricing, booking, and ticketing flows
• Strong knowledge of:
  • Fare construction
  • ATPCO fare structures
  • Taxes and surcharges breakdown
  • Repricing logic
  • Ticketing time limits (TTL)
• Experience designing normalized domain models over GDS data
• Strong backend engineering background (Python, Java, Kotlin, or similar)
• Experience leading engineers or owning a technical domain

Nice to Have

• Experience in OTA or airline tech environments
• Lifecycle-driven system design experience
• Integration-heavy platform experience
• Experience scaling teams within a domain

What This Role Is (And Is Not)

• Long-term domain ownership and hands-on architecture
• Not a generic backend engineer role
• Not ticketing support
• Not a short-term integration contractor

Success Criteria

Within 3 months

• Normalized search model defined and adopted
• Integration contracts with the Economic Core formalized
• Deterministic lifecycle surface established

Within 6 months

• Stable production flow from search to booking to ticketing
• No economic inconsistencies between Supply and Economic Core
• Backend team operating independently under a defined architecture

Why This Role Matters

This layer defines how Radar interacts with airlines and distribution systems. Decisions here affect economics, risk, policy enforcement, SLA management, and enterprise scalability.

You will architect and build the supply foundation of a multi-tenant travel platform while remaining hands-on in critical technical decisions and early implementations.

This is a high-impact, high-ownership position for someone who wants to define how airline distribution works inside a modern SaaS system.