Originally Posted by epiphani

There might be some interesting technical challenges, but on the scale of "tech problems", the entire thing rates pretty low.

The leadership and culture issues are also probably pretty major - which is why, like cc said, you'd need to come in at the top.

The biggest problem, in my mind, is the existing technical debt and existing systems that work "well enough". All considered, AC's IT actually works quite well at its core business - ticketing, PNR, checking in, flight management, etc. The problem is that it's all been built over time since the 80s or even 70s, and there are huge swaths of stuff that reflected the best practices (by probably mid-level developers) of the time.

How would I handle that? Toss out the entire stack, and rewrite from scratch using modern distributed backends and tools - in parallel to the existing system, feeding from the existing system, running quiet and hidden until it is stable and correct enough that it can be slowly phased into production as a full replacement.

Multi-year R&D cost on top of the existing system with no tangible benefits for probably the first 18-24 months. But, when it's done, massive reduction in cost and massive increase in reliability, performance, and maintainability. Also massive improvement in analytical tooling, business intelligence, marketing, preventative maintenance.. probably improvements in OTP and other rather visible stuff.