Product Design: Money Management App for University Students
Company: Brex
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are asked to build a money app for college students. Walk through who you would design it for, which problems it should solve first, and how you would know it is working.
```hint Students are not one user
Income, family support, loans and credit history vary widely between students. Pick one group and one money problem that matters to it before sketching features.
```
### Clarifying Questions
- Are we a new startup or an existing financial company expanding to students, and can we offer accounts and cards through a partner bank?
- Is success measured by user growth, near-term revenue, or keeping these customers after they graduate?
- Should I design for students in the US, where loans and building a credit history are central, or for another market?
- Which students should I target: undergraduates, graduate students, international students, or all of them?
### What a Strong Answer Covers
- A deliberate choice of student segment, justified by how students differ in income, family support and financial experience
- Pain points for that segment, ranked by how often they occur and how much they hurt
- A focused first version mapped to the top pain points, with what is left out and why
- A business model and campus go-to-market that do not depend on fees that harm students
- Success metrics and the main risks: regulation, credit harm, fraud, trust and churn at graduation
### Follow-up Questions
- How would the product make money without charging fees that hurt students?
- What does the product offer a user in the year they graduate, so that they stay?
- Would you offer students credit, and what limits would you put on it?
Overview: A product design question that asks a product manager candidate to design a financial app for college students. It tests segmenting students by how they receive and spend money, prioritizing real pain points, scoping a focused first version, choosing a business model that does not harm users, and defining success metrics and risks.