Senior Product Designer

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 made payments invisible. That's the problem. The thing people use more than any other app on their phone became the one they think about least. Fave is the chance to change that — to take something people do five, ten times a day and make it actually feel like something. No one's built a payments app around how homes work. Not flatmates, not couples, not families. If we get this right, we're the operating layer for how people manage money together. UPI does 14 billion transactions a month. That number's only going up. You'd be designing for a product that could be in millions of hands, used daily — and you'd be doing it from scratch. You'll be the second designer on a very small team. No committee. No layers. End-to-end ownership — from the first sketch of a feature to how it looks in someone's hands. Day to day, you'll design flows, write copy when copy matters, and think about how a screen might go viral before you think about whether it follows the grid. You'll ask how do we make this feel magical before is this consistent with the design system You'll also think beyond the app. How does this screen look in a reel How does this feature become something people show their friends Design and distribution aren't separate problems here.

What you'll spend time on:

→ Designing consumer flows with zero industry-standard handcuffs — if it needs to break the mold, break it → Writing UX copy, onboarding text, microcopy — there's no dedicated content designer → Working directly with engineers; we ship fast, no 15-step handoff process → Using AI tools aggressively — delegate the boring work, save your taste for decisions that matter → Thinking about how a feature becomes a reel, a screenshot, a reason someone tells a friend to download the app

Who we're looking for

We want taste. Not a clean Figma file.

In the post-AI world, a well-organised component library is table stakes. What's rare is judgment — the ability to look at a screen and know something's wrong before you can explain why, and fix it before lunch. Use Figma if that's your thing. Write code directly if that gets you closer to the output faster. We only care about what ships. → 4–8 years designing consumer mobile apps, with time in high-stakes flows — fintech, commerce, or health → A portfolio that shows thinking, not just execution — what was the problem, what you decided, what you'd do differently → Strong opinions on what beautiful means, and the confidence to defend them → Already using AI in your daily workflow, or aggressively learning to → Comfortable starting from nothing — no brief You write it. Fuzzy problem You sharpen it

Bonus: You think about virality and usability as the same problem. You've worked on a team small enough that there was no one else to blame.