Company Context
You’re the PM for Nova, a Series D fintech app with 12M monthly active users in the US. Nova started as a fee-free checking account with early wage access and has expanded into debit, savings, and bill pay. Revenue is driven by interchange, subscription (Nova Plus at $8/month), and referral partnerships.
Nova is competing against Chime, Cash App, and Credit Karma. The company’s strategic goal this year is to expand into “financial health” products that increase retention and subscription attach rate without taking on regulated credit risk (Nova is not a bank; it partners with an FDIC-insured sponsor bank).
Nova’s leadership believes the next growth lever is helping underbanked users build credit safely and transparently.
Product Opportunity: “Credit Builder” Feature
Nova wants to launch Credit Builder, a feature that helps users establish or improve credit by reporting on-time payments to credit bureaus. The initial concept:
- Users set aside $25–$200/month into a locked “Credit Builder” balance.
- Nova charges a small monthly fee (e.g., $4.99) or bundles it into Nova Plus.
- Nova reports successful monthly payments to bureaus via a partner.
- Users see progress via a “Credit Health” dashboard.
Why now
- Internal research suggests 38% of Nova’s active users have a credit score under 650 or no score.
- In surveys (n=4,200), 52% of respondents said “improving my credit” is a top-3 financial goal.
Current funnel (baseline from a limited beta landing page)
| Step | Metric (weekly) |
|---|
| View Credit Builder landing page | 1,000,000 |
| Tap “Learn More” | 14% |
| Start enrollment | 6% |
| Complete KYC + consent | 3.2% |
| Make first successful monthly payment | 1.9% |
| Still active after 3 months | 0.9% |
User research highlights (qual + quant)
- Trust and fear of harm: Users worry about “doing something wrong” and hurting their score.
- Confusion about mechanics: Many users don’t understand what gets reported (utilization vs payment history).
- Cash flow volatility: A large segment has irregular income; they fear overdrafts or failed payments.
- Skepticism about fees: Users compare against free alternatives and are sensitive to “hidden costs.”
Competitive Landscape
- Chime Credit Builder: Strong brand association; simple messaging; heavy emphasis on “no interest, no fees” (though users still perceive complexity).
- Self: More complex but established; users accept fees when outcomes are clear.
- Credit Karma: Strong education layer; weaker direct product action.
Nova’s differentiation today is a highly rated app experience (4.8 App Store) and strong customer support, but it has less credibility in credit.
The Core Challenge
You are asked to define how Nova should approach feature experimentation for Credit Builder.
Leadership wants speed, but Compliance and Risk are concerned about:
- Fair lending / UDAAP risk (misleading claims, unclear fees, confusing consent)
- Data privacy and bureau reporting consent
- User harm (failed payments, unexpected outcomes, support burden)
- Brand trust (Nova’s NPS is 52; leadership will not accept a material drop)
Your Tasks (Deliverables)
- Clarify the user job(s) to be done and identify the primary target segment(s) for the first iteration.
- Propose 3–5 experimentable hypotheses across the funnel (activation, retention, monetization, education/trust).
- Design an experimentation strategy that fits fintech constraints:
- what you would A/B test vs what you would validate via holdouts, phased rollouts, or qualitative methods
- how you would define guardrails and stopping criteria
- Define the MVP scope and a prioritization rationale (e.g., RICE/Kano), including what you will not build yet.
- Specify success metrics (with targets) and how you’ll attribute impact while avoiding misleading short-term wins.
Constraints
- Timeline: MVP must be in market within 10 weeks.
- Team: 1 PM, 6 engineers (mobile + backend), 1 designer, shared data scientist (25% allocation).
- Experimentation platform limitations:
- Client-side A/B testing exists, but server-side experimentation is limited.
- Credit bureau reporting requires batch processing; outcomes lag by weeks.
- Compliance requirements:
- All user-facing claims must be pre-approved.
- Consent flows must be explicit; cannot be bundled into generic terms.
- Risk tolerance:
- Must keep complaint rate below current baseline.
- Must not increase support tickets per 1,000 users by more than 15% during rollout.
What information you can assume you have
- Event-level analytics for the funnel steps above
- Ability to run in-app surveys and intercepts
- Access to customer support tagging and call drivers
- Partner provides bureau reporting status and (delayed) score change indicators
Your interviewer will evaluate how you structure the problem, choose experiments, define metrics/guardrails, and make trade-offs under regulatory and trust constraints.
