Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
Wego seeks an experienced Product Manager to own the Flights problem space, aligning strategy with marketplace growth and commercial objectives. You will shape roadmaps, define sequencing, and lead discovery, validation, delivery, experiments, launches, and optimization across engineering, design, and finance.
The role requires 5+ years in product management with direct flight tickets/OTA ownership; deep understanding of flight distribution mechanics, refunds, fees, and supplier reconciliation;
Wego is the leading travel app and the largest online travel marketplace in the Middle East and North Africa. Our mission is to make travel better by helping millions of people discover, compare, and book flights, hotels, and travel experiences with confidence.
Wego is the leading travel app and the largest online travel marketplace in the Middle East and North Africa. Our mission is to make travel better by helping millions of people discover, compare, and book flights, hotels, and travel experiences with confidence.
Founded in 2005, Wego has grown from a metasearch engine into a full travel platform — combining powerful search with our own OTA products, where we don't just point travellers at a fare, we sell it, ticket it, and stand behind it when plans change. Millions of travellers use Wego every month across hundreds of airlines, hotels, and travel providers.
That shift — from sending traffic to owning the transaction — is what this role exists for.
Flights OTA experience is a hard requirement. Without it, please don't apply. We will not shortlist strong generalist PMs, strong marketplace PMs, or PMs whose travel experience is limited to metasearch, aggregation, or affiliate funnels. Not because those people aren't good — because this domain cannot be learned on the job at the speed we need, and we've stopped pretending otherwise.
These are live, funded programmes, not aspirations. The detail will shift; the shape won't. Here are some examples of problems you’ll need to solve.
Zero Touch — self-service refunds and exchanges. Most of our contact‑centre volume is travellers asking whether they can cancel or change, and most of them don't proceed once they see the cost. You'll make that answer instant, accurate, and self‑serve — genuinely end to end, including back‑office execution and finance reconciliation. A refund that looks automated to the traveller but spawns four manual touches behind the scenes hasn't been automated, it's been moved. You'll also design the hybrid cases, with a human in the loop.
A booking record that reflects reality. You'll help define a store that traces a trip across its full lifecycle with every money movement attached, and that reconciles sources when they disagree — which they do, sometimes on the same booking, in ways that cost us real money.
Untangling the money. Payment fees, markups, booking fees, supplier costs, penalties, and the residue of every reprice, currently spread across a dozen-plus spreadsheets and recurring arguments about which one is right. You'll work with Finance Ops on the mid‑office layer that puts it all on one record — including the honest build‑versus‑buy call.
Read this as a preview of your first quarter, not as a warning.
90% accurate is not a pass. In most products a heuristic that's right nine times out of ten is a win. Here, the 10% is a traveller told their ticket was refundable when it wasn't — so we either break a promise or eat the loss — or a void we shouldn't have processed, which returns as an airline debit six months later with a penalty attached. You'll have to reason about failure cost per decision, not aggregate accuracy.
The truth is spread across systems that don't agree. There is no single row you can trust. Much of this work is deciding what the source of truth is before you can automate anything on top of it.
Money moves before the answer is known. Funds have often already gone to the supplier by the time we decide what the traveller is owed. Product decisions here land directly on finance reconciliation, and you'll need to design with that in mind rather than hand it over.
Complexity we're choosing to keep. Continuous reprice optimization is a significant profit stream. We are not turning it off to make servicing simpler. You'll be automating on top of a system that deliberately mutates bookings after sale.
Some rules only exist in someone's head. A real part of this role is operational design: turning tacit knowledge held by a handful of people into something a system — or an AI agent — can act on.
Strategy and vision. Define and evolve the strategy for your Flights problem space, aligned to marketplace growth and commercial objectives. Identify where we can be structurally more competitive, and translate that into measurable outcomes.
Roadmap and delivery. Own the roadmap and its sequencing, prioritising on customer value, business impact, technical feasibility, and dependency risk. Lead initiatives through discovery, validation, delivery, experimentation, launch, and optimisation. Balance near-term commercial wins against foundational platform investment — and be able to defend the trade-off.
Experience quality. Champion a fast, intuitive, and above all truthful experience at every stage. Optimise relevance, price presentation, filtering, comparison, provider selection, fulfilment, and self‑service. Validate with research, experimentation, and behavioural data.
Data and performance. Partner with Data Science and Analytics on funnel health. Define and track KPIs across acquisition, engagement, conversion, retention, traffic quality, provider performance, cost‑to‑serve, and marketplace efficiency.
Cross‑functional leadership. Work across Engineering, Design, Supply, Commercial, Marketing, Revenue Management, Finance Ops, and Customer Support. Communicate priorities, decisions, and trade‑offs clearly. Build alignment without direct authority.
Market intelligence. Track airline distribution shifts, NDC adoption, competitor moves, and emerging technology — particularly AI applied to fare interpretation and servicing — and turn that into initiatives.
Risk and operational excellence. Surface delivery, technical, commercial, and regulatory risk early. Improve experimentation frameworks and development process. Keep decisions consistent with platform stability and long‑term maintainability.
Expect the interview to be concrete. We'll walk through a real servicing scenario and ask how you'd sequence it. We'll show you an actual fare rule and ask you what it means. We'll ask about a time your product decision created a downstream operational cost, and what you did about it.
We're not testing recall of jargon. We're testing whether you've lived in this problem and have opinions about it.
Very few flights teams get to rebuild shopping, booking, and post‑booking at once, at real scale, at the exact moment the underlying technology has changed enough to make a fifty‑year‑old problem tractable. Fare rules have been an industry punchline for decades — people were calling them unsolvable when today's AI didn't exist. That's no longer true, and we intend to be early rather than late.
Behind every search, booking, and trip is a team that would rather fix the hard layer than paper over it. If that's the work you want, we'd like to talk.