Cloud Transit Routing Recovery Leader

The mandate

A transit-policy change propagated through shared cloud route tables and inspection appliances, drawing airport partner traffic into a constrained path before health automation withdrew additional routes. Ground-handling and crew services became unreachable from two airports while public endpoints remained healthy. The cloud-network executive was dismissed after review found overlapping route authority, undocumented partner prefixes and no safe regional isolation procedure.

The interim must begin in Dubai within fifteen days and serve for twelve months, with a possible two-month extension only if an airport test window moves. Recruitment for permanent cloud-network leadership starts after one region and two airport partners operate the new route authority model, expected in month six. The successor will overlap for six weeks and command the final partner-isolation drill.

Handover requires every route source, propagation path, inspection dependency and partner prefix to have accountable ownership; transit changes to pass simulation and bounded rollout; airport services to retain tested regional and inspection bypass according to policy; two compounded network exercises to succeed; and the permanent leader to accept topology, exception, provider and operational-risk registers.

The interim may freeze network changes, withdraw propagated routes, isolate transit domains, set emergency path priority, redirect internal teams and approve up to AED 85 million within the recovery programme. New carrier contracts, permanent hiring, airport commercial commitments, security-policy exceptions and decisions above AED 18 million require committee approval. The seat cannot bypass mandatory inspection or aviation safety controls.

Airport operational-process redesign, application feature work, corporate campus networking and wholesale cloud-provider migration are explicitly out of scope. The assignment covers cloud transit, route propagation, inspection service chaining, airport partner connectivity, failure isolation, outside-in service evidence and the organisation that commands these dependencies.

Why this seat is open

The outage demonstrated that cloud regions described as independent shared routing and inspection decisions that could propagate globally. Executive dismissal left network, security and airport teams with competing claims to route authority. A temporary leader must create bounded transit domains, test them with partners and induct permanent command without interrupting active airport operations.

What you will own

• Reconstruct route advertisements, tables, propagation, inspection paths, health inputs, withdrawals and service failures across clouds and airports.
• Assign authoritative ownership for prefixes, route intent, propagation domains, service chains, partner changes and emergency overrides.
• Decide segmentation, summarisation, preference, convergence, inspection bypass and fail-closed behaviour by aviation-service consequence.
• Establish simulation, peer review, canary, maximum-prefix, blast-radius, rollback and external reachability gates for network change.
• Reconcile documented topology with effective paths using flow, route, appliance, provider and partner evidence.
• Command drills involving route leak, inspection saturation, region isolation, partner misannouncement and control-system loss.
• Transfer maps, route policy, partner obligations, exceptions, exercise results and incident authority through successor-led operations.

Candidate qualifications

• Held executive authority for cloud transit and partner connectivity supporting aviation, logistics or similarly time-critical operations.
• Recovered a route-propagation or service-chaining incident spanning cloud regions, inspection systems and external networks.
• Designed bounded routing domains and emergency paths that did not silently defeat mandatory security controls.
• Built change gates using route simulation, external reachability, canary and maximum-blast-radius evidence.
• Negotiated operational ownership with airport, carrier, cloud and security providers during shared-path failure.
• Handed regional network command to a permanent leader through witnessed partner and isolation exercises.

Non-negotiables

• Can start on site in Dubai within fifteen days and travel monthly to airport or regional network-control locations.
• Will accept exclusive executive duty and continuous escalation availability for airport connectivity incidents.
• Brings production cloud-transit and partner-routing evidence; enterprise WAN or firewall governance alone is insufficient.
• Must disclose relationships with cloud, carrier, airport, inspection and managed-network providers.

1. 49 words maximum. State your earliest Dubai start and the widest cloud-route propagation incident you personally commanded.
2. 49 words maximum. Describe a shared inspection path that made two apparently separate regions fail together.
3. 49 words maximum. Which control would stop a valid local route change from becoming a global airport outage?