Senior Product Manager

Why this exists

What if the app that handles your home's money actually understood how homes work Fave is a UPI app built around homes, not individuals. Flatmates splitting rent and groceries. Dual-income couples managing a household together. Families paying the cook, the maid, the driver. The everyday money that moves between the people you live with — finally in one place

The role

UPI apps today are utilities. Open, pay, close. Nobody thinks about them. Nobody talks about them. That's the gap. Fave is the chance to build a payments app people actually have feelings about. One that understands the weird, messy, real ways money moves inside a home — and makes all of it effortless. If we get this right, we're the operating layer for how Indian households manage money together. You'd own the product end-to-end. Not a feature. Not a pod. The whole thing — payments, household features, growth loops, monetization, whatever comes next. There's no VP of Product handing you a roadmap. You'd be shaping what Fave becomes. Day to day, you'll write specs that people actually want to read (yeah. writing is a good proxy for thinking, so we strongly encourage writing instead of generating). You'll think about how a payments screen becomes a reason someone tells their flatmate to download the app. You'll also build. Prototype a feature before writing the spec. Ship a growth hack over the weekend. Build an agent that automates a product ops workflow you're tired of doing manually. AI is how a small team punches above its weight — and you'll use it that way every day

What you'll spend time on:

Defining what Fave builds next — and, harder, what it doesn't Designing product experiences alongside our designer. You have taste. Use it Obsessing over activation and retention as much as shipping Thinking about distribution as a product problem: referrals, sharing moments, screenshots people actually post Talking to users constantly

Who we're looking for

We want instinct. The best PMs we've met don't reach for a prioritization matrix when they're stuck. They look at the product, talk to three users, and know. Frameworks are fine. But if that's where your conviction comes from, this isn't the role. 4-6 years building consumer mobile apps. You've shipped things real people use daily You've been close to zero-to-one at least once. You know the difference between growing something that exists and willing something into existence Strong product taste — you notice when a flow is off, when copy is lazy, when an animation is 100ms too slow You think about distribution before you think about features. How does this spread is always the first question AI-native. You've built prototypes, automated workflows, or shipped something real using LLMs and AI tools. You treat AI as a multiplier on your output, not a novelty

Bonus: You've worked at a company small enough that you couldn't hide behind process. You've made something go viral at least once, even if by accident.