Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

Jupiter
Product Design Medium Member-only

How would you design a Jupiter Pots experience for gig workers with irregular income?

Prepared by NextSprints

15 mins
Report an error
User Empathy Solution Design Prioritization Fintech Digital Banking Fintech India Savings Product-Design Gig-Economy
Product Management Design Question: Jupiter Pots savings for gig workers with irregular income

Introduction

Jupiter's Pots let users park money for a goal inside their savings account, separate from day-to-day spending money. The feature works well for salaried users who get paid on the first of the month and can set a fixed monthly transfer. It works far less well for India's growing base of gig workers, such as delivery partners, ride-hailing drivers and freelancers, whose income lands in small, irregular amounts several times a week. This question asks for a Pots experience built around that irregular income. I'll clarify the goal, explain why the opportunity matters, pick a segment, map pain points, design a solution and close with metrics.

Tip

In a design question about a fintech product, say early that you are designing within the rules of the regulated partners. Jupiter is not a bank; the account and deposit insurance come from its partner bank. Interviewers like candidates who know where the product's freedom ends.

Step 1

Clarify Questions (3 minutes)

Before designing, I would ask the interviewer a few questions:

  • Is this a new feature or a change to existing Pots? Assume it is a new mode within Pots, so existing users are not disrupted.
  • Which gig workers? Assume platform workers paid weekly or daily by aggregators (food delivery, quick commerce, ride-hailing), plus online freelancers paid per project.
  • Is the goal savings balance, retention, or acquisition? Assume the primary goal is to make Jupiter the main account for gig workers, with savings as the habit that keeps them.
  • Any constraints? Pots money stays in the user's own partner-bank account. No new lending product is in scope, and we cannot promise a higher interest rate than the account pays.
  • Platforms? Android first, since most gig workers use mid-range Android phones. Hindi and other regional languages should be supported.

Propose the Goal

Help gig workers with irregular income build a cash buffer automatically, so a slow week does not force them into high-cost borrowing. For Jupiter, the business goal is primary-account status: if a worker's payouts land in Jupiter, card spends, UPI payments and later credit products follow.

Define the Scope

In scope: how money moves into Pots when income is irregular, how users see and protect their buffer, and how they withdraw in an emergency. Out of scope: credit lines, insurance and tax filing, which can be future extensions.

Tip

Stating out-of-scope items is as useful as stating scope. It shows you can say no, which is the most common thing a PM does.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Oct 31, 2026