Design a product for college students

Q: Design a product for college students.

How to answer this PM interview prompt in 2026. Pick a sub-segment, surface the institutional buyer, and propose something lovable, not just usable.

About 60% of candidates who get this prompt open with the same four pain points: mental health, budgeting, productivity, and social connection. Interviewers recognize this because it is the answer someone produces when they Google “college student problems” rather than reason about a specific person. The prompt is designed to test whether you can resist the temptation to design for a label and instead find the real unmet need inside a large, heterogeneous population.

“College students” is 20 million people in the US alone. The right first move is to decompose the group and pick one context worth designing for.

Scope the segment before you brainstorm

Strong candidates pick one of these and defend it in under 60 seconds:

First-generation college students. The sharpest information asymmetry in higher education. They navigate institutional systems (financial aid appeals, add/drop deadlines, office hours norms, academic probation rules) with no social network to ask questions and no prior model of what college actually requires.
Graduate students. Research-track students face a completely different problem set: advisor relationships, funding uncertainty, publication pipelines. The tools they need are closer to knowledge workers than undergraduates.
Student athletes. Navigating NCAA compliance, travel schedules, and academic requirements simultaneously. The coordination burden is high; the existing tooling is poor.
Transfer and international students. Orientation to a new institution with no existing social capital, compounded by bureaucratic complexity.

First-generation undergraduates are the strongest pick for this interview because the unmet need is specific, the failure mode is concrete (missed deadline, lost aid, drop-out), and the institutional buyer is visible before you even propose a feature.

The pain points worth building for

Within the first-gen segment, three problems are real:

Institutional illegibility. Navigating the university’s own systems (SIS, financial aid portal, advising calendar) is genuinely hard. The information exists but is buried in PDFs, department-specific portals, and emails that arrive without context. A missed financial aid verification deadline can cost a student their entire aid package.
Not knowing what you do not know. First-gen students disproportionately suffer from the absence of an informal network. They are reluctant to expose confusion to peers or professors who seem to expect fluency. The problem is not that information is unavailable; it is that they do not know which questions to ask.
Misaligned expectations about workload. The rhythm of college (midterms arriving weeks apart, syllabi that are aspirational rather than firm) is not intuitive to students who have only experienced structured K-12 schedules.

Pick pain point one. It has the clearest path to a defensible product and the clearest institutional buyer.

The product

A campus navigator that integrates with the university’s SIS and LMS and pushes the next 2-3 actions the student needs to take this week. Not a to-do list the student maintains. A push-based feed that surfaces what they do not know they need to do before Friday.

In 2026, the technical problem is trivial. An LLM reading a student’s course schedule, enrollment status, financial aid standing, and institutional calendar generates personalized nudges at pennies per student per day. Feasibility is not the constraint.

The hard problem is lovability. Students have extreme app fatigue. The product that asks them to install and open a new app will not get used. The right answer is to embed delivery in a channel they already live in: SMS, or a tile inside the university’s existing app. The first MVP skips LMS integration entirely and runs on SMS with a simple onboarding flow where the student registers their student ID. That clears the university IT procurement problem and gets to a working version fast.

The nudge design is where this product earns trust or loses it. Obnoxious AI antipatterns apply directly here: notifications that fire daily, reminders for things the student already completed, and “motivational” copy destroy trust fast. The product earns the right to nudge by being right, brief, and quiet. Three nudges a week is a better default than three a day.

Why this is viable, not just useful

Students have extremely low willingness to pay. Any product that monetizes directly through students will hit this wall immediately. YNAB has offered a free year-long trial for college students for years; this is not generosity, it is an admission that student-direct monetization of financial tools does not work. The market has already run the experiment.

The institutional buyer is the university. Universities have real budgets for exactly this problem: Title IV compliance requires retention tracking, and fall-to-spring retention rates are a metric university administrators report to boards and accreditors. A product that demonstrably improves first-gen retention by 5-10 percentage points is worth real budget. Retention tooling sells to university student success offices at $15-40 per enrolled student per year. This is a B2B2C motion, not a consumer viral loop.

The monetization model also clarifies the success metric. The right north star is not DAU. It is 30-day retention among first-gen freshmen, with fall-to-spring retention as the lagging institutional signal the university already tracks.

The viability trap most candidates fall into

Mental health apps face a related ceiling: 70% of college students report a mental health concern in the past year, but the category is saturated and institutional procurement for mental health tools is slow and politically fraught. Going here without a differentiated angle signals no market research. The same applies to budgeting, social, and generic AI productivity: all three have had multiple well-funded attempts at the student market, and none have found durable monetization.

The candidate who knows this, and can say it explicitly before pivoting to whitespace, signals product taste. The candidate who reaches for these categories first does not.

strong

"College students is a large and diverse group. Before I brainstorm, I want to pick a specific context where I think there's a real unmet need. I'm going to focus on first-generation college students navigating the transition into college. This group has the sharpest information asymmetry and the least social capital to compensate for it.

The pain point I want to solve is institutional illegibility: these students are navigating financial aid deadlines, add/drop rules, and advising norms with no informal network to ask questions and no prior model of how college works. A missed financial aid verification can cost a student their entire aid package. The stakes are high and the information is genuinely hard to find even for students who know where to look.

The product: a push-based campus navigator that integrates with the university's SIS and proactively surfaces the 2-3 actions a student needs to take this week. Not a to-do list. A feed that tells you what you don't know you need to do. In 2026, the LLM that reads a student's course schedule and financial aid status and generates a personalized nudge costs pennies and requires no specialized ML team. The hard problem is not building it, it's getting students to use it without it becoming another ignored notification.

I'd embed delivery in SMS for the MVP, which skips university IT procurement entirely. The nudge design has to be disciplined: three nudges a week maximum, always specific, never motivational. The product earns trust by being right and quiet, not by being frequent.

Viability: this is a B2B2C play. The university pays, not the student. Universities track fall-to-spring retention as a board-level metric and have budgets assigned to improving it. A product that demonstrably improves first-gen retention is worth $15-40 per enrolled student per year to a student success office. My success metric is 30-day retention among first-gen freshmen, with fall-to-spring retention as the lagging institutional signal. The main constraint I'd flag: this product depends on university sales cycles, not consumer virality. That shapes the go-to-market completely."

weak

"College students deal with mental health, money, productivity, and social connection. I'd build a super app with four features: a mood tracker, a budget tool, a study timer, and a social feed. Using a 2x2 impact/effort matrix, I'd prioritize the mood tracker as the MVP. I'd measure success with DAU and NPS."

Why this fails: (1) No sub-segment. Designing for all 20 million college students produces the average of nothing. (2) The mental health plus budget plus productivity stack is the default answer. Every interviewer has heard it. It signals no market research. (3) The super-app structure avoids the hardest question: what one problem does this product own? (4) No viability thinking at any point. Students have near-zero willingness to pay for a mood tracker. Who pays? The candidate never asks. (5) DAU and NPS do not connect to the specific value proposition. Interviewers see this answer from roughly 60% of candidates. It does not clear the bar.

What the interviewer is scoring

Five signals: user empathy, structured thinking, product taste, strategic awareness, and communication. Product taste is the signal most candidates fail to demonstrate. It shows up in whether you can identify a non-obvious opportunity (first-gen navigation, not generic wellness) and explain why the obvious answers are wrong before proposing something better. Strategic awareness shows up in whether you surface the institutional buyer without being prompted. Both require preparation that goes beyond memorizing a framework.

The named-user-group format of this question (“design a product FOR college students”) is a specific test of whether you can resist shallow demographic reasoning. Interviewers use it precisely because the tempting bad answer is so available.

The design WhatsApp for students prompt is often paired with this one and signals the interviewer cares about coordination and communication patterns in student life, not just solo productivity. For the 2026 context on why feasibility has stopped being the constraint, see feasibility is free. For why usability is no longer the bar and what lovability actually requires, see lovable, not just usable.