Delivery Manager – Airline Operations Platform

Delivery Manager – Airline Operations Platform

We are easyJet – a FTSE-250 listed, £multi-billion low-cost airline that serves tens of millions of customers every single year. If you’re reading this, you have probably already been an easyJet customer, and you’ll know that there is no more iconic (or Orange!) travel brand in Europe.

We fly more than 1,207 routes, connecting 38 countries across Europe, and employ more than 18,000 colleagues. We’re on a mission to make low-cost travel easy – and whatever your role here, you’ll connect millions of people to what they love using Europe’s best airline network, great value fares, and friendly service.

What makes us easyJet? Our Promise Behaviours – we are Safe, Bold, Welcoming and Challenging. Four Behaviours. One Spirit. One easyJet.

ROLE OVERVIEW

TEAM

· At easyJet, we are transforming Airline Operations through modern product-led technology, operational excellence, automation, data and AI-enabled capabilities.

· The Airline Operations Platform is the single point of contact for the applications and source data availability assigned to the Platform, enabling four operational missions across four business critical applications. It owns the crew, flight planning, network control and engineering systems that keep the network flying, AIMS, TOPS, LIDO and AMOS.

· As Delivery Manager, you will operate the delivery system between the Platform and the missions. You will coordinate the platform squads against mission sprints, own delivery cadence, and manage vendor commitments as dependencies rather than assumptions — so what Platform commits to a mission is deliverable, visible and honoured.

· This is a delivery role in a live operational environment. Much of the work involves interdependent third-party systems, so your value lies in sequencing, dependency management and honest, early communication when a commitment is at risk.

· Working closely with Mission Product Managers, Platform Leads, Technical Specialists, Architects, Service Support and Supplier Management, you will make delivery predictable, keep the backlog credible, and ensure change reaches the operation safely and with the right cover in place.

· This role reports to the Platform Lead – Demand & Capability and is one of two Delivery Managers, with mission and portfolio coverage allocated between them. The role has no direct reports and leads through influence, coordinating squad members who sit within the Platform capability chapters.

JOB PURPOSE

· Coordinate the platform squads against mission sprints, owning delivery cadence across the allocated portfolio.

· Own the commitment position with the missions: what Platform has committed to each sprint, what has changed, and what is at risk.

· Track and manage vendor commitments as external dependencies, surfacing the vendor critical path before it becomes a delay.

· Own dependency, risk and issue management across products, missions, suppliers and enterprise platforms.

· Ensure work entering a sprint is sized, understood and free of unresolved dependencies.

· Support the demand rhythm through triage, sizing and the reuse-first challenge, keeping the single backlog credible and current.

· Ensure change reaches the operation safely, with readiness, supportability, documentation and cover agreed before release.

· Define and report delivery metrics that give visibility of flow, predictability and delivery health.

· Champion Product and Platform ways of working, treating the missions as customers of the Platform.

· Provide clear, early communication on progress, risk and change to mission and Platform leadership.

· Drive continuous improvement in how the Platform delivers, removing repeated impediments rather than working around them.

JOB ACCOUNTABILITIES

Delivery Cadence & Squad Coordination

· Coordinate platform squads across the capability chapters — Data Availability, API & Integration; Proactive App Management; Automation — against mission sprint commitments.

· Own the delivery cadence: backlog refinement, sprint planning, stand-ups, reviews and release planning, run consistently rather than when there is time.

· Maintain one backlog and one plan for the allocated portfolio, so squad members working across several missions have a single view of priority.

· Sequence work so that run and support, mission demand and improvement work coexist rather than compete, protecting the agreed capacity allocation.

· Keep the plan honest: reflect actual progress and capacity, not the plan as originally committed.

Mission Interface & Commitment Management

· Run the per-sprint interface sync with the Mission Product Managers for the allocated missions: what Platform commits to that sprint, and what has changed since the last one.

· Own the commitment record, so a mission always knows what it is getting, when, and what it depends on.

· Surface changes to commitment early, with the reason and the option set, rather than reporting a miss after the fact.

· Ensure missions are not building platform capability that is already coming, by making the Platform roadmap and backlog visible to them.

· Escalate to the Platform Lead – Demand & Capability where commitments and capacity diverge, with the trade-off articulated.

Demand Support, Sizing & Dependencies

· Support daily triage and the weekly demand review, contributing sizing, dependency mapping and the reuse-first challenge.

· Ensure nothing enters a sprint unsized, without dependencies mapped, or without the vendor critical path named in the commitment.

· Own dependency management across products, missions, suppliers, enterprise data, architecture and I&O, coordinating resolution rather than reporting the blockage.

· Maintain and work the risk and issue log for the allocated portfolio, with mitigations owned, monitored and escalated where required.

· Identify where the same dependency or impediment recurs, and work with the Platform Leads and Architects to remove the cause.

Vendor & Supplier Delivery

· Track vendor commitments — releases, fixes, roadmap items, API and integration changes — as external dependencies with