Senior Product Engineer - Supply Team

Hi! 👋 I’m Fedir, Engineering Manager for Team Supply at WeTravel

Our team’s mission is to turn WeTravel from a product into a network. Today a travel operator can run their own business on WeTravel. Next, we want them to plug into each other, co-selling trips, sharing itineraries, and settling commissions automatically, without a single spreadsheet or bank transfer in between. If you want to build the operating system an entire industry runs on, and to be in the room when we decide what that system should be, let’s build something we’re proud of, together!

About WeTravel

Think of the most incredible adventures imaginable: trekking to Machu Picchu, cycling through Tuscany, or going on a safari in Kenya. For years, the small businesses and local experts who run these trips have been stuck using messy spreadsheets, countless emails, and complicated payment methods.

WeTravel is changing that. We build the tools that empower any entrepreneur to launch and grow their own travel business. Our platform makes it simple for organizers to create beautiful trip proposals, securely process payments, and manage their customers, so they can focus on what they do best: creating amazing experiences.

This is one of the last great frontiers of travel to come online, and as the category leader, we are at the forefront of this change. Last year alone, our platform was trusted by 8,000 organizers to lead over a million travelers on adventures in 150+ countries. Now, we’re on an exciting journey to grow from powering $1B to $10B in travel experiences per year.

We believe that every trip, when done right, can be a force for good - and we’re building the engine to make more of that possible.

What’s the role

Almost no travel operator works alone. Agents, B2C tour operators and destination management companies buy from suppliers, resell each other’s trips, and split the money afterwards. Today that all happens in spreadsheets, WhatsApp threads and PDF quotes; Which is why pricing a trip takes days, and why nobody can tell you two years later how a number was calculated.

Team Supply is building the layer that replaces it. We’re five engineers, and a PM, working on the earliest part of WeTravel’s roadmap: first the single-player OS, how an operator designs a trip, prices it, and sells it, then the multiplayer layer that connects operators to their suppliers and to each other. Getting this right makes WeTravel the tool operators open every morning, and roughly doubles the market we can serve.

You’ll join us to build that foundation and take it from early access to something thousands of operators depend on. What’s on our plate:

Quoting: a pricing engine in our new service: multiple currencies, tax regimes, margins, seasonal rates.

Supplier & Product Catalog: a place where operators keep their suppliers, negotiated rates and reusable trip building blocks.

The Partner Network: supplier onboarding, verification and payouts, so money moves between operators and their suppliers automatically.

Next up, the explicitly multiplayer pieces: supplier arrangements, commission flows, and a booking marketplace.

It is, in effect, a startup inside a company that already has customers, revenue and scale, much closer to 0 → 1 than most senior roles you’ll look at this year.

What you’ll do day-to-day

Lead and build features end-to-end: from reviewing user interviews and product design, through architecture and building systems, to deployment and monitoring in production.

Partner closely with our product team to discover user problems and shape their solutions, you’ll help decide what is worth building, not only how to build it.

Write high-quality, maintainable code across the backend (Ruby on Rails) and frontend (TypeScript/React).

Ensure our services are always on by building resilient applications, making sure they are well monitored, and mitigating incidents as an on-call/incident responder.

Mentor teammates and contribute to WeTravel’s engineering practices and excellence.

How we work

We’re focused on the impact. We don’t subscribe to any one framework or execution ideology, and we adapt based on what’s impactful.