Why this role exists

Hotels and Activities are the fastest-moving parts of the business, both built on supply data from several sources that rarely agree with each other. That data quality decides what every user sees: which products come up, in what order, at what price, and whether the booking holds. This role owns that layer, full time: live, growing, making what's already there work better and building what isn't there yet.

You'll get handed pieces to run: a data problem, a breaking journey, a slice of a release. You're accountable for them end to end, and they grow as you show you can carry them. Because the product takes real bookings every day, the work lands fast: clean up a duplicate listing, improve recommendations or catch a broken flow, and you've changed what someone experiences that week.

What we're looking for

- Final year or recent graduate, from a technical background. You know at least one programming language well enough to understand how software is put together, and can carry that understanding somewhere new: an unfamiliar API, a database you've never seen. Your first move is to open it up and work out how it behaves yourself
- You think clearly, and you can get that thinking across to someone else. Almost everything you produce is a document, a ticket or a table
- You default to thinking like the person using the product, not the person who built it
- You can hold several things at once and work out what actually needs doing first, even when everyone around you thinks their thing is the priority
- You're properly good with AI: less prompting, more building it into how you work day to day, using it to get further, faster; judging whether the output is any good stays your job.
- You're comfortable with data: a large, messy, half-wrong set of it doesn't put you off
- You can sit with being confused for a while,



and you'd rather ask a basic question out loud than guess quietly

Bonus, not required: prior product experience, a real interest in travel or exposure to the industry, a sense of humour.

How to apply (apart from the easy apply)

Email [email protected] and [email protected] with your CV and two things.

Something you've built that you're proud of, and that works. A project, a tool, a script, a teardown. Doesn't have to be about travel. Send it, or a link to it.

The documentation for it. A README, a spec, your notes: whatever would explain it to someone who wasn't there. If none of that exists, tell us how you thought your way through it instead.

What you'll do

Product work borrows from every function around it: QA one week, design the next, engineering or numbers after that, all filtered through how the person using the thing would actually experience it. The harder part is judgement: knowing what not to do, and saying no when it's needed.

Research. Becoming the person on the team who actually knows how this stuff works.

- Get deep enough into how our supply and systems actually behave that you can spot where two sources disagree, before a customer does
- Study how other platforms have solved the same problems, and understand the reasoning behind their choices, not just what's on screen
- Explore markets and supply we haven't launched yet, and come back with a view on what it would take

Analysis. Working out what the product is actually doing,



and what to do about it.

- Pull your own numbers and turn what you find into a recommendation someone can act on
- Size opportunities before we commit engineering to them, and check what actually moved once we've shipped
- Talk directly to users, and to the people who deal with it when something breaks. Write up what the product should have prevented

Product lifecycle. Taking work from a rough idea to something live, and staying with it after it ships.

- Turn vague problems into scoped work, with requirement docs engineering can build from without a follow-up meeting
- Test the journeys that matter end to end, the way a real user would hit them
- Chase fixes with partners until they actually land, which sometimes takes weeks of staying on it
- Keep the backlog honest: groomed, prioritised, free of tickets nobody intends to do

The kind of problems here

Two examples

- Discovery: getting someone from a vague intention to the right place to stay, through search, recommendations, collections, or something we haven't built yet.
- Content: making a property read like somewhere a person would want to stay, when the information about it arrives from several sources, inconsistent and half-filled.

Most of what's here looks like this: data problems as much as product ones. Which ones you get near, and when, depends on how the early months go.

What you'll get

- 3 to 6 months, paid, with conversion to a full time product role if it works out
- Pieces of a live system with your name against them, still in the product long after the internship ends
- Direct working relationships with engineering, design and ops. We're small and ship fast
- No layers between you and the product manager who owns Hotels and Activities: close review, straight feedback

📌 Product Management Intern (Bengaluru)
🏢 OnArrival
📍 Bengaluru