About Jeeny:
Jeeny is a mobile application that eases daily commuting and transportation. By connecting you with your preferred mode of transportation, we are fulfilling our aim of making mobility accessible, affordable, and flexible for all.
We are a joint venture between MEIG (Middle East Internet Group), Rocket Internet, and IMENA. Jeeny was established in 2014 as Easy Taxi. However, in 2016, it was revamped as Jeeny to cater to other services. Currently, we are operational in Saudi Arabia and Jordan.
We have offices in Riyadh, Jeddah, Madinah, Amman, Lahore, and Karachi.
About the Role:
We are looking for a Product Manager - Passenger Experience to own the passenger side of Jeeny, working from our Lahore team.
Jeeny is a ride-hailing platform in Saudi Arabia and Jordan. A passenger opens the app a few times a week, usually mid-errand, sometimes in a hurry, and often with a competitor's app open in the next tab. That makes this a product job about trust and speed: every screen between "I need a ride" and "a car is coming" is a chance to lose someone.
Responsibilities: What you will own
The Jeeny Passenger App on Android and iOS, the rules that sit behind it, and what happens commercially after you ship. In practice, six areas:
The booking funnel
- Opening the app, checking a price, choosing a pickup point and destination, requesting a ride, watching it get accepted, and boarding.
- You decide things like: what the price-check screen shows before a passenger commits, how a saved or recent destination gets surfaced, and what the app does when an offer expires or a driver cancels right after accepting.
Payments, wallet and pricing
- Wallet balance, digital payments, saved cards, promo codes, cashback, and subscription plans.
- You decide things like: when a promo applies automatically versus needs to be entered, how a subscription's savings get shown before someone pays for it, and how a passenger who thinks they were overcharged gets an answer.
Trust, ratings and support
- Driver ratings, cancellation reasons, in-app help, and the review queue on Google Play and the App Store.
- You decide things like: how many cancellation reasons we show before a passenger gives up and calls support instead, what the help centre surfaces first, and how a bad ride turns into a compliment or a complaint instead of silence.
- These affect whether someone opens the app a second time, so they get treated as product decisions with real weight, not as configuration.
App quality
- Crash rate, ANRs, app store ratings, and the review queue on Google Play and the App Store.
- You watch these weekly, decide what gets fixed first, and make the case for engineering time when quality work needs to beat feature work.
Tracking and analytics
- Which passenger actions get logged as core database data or tracking events, and whether those events actually work.
- Concretely: you specify the app tracking events and feature level data for any feature you ship, check they fire correctly on both Android and iOS before and after release
- This is absolutely critical and the reason the rest of the job is possible. Roughly a day every few weeks
Launch, adoption and commercial impact
Shipping is not the finish line. This part of the role grows over your first year, and we do not expect you to arrive fully formed in it. You will have your manager, and the KSA + Jordan business teams alongside you. But this is where we want the seat to end up, so we would rather be honest about it now.
- The go-to-market plan. Which passengers get it first, how they hear about it (in-app, push, SMS, WhatsApp, social), what the message actually says in English and Arabic, and how support gets briefed before it lands. You will shape this with marketing rather than hand the feature over and hope.
- Adoption. Over time this becomes your number. If a feature you built is being used by eight percent of eligible passengers a month after launch, we treat that as a product problem rather than a marketing one, and you are the person digging into why.
- The commercial case. For anything with a money angle, a subscription plan, a promo budget, a referral incentive, we want a view on what it costs, what it should return, and how you would know. If you have never built one of these, we will teach you the mechanics. What we need from day one is the instinct to ask the question before you build.
Discovery and research, which is a third of this job
This is the part we most want to grow, and it is what separates a product manager from someone who writes tickets faster. We would rather you spent two weeks properly understanding a problem than two days guessing at it.
- Get close to actual passengers. Not only through reports from operations. Read the Arabic app store reviews, listen to support call recordings, join a visit to a driver hub in Riyadh to see the other side of a booking, and speak to passengers directly when you can.
- Watch real sessions. Visual product analytics tool replays show you where passengers hesitate at price check, abandon at payment, or back out of a screen entirely. That is usually more honest than anything a passenger will tell you in an interview.
- Write the discovery down before the solution.