Full-Time
IC Role
2–4 Years
HSR Layout, Bengaluru
ABOUT POP
We're POP, a new-age fintech company making payments fun, rewarding, and worth it. With POP UPI, you earn POPcoins on every payment, real rewards redeemable across multiple brands on POPshop, our curated D2C marketplace spanning fashion, beauty, food, and electronics. Founded in Bengaluru in 2023, backed by Razorpay and partnered with YES Bank, we're building India's most rewarding payment experience.
The core loop we're building: Pay on POP → Earn POPcoins → Discover something you love on Shop → Redeem at 1:1 value → Come back. That loop only gets smarter with every cycle — if the app actually learns who you are. Platform is the team that makes POP feel less like a utility and more like something that genuinely gets you. That's what this role owns.
WHY THIS ROLE MATTERS
Most apps treat their users as anonymous transactions. POP doesn't.
When you open POP, you should see offers that make sense for you, get nudged at the right moment, and have a payment experience that just works. This role owns the layer that makes all of that possible — deep personalization across every surface of the app, and increasingly, outside it. What POPcoins offer surfaces to which user. What reactivation message lands when. What the app says to a first-timer vs. someone who's been with POP for a year.
You're not building features for a single product. You're building the intelligence layer that makes every product team on POP smarter — and the user experience sharper. That's a harder, more consequential job. And it'll touch more users than any single feature ever could.
WHAT YOU'LL BUILD
Knowing the User
Two users open POP. One has been here for a year. One just signed up. Should they see the same thing?
Behavioral signals exist. The gap is turning them into a coherent, real-time understanding of each user — and making that available to every product team without them rebuilding the same logic independently. You'll define what "knowing a user" means at the product level and own the system that answers that question.
A product team wants to target a specific cohort. Today that takes two days and a data request. How do you make it self-serve?
Segmentation is a product primitive, not a marketing tool. The bar: any PM on any team should be able to define and activate a precise user segment on their own.
Talking to the User
POP sends a notification. The user ignores it. The one that would've converted never goes out because the system assumed they'd tuned out. How do you fix that?
The wrong message at the wrong time is worse than silence. You'll build the orchestration layer that learns per-user preference, suppresses noise, and surfaces the right moment across push, SMS, and in-app. Not a campaign tool — a retention system.
Every surface of the app — home screen, offers, nudges — looks the same for everyone. How do you make it feel like it was built for each user?
In-app personalization is the final frontier. You'll define the decision logic and work with every product team to make their surfaces dynamic rather than static.
Powering the App
Multiple product teams run on the same payment infrastructure. How do you make sure you're an accelerator for each of them, not a bottleneck?
Shared infrastructure requires shared accountability. You'll own the payment layer every team depends on — and design it to be fast to onboard, hard to misuse, and reliable when it matters.
WHAT WE'RE LOOKING FOR
- Systems-minded. When a product team brings you a request, your first instinct is to ask whether it should be a shared capability or a one-off. You know the difference, and you've been wrong about it before.
- User-obsessed, even when your direct customers are internal teams. You hold the end user in your head through every infrastructure decision.
- You've shipped something real — identified it, argued for it, built it, proved it out. Consumer fintech, payments, commerce, or personalization background is a strong fit.
- Comfortable with technical depth. You don't write code, but you can read a system design and ask the right questions. You know why schema changes are expensive. You understand the difference between a sync and async call.
- You iterate fast and share early. You move without a polished brief and know how to instrument a hypothesis.
- AI-native. You think about where AI belongs in the product, not just in the process. You can tell the difference between AI as a feature and AI as a primitive. If you've scoped, shipped, and measured something with an AI component in it — tell us about it.
- 2–4 years of PM experience at a consumer product or early-stage company.
THIS ROLE IS NOT FOR YOU IF
- You need clear requirements to move. High ambiguity is the default here.
- You think the platform is just making APIs and writing documentation.
- You haven't owned a 0→1 product.
- You'd rather execute a brief than write one.
- You think personalization is a growth team problem, not a platform problem.