Product design question

You are a new PM at Google Pay. Design a feature for paying credit card bills.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests product design for a specific financial utility feature: reducing missed payments and friction for a well-defined recurring task.

Clarify scope: paying a credit card bill from any issuer within Google Pay, not a full card-management suite.
Identify the user: someone juggling multiple cards and due dates who currently pays via separate bank or issuer apps.
Identify the core job: see all linked cards' balances and due dates in one place and pay with minimal taps.
Propose a Bills tab listing linked cards with balance, minimum due, and due date, one-tap pay from a linked bank account, and optional autopay.
Address risk: autopay failures from insufficient funds must trigger a clear, early warning rather than a silent missed payment.
Define success: on-time payment rate for enrolled users versus a control group, and autopay opt-in rate.

Scopes tightly to bill payment and due-date visibility rather than a broader card-rewards or spend-tracking feature.
Names a concrete UI element, a Bills tab aggregating due dates, addressing the real pain of multi-card juggling.
Treats autopay failure as a first-class risk with an explicit early-warning design, not an afterthought.
Defines success with a causal metric, on-time payment rate versus control, not just feature usage.

Building a generic finance dashboard instead of solving the specific bill-payment and due-date problem.
No safeguard for autopay failures, which could cause real financial harm and erode trust.

How would you handle a user whose card issuer doesn't support direct integration?
How would you communicate a failed autopay attempt in time to avoid a late fee?