Design a Product for Senior Citizens: Complete Product Sense Answer

Why This Question Keeps Showing Up in 2026

“Design a product for senior citizens” is one of the most durable product sense prompts in PM interviews at Google, Meta, Amazon, and mid-size B2C companies. Interviewers like it because it forces you to design for a user you probably aren’t, which exposes whether you actually run user research in your head or just pattern-match to your own life. Updated for July 2026: with population aging accelerating across the US, EU, Japan, and China, this prompt has moved from “quirky edge case” to “obviously relevant market,” and interviewers expect candidates to know the segment cold.

This article gives you the complete structure for answering it end to end. Companion articles in this series go deeper on segmentation, metrics, and tradeoffs and MVP scope. For structured PM interview frameworks, see The 100x Product Manager Interview Playbook (Amazon: https://www.amazon.com/dp/B0DBC1FQWH?tag=sirjohnnymai-20).

Step 1: Clarify the Prompt Before You Design Anything

Weak candidates jump straight to “an app that reminds them to take pills.” Strong candidates spend the first 90 seconds narrowing scope. Ask the interviewer (or state your assumptions out loud if it’s a written prompt):

What product surface? Mobile app, physical device, web, voice assistant, or a service layered on an existing product?
What company is asking? A health insurer, a consumer tech company, a telecom, or a general “assume you work at Google” framing changes the answer completely.
What’s the business goal? Retention of an aging existing user base, new market entry, or a CSR/accessibility mandate?
Which slice of “senior citizens”? 65-75 healthy and active looks nothing like 85+ with mobility or cognitive decline.

State your assumption plainly: “I’ll assume this is a general consumer tech company looking to build a new product for the 65+ demographic, optimizing for daily engagement and trust.” That sentence alone signals PM maturity.

Step 2: Build the User Research Foundation

Before touching solutions, ground the interview in real behavioral patterns. You don’t need primary research data in an interview, but you need to reason like someone who has read it.

Three pain point categories to always cover

Category	What it looks like	Why it matters for design
Health	Medication adherence, mobility limits, vision/hearing decline, chronic condition management	Drives urgency and safety-critical design decisions
Isolation	Reduced social circles after retirement, loss of spouse/peers, geographic distance from family	Drives engagement loops and retention hooks
Digital literacy	Unfamiliarity with gestures, small tap targets, fear of “breaking” the device, scam vulnerability	Drives onboarding, UI, and trust/safety design

A common interview mistake is only covering health, because it’s the obvious one. Isolation is actually the higher-leverage insight for most consumer products — loneliness in seniors is a well-documented driver of both health outcomes and product engagement, and it’s less crowded competitively than the medication-reminder space.

Say the quiet part: seniors are not one user

The single highest-signal move in this interview is refusing to treat “senior citizens” as monolithic. A 68-year-old who just retired from a corporate job and travels twice a year has almost nothing in common with a 91-year-old in assisted living. Naming this explicitly, then picking one segment to design for, is what separates a 6/10 answer from a 9/10 answer. The segmentation article in this series breaks this into four working personas you can reuse in any interview.

Step 3: Convert Pain Points Into a Prioritized Problem Statement

Once you’ve listed pains, don’t design against all of them. Pick one, and justify the pick with a simple lens: frequency × severity × how underserved it is by existing solutions.

Example reasoning out loud: “Medication reminders are already well-served by pharmacy apps and physical pill organizers. Isolation is high-frequency, high-severity, and poorly served by anything except social media, which seniors largely don’t use comfortably. I’m going to design for reducing isolation among recently-retired, otherwise-healthy seniors.”

This single sentence does three things interviewers are scoring for: prioritization logic, competitive awareness, and a falsifiable, narrow scope.

Step 4: Generate Solutions With a Framework, Not a Brainstorm

Don’t free-associate features. Use a simple structure: for the chosen problem, generate 3-4 solution directions at different levels of investment, then pick one to go deep on.

Low-lift: A simplified “call a family member” button surfaced contextually based on time-of-day loneliness patterns.
Medium-lift: A curated community feature matching seniors by shared interest/location for recurring small-group video calls.
High-lift: A physical companion device (tablet-like, always-on) that surfaces family photos, prompts video calls, and requires zero navigation.

Pick one and go deep — most interviewers want depth on one direction more than breadth across three. Walk through the core user flow, the key screen or interaction, and the first moment of value.

Step 5: Address Accessibility as a Design Constraint, Not an Afterthought

This is where many candidates lose points. Accessibility for seniors isn’t a “nice to have” checklist — it’s core to whether the product works at all. Cover, briefly:

Large tap targets and high-contrast text (not just “we’ll follow WCAG”)
Voice-first or voice-assisted interaction as a fallback for low digital literacy
Trust and scam-protection design, since seniors are disproportionately targeted by fraud
Onboarding that assumes a family member or caregiver may set up the device initially

Step 6: Close With Success Metrics

Even a strong solution answer falls flat without a metrics close. State a north star candidate (“weekly meaningful social interactions per active user”) and 2-3 supporting metrics. The full framework for this — including counter-metrics to watch for unintended harm — is covered in the metrics and north star article in this series.

A Full Answer Structure You Can Reuse

Step	What to say	Time budget
Clarify	State assumptions about company, surface, and segment	1-2 min
Research	Cover health, isolation, digital literacy pain points	2-3 min
Segment	Pick one persona explicitly	1 min
Prioritize	Frequency × severity × white space	1-2 min
Solution	3 directions, deep dive on 1	5-6 min
Accessibility	Name it as a core constraint	1-2 min
Metrics	North star + 2-3 supporting metrics	2 min

Common Mistakes That Sink This Answer

Designing a generic health app and calling it done — this ignores 70% of the persona space
Treating “senior citizens” as universally low-tech, which is increasingly false for the 65-75 cohort
Skipping business goals entirely and designing a pure charity project
No mention of caregivers, who are often the actual decision-makers and even the actual users
Forgetting trust/safety, a top-3 concern for any product targeting this demographic in 2026

Final Thought

This prompt rewards structure and empathy in equal measure. The candidates who stand out aren’t the ones with the cleverest feature idea — they’re the ones who clearly demonstrate they’ve thought about a real, specific person, justified their choices with a repeatable framework, and closed the loop with metrics. Practice this structure on 2-3 other demographic-based prompts (new parents, college students, people with disabilities) and you’ll find the skeleton transfers almost entirely.

For a deeper, more systematic bank of product sense frameworks used across FAANG and high-growth company interviews, see The 100x Product Manager Interview Playbook (Amazon: https://www.amazon.com/dp/B0DBC1FQWH?tag=sirjohnnymai-20).